News for hackers. Stuff that matters.
Re:NeXTSTEP on Pa-RISC by astrange on Monday January 05, 2026 @03:31AM (#46496504)
There's plenty of differences. The device driver stack and window server are all totally different.
Re:NeXTSTEP on Pa-RISC by lukeh on Monday January 05, 2026 @04:04AM (#46496693)
And Mach 3 vs 2.5. And a 4.4BSD (well, *BSD) user land, although in fairness the original, never released NEXTSTEP 4.0 also had this.
Re:NeXTSTEP on Pa-RISC by anthk on Monday January 05, 2026 @05:22AM (#46497160)
So is the jump between W9X and NT based OSes, both in the kernel, graphics modes (GDI, Direct Draw vs Direct3D to draw the desktop, compositing window managers...) and the like. Specially after Windows 8 where Direct Draw it's slow as hell and you need to use WineD3D which runs ddraw.dll on top of OpenGL. But you can use Win32 on both.
Re:NeXTSTEP on Pa-RISC by flohofwoe on Monday January 05, 2026 @05:39AM (#46497281)
...I'm pretty sure the same would be true in any modern version of NeXTStep had it survived as its own 'brand' (apart from slightly different requirements caused by the hardware the OS needs to run on of course - e.g. running on a handful different Apple devices versus having to work on 'everything').
Re:NeXTSTEP on Pa-RISC by astrange on Monday January 05, 2026 @05:30PM (#46506009)
Darwin ditched the old driver stack for IOKit because they thought it was icky to have ObjC in the kernel. That's pretty much entirely up to leadership changes, not technical reasons.
Re:NeXTSTEP on Pa-RISC by pjmlp on Tuesday January 06, 2026 @03:54AM (#46510124)
Agreed, the same way Longhorn, Midori and Singularity failed to win the hearts of Windows team, while Android and ChromeOS obliterated their mobile and US school market.

Turns out using a managed userspace is viable, if management is on board to support the development all way through.