by BirAdam on 10/5/25, 2:47 PM with 142 comments
by faluzure on 10/5/25, 7:37 PM
First, we had ICON computers in my elementary school, we'd all try to spin the trackball as quickly as it would go. Not sure if we ever broke one.
The second is when I worked at BlackBerry. I was building a feature that allowed you to use your QNX BlackBerry as a Bluetooth HID device. You could connect it to any device and use the trackpad + physical keyboard to remotely control a computer. It was fantastic. You could hook your laptop up to a project and control slides from your BlackBerry.
Then some product manager with questionable decision making told me to lock it down so it would only work with Blackberry Playbooks for "business purposes", rendering it effectively useless (since Playbooks are all ewaste). I distinctly remember that meeting where Dan Dodge argued that since it's a standard, it should not be locked down.
I respect Dan Dodge for that, I don't think I'd work with that PM again.
by taviso on 10/6/25, 12:26 AM
This was a screenshot of my Gentoo desktop around 2004!
by travisgriggs on 10/5/25, 10:51 PM
It was a powerful lesson (amongst others) in what I came to call “the Law of Conservation of Ugly”. In many software problems, there’s a part that just is never going to feel elegant. You can make one part of the system elegant, which often causes the inelegance surface elsewhere in the system.
by jasoneckert on 10/6/25, 2:40 AM
by _joel on 10/5/25, 6:38 PM
by Theodores on 10/5/25, 8:07 PM
What I also liked about QNX was the petite size. If I remember correctly it came on one floppy disk, and that included a GUI, not that you need a GUI with QNX since the product will be an embedded system of sorts. All of the documentation was clear and, even if you had not read the manual, the overlap with UNIX meant that the system was far from intimidating as most of the commands that I knew would work fine, albeit with different options to commands.
I had not fully realised how QNX had gone from strength to strength in automotive, and I didn't even know Harmon owned them for a while.
Given that we have gone from single core, 32 bit 386/486 to today's sophisticated SOCs that are thousands of times more capable, the question has to be asked, how important is QNX's superpower of realtime goodness, particularly if it is just for automotive applications such as turning on the A/C?
Surely a modern CPU that goes so much faster can do a better job without having to care about realtime performance? Or maybe Android Auto and Automotive Linux have those bases covered? Regardless, I am sure that if you want realtime embedded applications then you hire the guys that know QNX and reject those that haven't a clue.
by heja2009 on 10/6/25, 8:25 AM
One feature of the OS I fondly remember was that the most basic system calls (send/receive/reply) were implemented as about 3 inline assembler instructions each directly in the header file (qnx.h ?).
by WillAdams on 10/5/25, 6:31 PM
https://carleton.ca/rcs/qnx/installing-qnx-on-raspberry-pi-4...
by kragen on 10/6/25, 1:12 AM
Things they weren't anticipating included GNU, the internet, Microsoft Windows, third-party development, the Windows applications barrier to entry, the World-Wide Web, shareware, BBSes, VARs, and the free-software movement. They didn't understand how operating systems were a winner-take-all game, so pricing your OS at hundreds of dollars was a losing strategy.
But it was 01986, so who could blame them? Their 01987 ad does try to reach out to VARs.
Still, they were certainly aware of Unix, and you'd think that would mean they were aware of uucp. They just didn't anticipate its significance. Again, though, who did?
They also don't seem to have appreciated the importance of GUIs until version 2.0 in 01987, despite the popularity of the Macintosh, the "Jackintosh" Atari ST, and GEOS on the C64. The article says that the "Photon" GUI everyone remembers wasn't until QNX 4.1 in 01994.
by brynet on 10/5/25, 10:05 PM
All but a few of these computers were destroyed by the ministry of education. And without the LEXICON server that accompanied them, they're basically useless.
For a bit of fun, I ran the DOOM shareware demo using the official QNX4 port on a 486SX with 8M of ram.
https://brynet.ca/video-qnxdoom.html
I picked up QNX6 again as a hobbyist later in life... until self-hosted QNX was killed, no bootable .ISOs after 6.5. Then they killed the hobbyist license, killed the Photon desktop GUI, dropped any native toolchain support in place of a Windows/Linux-hosted IDE. Porting software became difficult, pkgsrc no longer maintained.
They are completely noncommittal as a company, nothing short of actually open-sourcing it under the MIT/BSD would convince me to use it again.. and not another source-available effort that they inevitably rug pull again.
https://www.osnews.com/story/23565/qnx6-is-closed-source-onc...
by Rochus on 10/5/25, 7:44 PM
The Neutrino 6.4 version, which was made accessible as "openQNX" to the public, can still be downloaded from e.g. https://github.com/vocho/openqnx.
Here is an AI generated documentation of the source: https://deepwiki.com/vocho/openqnx
by ahartmetz on 10/5/25, 6:55 PM
by yangosoft on 10/5/25, 7:04 PM
by Quessy on 10/6/25, 7:38 AM
by 51Cards on 10/5/25, 7:07 PM
by CalChris on 10/5/25, 7:51 PM
by Aldipower on 10/6/25, 1:25 PM
by jacquesm on 10/5/25, 8:32 PM
by gmueckl on 10/5/25, 6:36 PM
by Lammy on 10/5/25, 9:20 PM
So much '90s anime in those screenshots — super nostalgic!
by aclark on 10/5/25, 10:03 PM
by michaelw on 10/5/25, 9:53 PM
The OS was so clean but it lacked a lot of basic tooling. Back then there was no GUI or even a graphics library. We had to build or port a lot of things, including a VCS, from scratch. My editor of choice was JOVE (I couldn't get Emacs to build). I remember digging up various papers on graphics and creating our first graphics library.
by pjmlp on 10/6/25, 8:38 AM
It was great experience, especially for those of us that appreciate microkernels.
by dvratil on 10/5/25, 7:26 PM
I was also a huge fan of BlackBerry phones (having used Q5 and Z10 as daily drivers). The system was solid and had some really cool ideas. Too bad it didn't work out...
by leakycap on 10/5/25, 11:06 PM
by kotaKat on 10/5/25, 6:38 PM
by cmos on 10/6/25, 1:49 PM
We needed the help. Thank you Dan!! We eventually ported to linux about 6 years later, but you helped our startup get up and going.
by christkv on 10/6/25, 5:29 AM
by varispeed on 10/5/25, 8:23 PM
by lambertsimnel on 10/6/25, 7:30 AM
by derekcheng08 on 10/6/25, 3:03 AM
by smoyer on 10/6/25, 12:14 AM
by hacknews20 on 10/6/25, 12:35 PM
by xattt on 10/6/25, 12:25 AM
by jjkaczor on 10/6/25, 1:06 PM
by pjmlp on 10/6/25, 9:04 AM
> The name QUNIX was a bit too close to the name UNIX for AT&T. The name of the system was changed to QNX in late 1982 following a Cease and Desist by AT&T.
Already not as nice as in the early days.
> While RV1 was limited to just C and x86 assembly language, the company was hard at work on BASIC, FORTRAN, and Pascal compilers that would utilize common code generators allowing for the mixed-use of languages without losing optimization.
Yet another example of previous polyglot compiler stacks attempts.
> UNIX systems come in more flavours than ice cream.
That was a fun one.
by transitorykris on 10/5/25, 9:17 PM