Comment by wowczarek
12 hours ago
Photon was what I was hoping for before I clicked the link. One of my favourite GUIs, closely tied with CDE.
Photon or not, I hated the period where they sort of moved to canned BSP deployment only, where in 6.5 I could just develop on a live system. This is nice.
Me too, although it's been a long time since Photon.
"This environment runs as a virtual machine, using QEMU on Ubuntu. To try the image, you'll need: Ubuntu 22.04 or 24.04." So it doesn't boot on bare metal?
Maybe they're trying to get away from needing Windows. The previous recommended development environment was cross-compilation from Windows.
The big news here is that they have a reasonable non-commercial license again.[1] The trouble is, QNX did that twice before, then took it away.[2] Big mistake. They lost their developer base. Support of open source tools on QNX stopped. As I once told a QNX sales rep, "Stop worrying about being pirated and worry about being ignored". They'll need to commit contractually to not yanking the non-commercial license to get much interest.
QNX should be licensed like Unreal Engine. If you ship enough products using it, it gets noticed and they contact you about payments, and if you're not shipping much product, Unreal doesn't care. This has created a big pool of Unreal developers, which, in turn, induces game studios to use Unreal. Unreal's threshold is US$1 million in sales.
Apparently they opened things up a bit last year, but nobody noticed.
Usefully, there is a QNX Board Support Package for the Raspberry PI, so you can target that. QNX would be good for IOT things on Raspberry PI machines, where you don't want the bloat and attack surface of a full Linux installation.
[1] https://qnx.software/en/developers/get-started/getting-start...
[2] https://www.theregister.com/2024/11/11/qnx_8_freeware/
Bare metal is on the short-term roadmap!
> QNX should be licensed like Unreal Engine.
That sounds quite a bit harder to enforce for an OS designed to run inside, often not internet-connected, devices.
If someone would decide to run QNX (or whatever) inside, often not internet-connected, devices then some IP enforcement wouldn't stop them anyway.
1 reply →
> They lost their developer base. Support of open source tools on QNX stopped.
Right. These days it's better to invest into Redox OS[1] as a potential substitute for it (if work on real time capability). And with real time patches merged into Linux mainline[2] QNX doesn't stand much chance today too.
[1] https://doc.redox-os.org/book/microkernels.html
[2] https://arstechnica.com/gadgets/2024/09/real-time-linux-is-o...
> And with real time patches merged into Linux mainline[2] QNX doesn't stand much chance today too.
Correct me if I'm wrong but these and other Linux patches were always about soft real time and Linux never had hard real time capability because of its architecture.
1 reply →
It’s really sad it wasn’t open sourced. In the early 2000s I was triple booting Windows 98, BeOS, and QNX. BeOS was my favorite, but QNX Neutrino was great as well.
> One of my favourite GUIs, closely tied with CDE.
In case you're not aware: CDE is still around, open source, and runs on modern unix-likes.
> In case you're not aware: CDE is still around, open source, and runs on modern unix-likes
Oh I'm aware :) also this beauty from SGI is now around again:
https://docs.maxxinteractive.com/
There is also a FWWM[1] "skin" that doesn't require long time abandoned C code - NsCDE[2]. It still requires X server (just like CDE itself) which becomes rarity these days. They need to port it to Wayland eventually.
[1] https://github.com/fvwmorg/fvwm3
[2] https://github.com/NsCDE/NsCDE
Eh, there's always https://gitlab.freedesktop.org/wayback/wayback for that.