Live data from Hacker News

QNX Self-Hosted Developer Desktop

devblog.qnx.com

141–150 of 174 posts

Re: QNX Self-Hosted Developer Desktop

#141

Why would I run QNX on the desktop instead of say Linux or FreeBSD?

QNX is not a GPOS, so you wouldn't. I mean you _could_, but the real benefit here is hidden within: with the toolchain now included in this image, folks working on QNX projects can now build them right on target. No more messy cross-compilation.

Re: QNX Self-Hosted Developer Desktop

#142
post #95

If you want to fall for the QNX bait and switch a 3rd time, more fool you.

They don't promise anything "Open Source" here.

The bait and switch was around the “free” license for non-commercial use. They got lots of people using it and porting software to it, and then they revoked that free license.

Then they did exactly the same thing again a few years later.

And now, for the 3rd time, they are offering a “free” non-commercial license.

Re: QNX Self-Hosted Developer Desktop

#143

Earlier quoted context omitted.

Oh! I only worked with it commercially prior to that so I never got the memo. What an insanely stupid move. That was one of their USPs. In general QnX was commercially mismanaged and technically excellent. I'm imagining a world where they clued in early on that an open source real time OS would have run circles around the rest of the offerings and they'd have cleaned up on commercial licensing. Since the 80's they've…

There's been talk about this on Reddit too, where our chief architect of QNX 8 broke down the decision. He mentioned it was ultimately a tough decision, but that in the end the cons outweighed the pros.

Hey, could you please post a link to the thread you're referring to? I'm guessing it had to do with the io-pkt to io-sock transition, but I couldn't find any information about that.

I've also noticed that all of the message passing system calls still accept the node ID. Are there plans to open up this interface to allow for implementation of custom network managers, maybe? I'd be very interested in exploring that.

Re: QNX Self-Hosted Developer Desktop

#144
post #10
post #9

This is a major throwback to the QNX demo disk, which bundled a browser and desktop environment onto a single floppy disk!

It was mind blowing at the time because Linux required at least 4-5 floppies to set up a text-only base system while QNX ran live from just a single 1.44MB.

that's not really true. In 2001 I built a single disk linux installation (with a handful of popular nics supported) with X (tiny X with vesafb support) and rdesktop + vnc as a thin client on floppy.

I'd be honest and say that qnx demo disk had more usability overall than my disk, but one could easily have a usable text only linux bootable disk. Busybox and uclibc already existed back then.

https://www.cs.columbia.edu/~spotter/floppy.bin (won't be that useful today due to the ethernet drivers, but it was a 1.44mb floppy)

Re: QNX Self-Hosted Developer Desktop

#146
post #32

Earlier quoted context omitted.

QNX is hard realtime. At one point, its kernel had O(1) guarantees for message passing and process switching. It could have been rewritten without any loops. I'm not sure if that's still true. It's also really compact. This used to be a great selling point for underpowered car infotainment systems. Some cars had around 1Mb of RAM for their infotainment, yet they were able to run fairly complex media systems. QNX is a…

I think it is mostly used for non-UI stuff. I could be wrong but outside of car infotainment I've never seen it used for UI stuff. Mostly it just sits headless quietly running some branch of industry that we all depend on. The joke used to be that if QnX had a y2k bug that had been missed civilization would end and never mind windows because you won't have any water, food, energy or transportation anymore.

Yep. QNX was better than anything else around 2000. VxWorks was technically slimmer and more reliable, but QNX had a real mostly-POSIX-compatible environment. You could develop/debug the code on QNX itself and deploy it on the devices.

They were also early adopters of Eclipse, which was the "default IDE" before the advent of VS Code.

Re: QNX Self-Hosted Developer Desktop

#147

Earlier quoted context omitted.

I think it is mostly used for non-UI stuff. I could be wrong but outside of car infotainment I've never seen it used for UI stuff. Mostly it just sits headless quietly running some branch of industry that we all depend on. The joke used to be that if QnX had a y2k bug that had been missed civilization would end and never mind windows because you won't have any water, food, energy or transportation anymore.

Yep. QNX was better than anything else around 2000. VxWorks was technically slimmer and more reliable, but QNX had a real mostly-POSIX-compatible environment. You could develop/debug the code on QNX itself and deploy it on the devices. They were also early adopters of Eclipse, which was the "default IDE" before the advent of VS Code.

I've used VxWorks as well, yes, it was slimmer (a lot slimmer, actually), but I would disagree that it was more reliable. QnX supported a ton of hardware out of the box and if there ever was unreliability as far as I've seen it it was always comms layer related, never the core OS or any other bits that you could put next to VxWorks and compare on a functional level. You just required a much bigger SBC to run it, and that's why we used VxWorks in the first place. But I would have been much happier with QnX. I'm imagining the modern day equivalent of QnX running on a Raspberry Pi Pico or one of the larger Arduino's or a Teensy. That would be an absolute game-changer.

Re: QNX Self-Hosted Developer Desktop

#148
post #27

I always liked their original UI - Photon[1][2]. Very lightweight and fast. Also a distinct and consistent style. I understand why they dropped it in favor of Qt and later Web technologies, but it's still a big loss. [1] https://www.qnx.com/developers/docs/6.5.0SP1.update/com.qnx.... [2] https://www.mikecramer.com/qnx/momentics_nc_docs/photon/prog...

I still see it used in manufacturing.

Re: QNX Self-Hosted Developer Desktop

#149
post #102
post #27

I always liked their original UI - Photon[1][2]. Very lightweight and fast. Also a distinct and consistent style. I understand why they dropped it in favor of Qt and later Web technologies, but it's still a big loss. [1] https://www.qnx.com/developers/docs/6.5.0SP1.update/com.qnx.... [2] https://www.mikecramer.com/qnx/momentics_nc_docs/photon/prog...

I was expecting to see that, I ended up looking up some old LiteStep themes [1][2] for my fix [1] https://www.wincustomize.com/explore/litestep/6/ [2] https://www.wincustomize.com/explore/litestep/292/

Reminds me of HaikuOS.
Post reply on HN