341–350 of 380 posts
Earlier quoted context omitted.
It used to be desktop-friendly enough to develop on. It's not a purely embedded OS.
I wouldn't call it desktop-friendly. Yeah, you could install and develop for QNX on it, but that was pretty much all you could do on it? Definitely won't be playing any video games on it.
Earlier quoted context omitted.
It used to be desktop-friendly enough to develop on. It's not a purely embedded OS.
I wouldn't call it desktop-friendly. Yeah, you could install and develop for QNX on it, but that was pretty much all you could do on it? Definitely won't be playing any video games on it.
Earlier quoted context omitted.
I wouldn't call it desktop-friendly. Yeah, you could install and develop for QNX on it, but that was pretty much all you could do on it? Definitely won't be playing any video games on it.
Ignore this, I read "photon" as "proton"
Earlier quoted context omitted.
I wouldn't call it desktop-friendly. Yeah, you could install and develop for QNX on it, but that was pretty much all you could do on it? Definitely won't be playing any video games on it.
IMO "Gaming" is a level above "Desktop". You wouldn't play games on FreeBSD either yet it is a perfectly acceptable desktop OS for productivity apps. The question, can QNX still run Firefox and LibreOffice?
- graphics card drivers years behind (actually what made me switch to linux)
- A lot of linux graphic environment tied itself to systemd and it's friends
- Specifically, firefox lacks some features that available on Linux, Windows and macOS (related to memory consumptions and overall snappiness)
- Many things depend on FreeBSD specific patches to work and if you aren't a seasoned porter, good luck porting it yourself[1]
[1]: this one obviously depends on what kind of software you require. For it me it's a miss.
Earlier quoted context omitted.
QNX is heavily used in industries where functional safety or particular high assurance models are required. Sure FreeRTOS has a SafeRTOS mode, but its not sufficiently functional for a modern ADAS stack or complex robotics systems. QNX is used in all major automotive companies around the world for a reason, and a crucial part of NVIDIA's DriveOS stack.
> and a crucial part of NVIDIA's DriveOS stack fwiw they have been working hard to support linux as a second option, and have been major contributors to Real Time Linux sooooooo
If only you could believe them. QNX has been "opened" twice before. Each time, there was a rug pull, and it went closed again. Before the first rug pull, open source groups routinely added QNX to their target list. There was a Firefox for QNX. Eclipse had QNX as a target. GCC and most of the Gnu command line tools could be built for QNX. There was a desktop environment, Photon. I used that as a primary desktop for th…
>QNX went open source. Not open source. Those words have a specific definition[0], which QNX never met. 0. https://opensource.org/osd
Earlier quoted context omitted.
Who needs throughput? Server software, but Linux is already dominant there and everyone's happy. For everything else, including desktop and mobile operating systems realtime sounds like a good idea.
> For everything else, including desktop and mobile operating systems realtime sounds like a good idea. Why on earth would you need real time on desktop? Every time the topic is discussed on internet bunch of confused people chime in with this sentiment that doesn't make much sense. "RTOS" is not some magic that somehow makes everything on your desktop fast. All it would do in reality is make everything slower for 99…
We sidestep this problem because our CPUs are insanely fast for this task, so as long as you don't game, compile and record audio at the same time, you should be fine. But we don't have any guarantees.
I wonder how much DBus (the Inter-Process-Communication (IPC) standard Linux desktops have been based around) is baked into QNX & instrumental to it! Maybe I can find out now? https://ioactive.com/pdfs/IOActive_Remote_Car_Hacking.pdf or https://insights.sei.cmu.edu/blog/vehicle-cybersecurity-the-... That was such a time. It's sad that it was a security panic, to me, because there was incredible promise there... All o…
Dbus is a (not very good) userland message bus. QNX is a realtime kernel. I don't really understand what you mean by: > Really interested to see if DBus really does underpin much of QNX, or whether this was just a time & place.
Is QNX just a kernel, no userland for it? I would have assumed it might include higher level offerings, including I would guess, to be helpful, some cross-system messaging options. Until now it's been impossible to guess. But yeah, it's quite likely this DBus stuff is just Dodge's repurposing of (not fantastic but reasonably ok and well known) messaging tech, DBus, layered atop.
Earlier quoted context omitted.
Dbus is a (not very good) userland message bus. QNX is a realtime kernel. I don't really understand what you mean by: > Really interested to see if DBus really does underpin much of QNX, or whether this was just a time & place.
Maybe it's just the Uconnect infotainment system. The PDF I linked above is the in-depth Jeep hack run-down, and a huge huge huge part of it is playing around with the many many many many DBus services. Is QNX just a kernel, no userland for it? I would have assumed it might include higher level offerings, including I would guess, to be helpful, some cross-system messaging options. Until now it's been impossible to gu…
So yes, that was just a choice of whoever made the Jeep infotainment system.