I actually disagree.

We have lower power bare metal systems, think AVR/STM stuff (in the 1Mhz to 50Mhz range with 128K or less of RAM) here FreeRTOS, no freeRTOS, custom driver code and some basic application code makes sense. For simple to very complex systems.

Then there's 1Ghz+ stuff with an MMU and 2GB+ RAM. Linux makes sense here.

Companies are now making chips 200Mhz+, 4MB RAM, with no MMU. This is precisely where Zephyr excels, you want a full networking stack? Switch that on. A file system, easy. Driver for some more complex thing? Maybe an SDIO radio? boomboom

nRF52820 is 256 KB Flash and 32 KB RAM chip. Actually it's around 150 KB flash, because you need space for 120KB softdevice blob (and some RAM too). And it's perfectly enough for many devices. They want developers to use Zephyr for this chip.

Finally, it's finished! I want to give a huge thanks to the community for supporting the project over the past year! I'm excited to take this next step!

AMA!

Hey! Project I worked on with a buddy using the vl53l1x ToF range finder. Hope you like it :) !

Thanks for the link to the paper, this was an insane amount of work.

Yup +1, I agree with you and the OP. If you work for a huge company your skill set may be extremely narrow. Buy having lots of side project will at the very least give you a talking point if you want to change to another company that might not have the exact position you were working at your current company

>> If you work for a huge company your skill set may be extremely narrow.

In my experience working for a huge company makes it very easy to broaden your skills. You can change teams, take on mentorship and recruiting, lead teams, lead initiatives, switch from front- to backend at different times, and learn from a large number of people - all from the "comfort" of the company you are already in.

This is a post documenting my adventures in fitting a WiFi router into a wall charger!