Given the long history of poor quality software devlivered by IC vendors I am reluctant to use any controller with a builtin ROM driver library or vendor code.
These companies are not in the software business. their only goal is to deliver some examples on how to use the chip, not provide production ready, reliable and maintainable code.
As a user of microcontrollers I don't like the idea that every semiconductor vendor rolls his/her own RTOS.
That's IMHO more like a vendor lock in than anything else. Ideally a RTOS should enable you to switch semiconductor manufacturers easily.
BTW I don't think that it will help to throw RTOS solutions to people in order to have more designs going to production. People need also to be trained how to use this kind of technology.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.