frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

We Mourn Our Craft

https://nolanlawson.com/2026/02/07/we-mourn-our-craft/
75•ColinWright•1h ago•41 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
21•surprisetalk•1h ago•18 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
121•AlexeyBrin•7h ago•24 comments

U.S. Jobs Disappear at Fastest January Pace Since Great Recession

https://www.forbes.com/sites/mikestunson/2026/02/05/us-jobs-disappear-at-fastest-january-pace-sin...
102•alephnerd•2h ago•55 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
824•klaussilveira•21h ago•248 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
56•vinhnx•4h ago•7 comments

Al Lowe on model trains, funny deaths and working with Disney

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
53•thelok•3h ago•6 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
105•1vuio0pswjnm7•8h ago•121 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1058•xnx•1d ago•608 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
76•onurkanbkrc•6h ago•5 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
478•theblazehen•2d ago•175 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
205•jesperordrup•11h ago•69 comments

France's homegrown open source online office suite

https://github.com/suitenumerique
547•nar001•5h ago•253 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
216•alainrk•6h ago•335 comments

Selection Rather Than Prediction

https://voratiq.com/blog/selection-rather-than-prediction/
8•languid-photic•3d ago•1 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
35•rbanffy•4d ago•7 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
28•marklit•5d ago•2 comments

Show HN: I saw this cool navigation reveal, so I made a simple HTML+CSS version

https://github.com/Momciloo/fun-with-clip-path
3•momciloo•1h ago•0 comments

I Write Games in C (yes, C)

https://jonathanwhiting.com/writing/blog/games_in_c/
4•valyala•1h ago•1 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
113•videotopia•4d ago•30 comments

SectorC: A C Compiler in 512 bytes

https://xorvoid.com/sectorc.html
4•valyala•1h ago•0 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
73•speckx•4d ago•74 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
68•mellosouls•4h ago•73 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
273•isitcontent•22h ago•38 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
199•limoce•4d ago•111 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
285•dmpetrov•22h ago•153 comments

Making geo joins faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
155•matheusalmeida•2d ago•48 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
21•sandGorgon•2d ago•11 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
555•todsacerdoti•1d ago•268 comments

Ga68, a GNU Algol 68 Compiler

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
43•matt_d•4d ago•18 comments
Open in hackernews

NeXTSTEP on Pa-RISC

https://www.openpa.net/nextstep_pa-risc.html
62•andsoitis•1mo ago

Comments

badc0ffee•1mo ago
> NeXTSTEP itself, while revolutionary in aspects, did not have long commercial success. However some of its ideas and technologies live on in Mac OS, after corporate M&A and consolidation in the tech sector.

On the contrary, macOS is NeXTSTEP plus several years of development. It's what the NS means in NSLog.

erichocean•1mo ago
And iOS of course is also derived from it.
pipo234•1mo ago
I guess it's a bit more subtle.

The point that the article makes is about opening up NeXT to other hardware platforms. So while from one perspective, you might argue it lives on inside Apple, you could also argue that's where nextstep died.

In the early 2000s I worked for a company that went all in on NeXTSTEP a decade earlier. The product was developed in a "4 GL" called 4D or 4th dimension.

We had to do a painful migration to windows nt/xp because NeXTSTEP was discontinued and apple actively fought to kill attempts to fork or open source the code base.

anthk•1mo ago
You could port tons of code to GNUStep or that other Cocoa libre API.
astrange•1mo ago
There's plenty of differences. The device driver stack and window server are all totally different.
lukeh•1mo ago
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.
anthk•1mo ago
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.
flohofwoe•1mo ago
...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').
astrange•1mo ago
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.
pjmlp•1mo ago
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.

pjmlp•1mo ago
It used to be, Tahoe is generations away from NeXTSTEP.

NeXTSTEP drivers were written in Objective-C, originally OS X used C++ subset based on COM (IO Kit), now moved into userspace and called Driver Kit, in homage to the NeXTSTEP DriverKit name.

NeXTSTEP was focused on OpenGL and Renderman, OS X used OpenGL, macOS is now using Metal.

NeXTSTEP drivers were on kernel space, now everything is moving into userspace.

NeXTSTEP used Display Postscript, OS X moved into PDF subset, nowadays that is only part of the rendering stack.

NeXTSTEP had a X Windows Server as well, on macOS that is now gone.

macOS Finder is nothing like the NeXTSTEP file application.

NeXTSTEP supported a concept similar to OLE, it is nowhere to be seen on macOS.

jdboyd•1mo ago
Is macOS in any recognizable way still a micro-kernal operating system or did that get removed as well?
pjmlp•1mo ago
OS X was never a proper micro-kernel, rather an hybrid one like Windows NT, using still a micro-kernel like approach but with subsystems on the same process space.

https://fahrplan.events.ccc.de/congress/2007/Fahrplan/attach...

https://www.amazon.de/-/en/Mac-OS-Internals-Approach-paperba...

If anything it is going more into that direction, after Apple announced removing all kernel extensions, and having userspace counterparts to them.

https://developer.apple.com/documentation/SystemExtensions

https://developer.apple.com/documentation/systemextensions/i...

Usually it takes one OS version between introducing new userspace APIs, and removing the old way on the following version.

wpm•1mo ago
Apple removed third-party kernel extensions (and even so only removed the ability to install them without going into recovery and changing a scary box). There are still lots of .kext files in the /System folder for hardware drivers.
pjmlp•1mo ago
Yes, however that brings it closer to a micro-kernel model, if no one else is allowed to change the kernel as shipped from factory, having everything else done in userspace.

Additionally, if there is a userspace extension to an existing kernel extension, the userspace one will take precedence.

jhbadger•1mo ago
I don't know if it shares ancestry with the NextStep X server, but the one that used to be bundled with OS X (Xquartz) is still availsble for download (even on Tahoe) and I for one still keep it installed as I run various X11 based programs on my Macs.
p_l•3w ago
Finder has a lot of signs of being actually a MacOS Classic application - not just the internal presence of Classic-style paths (with ":" separators) but also how Dock was originally developed on MacOS 9.x because the principal developer didn't have OSX machine allocated.
speed_spread•1mo ago
What we really needed was NeXT on Alpha. So much cool tech lost to the Wintel juggernaut in the 90s.
WillAdams•1mo ago
I would really like for it to be easier to run NeXT/OPENSTEP on modern hardware --- somehow, since Mac OS X 10.6.8, Mac OS has gotten ever less comfortable (and I really miss the "Unix Expert" checkbox, as well as the repositionable main menu, tear off menus, pop-up main menu, Display PostScript, nxhosting, &c.

An educational copy of OPENSTEP 4.2 was the last thing I purchased for myself from Apple since they discontinued the Newton MessagePad.... and I'm sad my Cube quit booting, and that I never got it running on my ThinkPad.

felixding•1mo ago
100% this.

Let's hope projects like https://github.com/trunkmaster/nextspace succeed.

WillAdams•1mo ago
Yeah, a nice GNUstep or similar environment for Linux would be a workable option --- I'd love to see something optimized for a Raspberry Pi....
TMWNN•1mo ago
>NeXT tried to get its own NeXT RISC workstation to market (chased a chimera) and looked at Motorola 88000 and PowerPC

Jobs made a huge mistake by going with the 68K in the first place. DEC would prove just a few months after NeXT's October 1988 launch the viability of a MIPS-powered workstation.

Even better, in the long term, would have been to go with the 80386.

stmw•1mo ago
In fairness, I think it wasn't obvious that Motorola would run into so much trouble with the 68k line, or that 80386 would be the far-away winner. Sun and many others were betting on 68k, too.
TMWNN•1mo ago
>Sun and many others were betting on 68k, too.

Sun launched its first SPARC-based system more than a year before the NeXT launch in October 1988.

Sun came out of Stanford and was aware of the Stanford and Berkeley RISC architectures (the latter of which led to SPARC). NeXT had academia heritage, too, via Mach from CMU, but I guess it wasn't enough to persuade Jobs to go for a more exotic architecture than the one he was familiar with from Apple, or the "enemy" in Intel.

One can see a world in which NeXT goes with 80386 from the beginning, eventually pivots much earlier to software-only, and becomes a real rival to Microsoft and IBM in the early 1990s to provide a multitasking successor to DOS. Or, for that matter, IBM goes with NeXTSTEP (or just buys NeXT) instead of the AIM Alliance.

stmw•1mo ago
No dispute on the facts about Sun etc. "more than a year before" is not a lot of time in hardware launches, and that was a very dynamic time. Regarding Sun, some good old HN discussion here: https://news.ycombinator.com/item?id=29082150

But the alternate computer history is interesting to imagine, could have been via x86 or PowerPC with IBM or something else. Same with Be.

p_l•3w ago
My understanding is that issues in scaling 68k line were already well known by then, same as with VAX (even if crucial people at Digital didn't want to believe).

The difference is that 68k was ubiquitous, reasonably cheap 32bit capable platform with MMU that had huge availability of parts and made porting software easy. Sun was working with 68k partially because they chose it in 1980, a year after it was made available, and by 1986 they published SPARC ISA and shipped first systems a year later

antijava•1mo ago
I used to have a NeXTStep HP workstation back in the day. Worldcom had hundreds of them running custom network monitoring. I think we were one of,the biggest NeXT installations outside of the NSA.