I've only heard good things about PlatformIO, but it always seems like they sorta reinvented the wheel instead of using existing tools. They've done a LOT of the hard work of making stuff "just-work", but why didn't they do all this using the normal tool-chain like CMake/git/GNU-tools/crosstool-NG/etc.? Is there something extra I'm missing that you can't do with the existing tools? Or is it to get some kind of lock-i…
> but it always seems like they sorta reinvented the wheel instead of using existing tools PlatformIO wasn't built as a commercial project. What is more, we didn't re-invent wheel or clone other project/idea. PlatformIO is a practical solution for the problems which were resolved in http://smartanthill.org (the place where PlatformIO was born). The problem, where you need to build the same source code into the multip…
You know, it's funny. You explain this as a big advantage of PlatformIO, but it's actually the thing that worries me the most. I don't even know yet why -- kind of a gut feeling.
I guess it prompts me to ask question such as: will it really work properly for all 370 platforms? Or only kinda? Can it do everything I need it to? or does it limit all 370 boards to their lowest common denominator in terms of interface and exposed capabilities?
There's another argument though: Usually I need only one board. Maaaaybe two. So while setting up toolchains can be a thoroughly unpleasant experience, it's something I do once per project or so, and then I'm good for the next months or years. This vast support is nice, but rather irrelevant in practice.