Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

111

I've been playing around with ZenithOS, a fork of TempleOS. I was reading their road map. A lot of it made sense. But then out of nowhere it said "drop support for all floating point types".

Here is the full roadmap:

  • AHCI driver that is capable of reading and burning CD/DVD discs, and can also work with RW discs.

  • Speed up the OS by doing compiler optimizations like register arguments.

  • Drop floating point support completely.

  • Add either SSE or AVX support (not both) to the assembler/compiler, for working with large integers.

  • Write a new 32-bit color graphics library that uses the added SIMD instructions. Refresh DolDoc for the following:

  • Build a simplistic GUI framework that integrates with DolDoc and the terminal using the new graphics library.

  • Add Intel HD Audio support.

  • Write drivers for the 5 most common ethernet cards.

  • Create a clean and robust networking stack that supports raw sockets, TCP, UDP, IP, ICMP, DHCP, and an HTTP library. Perhaps we can avoid Berkeley Sockets and create our own system?

  • Write applications using this networking stack.

  • Write a JSON library, so REST APIs can be used.

  • Drop FAT32 and maybe RedSea, replace with exFAT and proper ISO9660 support.

  • Whole system VCS, with root being top-level directory. Stored repo inside the OS, you can checkout any commit onto another partition and boot it to see what the OS was like in that commit.

  • Pull updates directly onto root filesystem from network. (it's a repo source tree after all).

  • At this point, bigger fish in the pond can be eyed. Perhaps support for USB keyboard and mice, and native USB mass storage support, significant code clean up and refactoring.

  • Port to other architectures??

Do you see any benefit?

I've been playing around with ZenithOS, a fork of TempleOS. I was reading their road map. A lot of it made sense. But then out of nowhere it said "drop support for all floating point types". Here is the full roadmap: - AHCI driver that is capable of reading and burning CD/DVD discs, and can also work with RW discs. - Speed up the OS by doing compiler optimizations like register arguments. - Drop floating point support completely. - Add either SSE or AVX support (not both) to the assembler/compiler, for working with large integers. - Write a new 32-bit color graphics library that uses the added SIMD instructions. Refresh DolDoc for the following: - Build a simplistic GUI framework that integrates with DolDoc and the terminal using the new graphics library. - Add Intel HD Audio support. - Write drivers for the 5 most common ethernet cards. - Create a clean and robust networking stack that supports raw sockets, TCP, UDP, IP, ICMP, DHCP, and an HTTP library. Perhaps we can avoid Berkeley Sockets and create our own system? - Write applications using this networking stack. - Write a JSON library, so REST APIs can be used. - Drop FAT32 and maybe RedSea, replace with exFAT and proper ISO9660 support. - Whole system VCS, with root being top-level directory. Stored repo inside the OS, you can checkout any commit onto another partition and boot it to see what the OS was like in that commit. - Pull updates directly onto root filesystem from network. (it's a repo source tree after all). - At this point, bigger fish in the pond can be eyed. Perhaps support for USB keyboard and mice, and native USB mass storage support, significant code clean up and refactoring. - Port to other architectures?? Do you see any benefit?

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (23).
[–] • 1 pt

It looks like some people are converting code from using floats to ints for optimization: http://justinparrtech.com/JustinParr-Tech/programming-tip-turn-floating-point-operations-in-to-integer-operations/

But to me that seems like something you would want to do after the fact if you need that code sped up, and after all the code is complete.

I'd hate to write something floating point heavy and have to do that kind of twiddling for every bit of it, with no exception to fall back on.

[–] • 2 pts

Fair enough. I think there are good chunks of code that don't require precision and can speed up things.

On another topic, what's your opinion on the new crApple M1 architecture.

[–] • 1 pt

I had to look it up, but I'd say I'm positive to it. I have very little assembly experience but from what I've seen I really like ARM's instruction set. Having different speed cores opens up more options to developers. The neural network core is kind of cool if not a bit scary. When I say I'm for AI what I mean is I'm for democratizing AI and want the average person to understand it and use it. On a highly locked down device (any apple device), I'm not 100% certain it will be used for good.

So yeah, I think their architecture is interesting, if it was being run on an open system.

[–] • 0 pt (edited )

Thanks for your insightful answer. I'm thinking the same way.

One thing is sure, the engineers who developed this new architecture are from SJ era and has nothing to do with Tim Cuck.

Seeing how crApple is showing their anti-White agenda (90% of their ads and videos are essentially filled with blacks, then latinos/asians and mixed races, adding all LGBTQWERTY+ signs hidden in plain sight), it's obvious that Tim Cuck is behind these policies and only cares about looking cool to degenerate sodomites like him while also taking selfies and opening stores in middle-eastern countries that are murdering gays.

We need the competition to come up with equivalent alternatives (not counting on Intel).