211–220 of 380 posts
Earlier quoted context omitted.
My honest opinion is that the prevalence of licenses like GPLv3 and AGPLv3 end up indirectly leading to people recreating the wheel, rather than using the wheel that exists already.
Working as intended. If they don't want to share, then they can't benefit.
Earlier quoted context omitted.
One of the dirty secrets of the mobile industry, particularly before Apple showed up and spoiled all the fun, was how many execs and chunks of the ethos were airlifted out of Ma Bell. The kind of moat-building we're seeing take over the internet over the last couple decades is something that mobile carriers already had in heaps. It was also common for carriers to extort very high fees from anyone selling apps on thei…
I remember getting some LG phone in maybe 2007 and being excited because I read you could write 3rd party apps and games for it. Then I tried reading the BREW developer docs and trying the emulator, which were both abysmal. Then I read that just to try an app on my phone I would need to pay hundreds of dollars (IIRC it was $400) to get it signed. That totally killed my desire to develop for my flip phone.
Earlier quoted context omitted.
"Real time" is only good if you need guaranteed responsiveness within certain time limits. It can actually be suboptimal and slow you down if you don't need it and want to optimize other things like throughput.
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.
Industrial automation and hard real-time embedded devices like those that control surfaces in Fly-By-Wire systems are out there and with those it's not a matter of "throughput" but a matter of timeliness.
I did a major project with QNX about a decade ago where the maximum allowed latency between any device on the (fiber-optic) network being asked a question by the master controller and the reply - then the processing of the reply - was less than 1 millisecond, full stop.
Come in late and most of the time the sky doesn't fall in. But on the occasions that it does, you potentially have a 4 meter wide ribbon of red-hot steel flying out of the stands at 50mph. Or you blow one of the transistors that controls the 10-20 megawatt DC motors in each stand. (These "transistors" were boxes about 7' tall, filled with oil, and cost northwards of $200k).
Sometimes it just doesn't pay to be late.
@JohnAtQNX can you remove the "everybody needs an account" restriction from your website downloads, and also remove the license mechanism from qcc? That would go a long way towards encouraging hobbyists to try it out. Your money comes from high-volume licensing deals, where you presumably get a per-unit license fee. That revenue stream is jeopardized by pissing off the CI/CD teams that have to support QNX product lin…
Hiya! We've discussed how to make that work. It's good to hear the same thing from an outside voice. I'll bring it back to the table to inch it along. Thanks!
When you're a consultant or a random sysops person in a huge enterprise, that's infuriating. There is zero benefit to the vendor doing this, nobody can ever benefit from "pirating" a free component that can't be used without another paid component.
I've permanently blacklisted vendors for pulling this kind of thing.
Most recently Crowdstrike: I was up all weekend doing emergency server rollbacks and they had the nerve to publish critical information behind a login!
Tip: If your company ever uses the word "you" in any communication of any kind, then that company has made a serious error of understanding. There is no "you" at an enterprise customer! There's teams of many people each, and not all of them are even aware of who has an account and for what.
Earlier quoted context omitted.
Also I wonder how many applications really need more real time responsiveness than you can get out of Linux. We even have https://arstechnica.com/gadgets/2024/09/real-time-linux-is-o... If I use Linux I know I won't have to have a discussion about licensing, I know I won't get rug pulled, etc. Also the ban on commercial use is heinous. I am going through this with Arangodb right now. I love the product, but I have no…
rt linux is not appropriate for many hard realtime requirements i have seen some try and fail in an effort to save $perceived_value
What would be a good hobbyist project to learn QNX?
I'd rather look at seL4, pragmatically speaking.
You already have to add things to microkernel-based systems to make them useful. You have to add even more to those based on separation kernels.
Earlier quoted context omitted.
I remember getting some LG phone in maybe 2007 and being excited because I read you could write 3rd party apps and games for it. Then I tried reading the BREW developer docs and trying the emulator, which were both abysmal. Then I read that just to try an app on my phone I would need to pay hundreds of dollars (IIRC it was $400) to get it signed. That totally killed my desire to develop for my flip phone.
It's crazy to think that that's an ecosystem where paying a dollar or more for a ringtone had been normalized.
https://www.visualcapitalist.com/music-industry-revenues-by-...
Earlier quoted context omitted.
You would use it if you wanted to get a job doing RTOS dev and wanted to show you had some skin in the game.
Maybe you would have used QNX as an engineer flex in 2012, but as an embedded firmware dev myself, I'd laugh if someone suggested we use QNX for anything. Besides the licensing issues... just why? It confers no imaginable benefit versus any one of dozens of alternatives. It's like if someone suggested I run Haiku on my work laptop.
For QNX 8.0, here’s a saved-you-five-minutes direct link to the developer terms associated with noncommercial use: https://support7.qnx.com/download/download/51624/BB_QNX_Deve... (I am not your lawyer, this is not legal advice. This is not a comprehensive review, assessment, or summary of possible interpretations of that license. Seek professional counsel from a lawyer before acting on anything stated below.) These t…
Since when are social apps high risk? The high risk clause is clearly targeted at applications that have safety requirements (IEC 61508, ISO 26262 etc.). A crashing Twitter client won't injure or kill anyone.
any product, device, component, or system which if it fails or is interrupted, may result in loss of life, or other serious or catastrophic personal injury and/or substantial financial or commercial or societal loss.
So its not just safety-critical applications, it also includes "societal loss". What does that mean I have no idea. Does losing Twitter client leads to "societal loss"? You can argue both ways