PlatformIO is just cool. Let me switch from Arduino IDE. Also, it provides great CLI tool so that it could be well integrated with other IDEs/Editors. Since I am a VS Code fan, so I could leverage the good CLI and build a PlatformIO extension for VS Code: https://marketplace.visualstudio.com/items?itemName=formulah...
PlatformIO, open source ecosystem for IoT
21–30 of 38 posts
Re: PlatformIO, open source ecosystem for IoT
#22PlatformIO is great. If you want to do serious work, and not just mess around with Arduino, it provides a great ecosystem and excellent tooling. No custom IDE necessary.
I especially love the library management part. There's no versioning, but it's really helpful to be able to just list your libraries and have them be automatically downloaded and linked to your executable.
I love and use PlatformIO, but I've dumped their library system because often the libraries in the pio db are a version or two behind what I can get from github.
Re: PlatformIO, open source ecosystem for IoT
#23Earlier quoted context omitted.
I especially love the library management part. There's no versioning, but it's really helpful to be able to just list your libraries and have them be automatically downloaded and linked to your executable.
I love and use PlatformIO, but I've dumped their library system because often the libraries in the pio db are a version or two behind what I can get from github.
It depends on a library manifest (library.json, library.properties or module.json). If library's author updates "version" field, then PIO Library Crawler will update it in a registry.
Please note that you can manually update manifest and make PR to author's repository. Click on "Manifest" tab when looking at a library in Web Registry and you will see "Edit" button.
Re: PlatformIO, open source ecosystem for IoT
#24Happy user here as well. Doing Arduino/ESP8266 development using macOS host. PlatformIO is a fresh breeze for embedded development.
I've been using https://github.com/SuperHouse/esp-open-rtos. Who exactly is the target audience for PlatformIO?
Re: PlatformIO, open source ecosystem for IoT
#25Earlier quoted context omitted.
I agree. I've been in a row with their founder over the same criticism you offer. PlatformIO is really nice and smooth and seamless, as long as you do exactly what they think you should be doing. It would be a great product if it un-bundled all the functions. Of course that would make it not-really-a-product, and they couldn't charge money for it as easily. But instead it's a monolith that offers you little wiggle-ro…
> It would be a great product if it un-bundled all the functions. Of course that would make it not-really-a-product, and they couldn't charge money for it as easily. But instead it's a monolith that offers you little wiggle-room. Could you explain in details? Do you know that you can create own development platform or add support for new embedded board wihout our support? - http://docs.platformio.org/en/latest/platfo…
> Could you explain in details?
Mayb ein a separate post. That's a lot details :-)
> Do you know that you can create own development platform or add support for new embedded board wihout our support?
But you would still force me to use PlatformIO as my build system, correct?
Now, assuming I accepted that:
How much effort is it for someone who doesn't know PlatformIO that well, doesn't know (or car about) SCons? Is it more or less effort than just using make/cmake/build system of my choice instead?
Can I be certain that I won't find out too late that I'm now locked in somehow? Are its processes truly flexible enough for what I need, and might need in the future?
Can I even (with reasonable effort) create new commands (e.g. platformio static_code_analysis) to shape PlatformIO to my needs?
> Yes, PIO Core 2.0 was monolitic. We rewrote it from scratch and announced decentrizlied PIO Core 3.0
Nice. Can you give me a quick pointer on how to just use the uploader portion of PlatformIO given I already have binaries at some location?
> Which framework/workflow do you use for unit testing?
The one that makes the most sense. If I get to pick, I like to use Catch. But since the decision tends to have already been made for me (through existing test suites, or coworker's preferences), I use whichever is most practical.
Or even several in parallel, as is the case on my current project.
Re: PlatformIO, open source ecosystem for IoT
#26Earlier quoted context omitted.
I agree. I've been in a row with their founder over the same criticism you offer. PlatformIO is really nice and smooth and seamless, as long as you do exactly what they think you should be doing. It would be a great product if it un-bundled all the functions. Of course that would make it not-really-a-product, and they couldn't charge money for it as easily. But instead it's a monolith that offers you little wiggle-ro…
> It would be a great product if it un-bundled all the functions. Of course that would make it not-really-a-product, and they couldn't charge money for it as easily. But instead it's a monolith that offers you little wiggle-room. Could you explain in details? Do you know that you can create own development platform or add support for new embedded board wihout our support? - http://docs.platformio.org/en/latest/platfo…
BTW, looking at the documentation: it seems that unit testing is reserved for the paid version PlatformIO plus.
Free users don't get to unit test? Ivan, please tell me I'm misreading this.
Re: PlatformIO, open source ecosystem for IoT
#27Earlier quoted context omitted.
I especially love the library management part. There's no versioning, but it's really helpful to be able to just list your libraries and have them be automatically downloaded and linked to your executable.
> I especially love the library management part. There's no versioning It is! :) http://docs.platformio.org/en/latest/librarymanager/index.ht...
Oh, you added it? Fantastic, I love all the great work you do on PlatformIO.
Re: PlatformIO, open source ecosystem for IoT
#28Earlier quoted context omitted.
I especially love the library management part. There's no versioning, but it's really helpful to be able to just list your libraries and have them be automatically downloaded and linked to your executable.
I love and use PlatformIO, but I've dumped their library system because often the libraries in the pio db are a version or two behind what I can get from github.
Like ikravets said, the crawler just scrapes Github, so updating the libs is just a pull request away. As a library creator, I like how integrated it is with Github, which means I don't need to upload a new version of my library anywhere, I just need to remember to change the version in the JSON.
Re: PlatformIO, open source ecosystem for IoT
#29Happy user here as well. Doing Arduino/ESP8266 development using macOS host. PlatformIO is a fresh breeze for embedded development.
I've been using https://github.com/SuperHouse/esp-open-rtos . Who exactly is the target audience for PlatformIO?
Compare the 'Quick Start' documentation of esp-open-tool to ´brew install platformio´, ´platformio init´. That's pretty much the point of PlatformIO, I guess.
Re: PlatformIO, open source ecosystem for IoT
#30Earlier quoted context omitted.
I've been using https://github.com/SuperHouse/esp-open-rtos . Who exactly is the target audience for PlatformIO?
Compare the 'Quick Start' documentation of esp-open-tool to ´brew install platformio´, ´platformio init´. That's pretty much the point of PlatformIO, I guess.
Right, but is the expectation to stay in that platform as one improves his skills?