Hacker News new | past | comments | ask | show | jobs | submit login

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.



ISO 26262 ASIL D safety certification, mature tooling and ecosystem, easy to hire experienced devs, “it worked for the last 5 projects”, etc.


There's a few vendors that sell FreeRTOS forks that have that cert. SAFERTOS is a very common one

> mature tooling and ecosystem

Amazon has been working on freertos for a long time

> easy to hire experienced devs

tbh if you've used one rtos, you've used them all. the learning curve is in the concepts, not the api. any good vendor will have engineering support that helps you where appropriate

> “it worked for the last 5 projects”

inertia only takes you so far




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: