jmmv
Joined 13 years ago
Joined 13 years ago
Also, they didn't want you to be able to guesstimate how many machines / computing power they had, for similar reasons.
(Why a fork? Because it's primarily vibecoded and Haiku won't take the patches upstream. But hey, I'm gonna give it a try anyway.)
TBH, I had used Emacs before VSCode and had accumulated a bunch of cruft in my .emacs configuration, and I never felt it was "mine" anyway...
This is also pretty common even if you don't use multiboot. The I/O services exposed by the BIOS or firmware during boot may not be usable once the kernel has started, and thus the kernel has to provide its own drivers.
Then I "switched" to Substack 3 years ago and the audience growth is real. I'm approaching 2000 subscribers (some of which are paid, which always surprises me and I appreciate), and these keep growing organically although I'm sure a large portion of which are fake. It's hard to say it doesn't work or isn't worth it.
Now... spoiler: I never "switched" to Substack. I continue to write all of my content on my website _first_, with all of the features it had before, but now I copy/paste the content into Substack and distribute it that way. It's painful, but I have scars from when I moved off of Medium and want to ensure I "own" the originals.
If you are curious, I had written more about this 2 years ago in https://blogsystem5.substack.com/p/20-years-of-blogging
But what I also came out thinking was: none of that shows. The kernel is great, sure, but all of the crap that has been built on top doesn't let it shine, and that's what people interact with. Take Windows 11 with is dog-slow file manager and the overall feeling that everything is bloated and designed to annoy you. I wish there was a simpler edition... but it ain't gonna happen.
What? First, those chips were plenty powerful to run HL2 (the game predates them). And second, all x86_64 chips can run older x86 32-bit code unmodified.
The reason macOS stopped supporting 32-bit code has nothing to do with the processors but more about them wanting to remove support for 32-bit binaries from the kernel and from all user-space libraries. To run a 32-bit binary, you need itself and all libraries it depends on to be 32-bit too, including the syscall boundary, which is "fine" (both Windows and Linux do this just fine, so it's really on Apple to have removed this). And I suppose Apple removed those because it was building towards a 64-bit-only world to simplify the Apple Silicon transition.