News for hackers. Stuff that matters.
Re:Using BeOS on a Power Mac (2001) by wmf on Sunday December 26, 2021 @03:38PM (#29696080)
Most of what I learned from BeOS was what not to do (endian-specific code, C++ ABI, proprietary toolchain, messages on top of byte streams, forced multithreading, etc.). I still don't understand where the responsiveness came from.
Re:Using BeOS on a Power Mac (2001) by laumars on Sunday December 26, 2021 @04:43PM (#29696670)
The multi-threading was probably part of the reason. SMP was quickly becoming more and more common place with even Power Macs having a second processor despite Mac OS 9 and it’s predecessors not supporting SMP (applications had to specifically be written to support it).

Likewise on Intel, you had Windows 9x that didn’t support SMP so you were stuck with the NT line if you wanted multi processor support. I recall NT4 being pretty poor for desktop usage due to patchy driver support but Windows 2000 was amazing. Linux and BSD weren’t really desktop ready either.

So BeOS was basically a workstation class operating system designed to be running on lower footprint hardware (the comparison someone else made to Amiga is pretty apt).

As much as I typically hate Windows and prefer Linux and FreeBSD, Windows 2000 was pretty solid release and particularly when you place it in its era where only BeOS really competed with it in terms of performance and stability on commodity hardware.

Re:Using BeOS on a Power Mac (2001) by fault1 on Sunday December 26, 2021 @04:13PM (#29696435)
> I still don't understand where the responsiveness came from.

personally, I thought it was because it was macos, which was riddled with a lot of legacy code, for example 68k emulation in the innards of the kernel, and tacked on cooperative/preemptive multitasking.

I remember playing with a leaked version of Copeland/Gershwin. It felt way more modern in a different way than BeOS, but I can't remember how complete it was.

Re:Using BeOS on a Power Mac (2001) by rbanffy on Sunday December 26, 2021 @08:52PM (#29698224)
> I still don't understand where the responsiveness came from.

You can get a lot of snappiness from prioritizing GUI processes and lowering the priority of everything else. In modern machines, with lots of cores, you can also try to increase affinity of different interactive processes with a set of cores so that they avoid migrating and losing caches. Finally, Apple is placing low-priority process in the efficient cores and leaving interactive code on the performance ones.