Thanks for the informative reply. I’m a nervous one when it comes to upgrading a foundation. You’re telling me that everything is stored locally is a great help in getting a clear picture of what’s going on.
I very much appreciate the work the MBED team does. It must be an enormous task given all of the software and hardware flavors and contributions by many people.
This is quite subjective if you should switch or not. For me Mbed Studio’s code linting makes quite a big difference. I do not need to memorize all the API member functions, i just hit . (or :: or ->) and i can easily find what i am looking for. Less typos/bugs overall.
You can import any Mbed libraries/projects from github/online compiler (in earlier Studio versions that did not always work)
With Mbed Studio everything is stored locally on your hard drive. By default each your local projects will download it’s own Mbed OS framework. If you have many projects those can eat up free space quite fast. There is also an option that 1 OS version can be shared through all the projects.
Mbed Studio also notifies you if there is an update for a component of your project and can update it if you want.
Mbed Studio also lets you modify core files, so you can also contribute to core…
And you can also debug the code on your target with Mbed Studio.
Personally i think Mbed Studio is far more versatile, however first compilations/clean builds are slower than with the online compiler and Studio can also take a lot drive space.