Live data from Hacker News

PlatformIO, open source ecosystem for IoT

platformio.org

31–38 of 38 posts

Re: PlatformIO, open source ecosystem for IoT

#31
post #8

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 need to bother with make/cmake/build scripts/toolchains/upload tools and other things... Just tell PIO which board (currently, we support ~370 different boards/architectures/mcu) do you want to use and PIO will do all complicated work for you automatically.

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.

Re: PlatformIO, open source ecosystem for IoT

#32
post #6

One major error in principle is that PlatformIO will infiltrate an existing Atom installation. PlatformIO can not be installed in parallel (as far as I know) and it will not warn before doing serious changes to your nicely nurtured Atom configuration.

I'm guessing you mean the PlatformIO editor, which is different from PlatformIO itself. You can install PlatformIO without installing the editor at all, which is entirely how I use it.

Yeah sure but Atom is one of the most intriguing parts of PlatformIO, especially if you want a better alternative to the shitty Arduino Editor...

Re: PlatformIO, open source ecosystem for IoT

#33

Earlier quoted context omitted.

> 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 need to bother with make/cmake/build scripts/toolchains/upload tools and other things... Just tell PIO which board (currently, we support ~370 different boards/architectures/mcu) do you want to use and PIO will do all complicated work for you automatically. 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 --…

Dear Luca,

We don't force you to use PlatformIO. If you like manually manage build scripts, toolchains, etc. and understand how to do that, you can switch PlatformIO to your own build system. I remember that I already explained to you how to do that (own `build_script` entry within PIO build environment).

> There's another argument though: Usually I need only one board. Maaaaybe two.

Thanks, I've heard your feedback. PIO is intended for developers who don't want to focus on the 1 board for 1 year. We don't live in 90-th, today each month we have new boards, MCUs, connectivity solutions, etc. PIO allows you an easy switch between them. If you don't know at 100% which hardware do you need for the next 1 year, PIO is the excellent tool here. You can experiment with dozens of boards and find better hardware according to the project requirements. They cost a few $$$ today.

Stay tuned for our news. We are working on the very interesting things which will be announced soon.

Re: PlatformIO, open source ecosystem for IoT

#34

Earlier quoted context omitted.

> You need to bother with make/cmake/build scripts/toolchains/upload tools and other things... Just tell PIO which board (currently, we support ~370 different boards/architectures/mcu) do you want to use and PIO will do all complicated work for you automatically. 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 --…

Dear Luca, We don't force you to use PlatformIO. If you like manually manage build scripts, toolchains, etc. and understand how to do that, you can switch PlatformIO to your own build system. I remember that I already explained to you how to do that (own `build_script` entry within PIO build environment). > There's another argument though: Usually I need only one board. Maaaaybe two. Thanks, I've heard your feedback.…

> If you don't know at 100% which hardware do you need for the next 1 year, PIO is the excellent tool here

Actually, no.

That was one of the points I was trying to make. Beause I have to trust you that PlatformIO works well enough on all 370 boards. And I won't know until I try, by which time I'm already deeply invested in PlatformIO.

Re: PlatformIO, open source ecosystem for IoT

#35

Earlier quoted context omitted.

> You need to bother with make/cmake/build scripts/toolchains/upload tools and other things... Just tell PIO which board (currently, we support ~370 different boards/architectures/mcu) do you want to use and PIO will do all complicated work for you automatically. 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 --…

Dear Luca, We don't force you to use PlatformIO. If you like manually manage build scripts, toolchains, etc. and understand how to do that, you can switch PlatformIO to your own build system. I remember that I already explained to you how to do that (own `build_script` entry within PIO build environment). > There's another argument though: Usually I need only one board. Maaaaybe two. Thanks, I've heard your feedback.…

> I remember that I already explained to you how to do that (own `build_script` entry within PIO build environment).

Yes, I vaguely remember. I think it was before 3.0 came out?

It's been a while, but IIRC it didn't feel like build_script was a good solution for me.

IIRC you said you were going to improve the documentation. I shall re-read it. Maybe it makes more sense to me now, and I'll change my opinion.

> Stay tuned for our news. We are working on the very interesting things which will be announced soon.

I'll be watching with interest.

Re: PlatformIO, open source ecosystem for IoT

#36
I work with Arduino on ESP chips.

I could not imagine embedded development without PlatformIO. With just so many types of hardware, each having slight dofferences and intricacies, it quickly becomes wasteful to use individual solutions. PlatformIO accomplishes so many goals at once, I am deeply grateful for this product!

Re: PlatformIO, open source ecosystem for IoT

#37
post #30
post #29

Earlier quoted context omitted.

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?

I don't know. Personally, embedded programming is a hobby for me. As a long time unix user, I've no problems with complex development environment setups, but if there exists a scripted, tested, and mainained alternative, I'll probably prefer that, because I don't want to recall the configuration details for every platform I program on (esp. if it's non-daily activity).

Re: PlatformIO, open source ecosystem for IoT

#38
post #32

Earlier quoted context omitted.

I'm guessing you mean the PlatformIO editor, which is different from PlatformIO itself. You can install PlatformIO without installing the editor at all, which is entirely how I use it.

Yeah sure but Atom is one of the most intriguing parts of PlatformIO, especially if you want a better alternative to the shitty Arduino Editor...

On what planet is the Atom part the most intriguing part? Having one interface to all the stupid build chains and libraries is the point for me. Next up the freedom to use a proper editor - any editor. Not that POS Arduino thing.
Post reply on HN