Many eons ago before the Arduino came out, I used to have EE labs in university based on the same Atmega chip but using a commercial IDE-compiler, and boy was that a giant PITA as a young buck, having to read dozens of datasheet pages, calculate by hand all the register values just to get a bloody 1 ms PWM timer output on a pin, which never worked the first time and needed an oscilloscope to debug.
"Oh, you did everything right, but forgot to flip the bit of the correct pin of the output port in the right registry, have fun debugging it for the next 3 hours while you pull your hair out."
And we used "modern" C, not AVR assembly (which is still nice and quite simple to understand once you get the hang of it, don't get me wrong). Sure, as an EE, that was a mandatory right of passage to prep you for a job in the industry, but not something average people would want to do as a hobby.
The fact that you can do that with 2 simple lines of code, from an API, from a well documented library, that's well tested and guaranteed to work, without an expensive commercial toolchain and HW debugger, was the game changer for the hobbyist market.
But this move feels a bit late in the game for them. They should have done this nearly 10 years ago, but now it feels like they squandered their early lead and became sort of irelevant amongst the sea of RPi, ESP32, STM32 with their own easy to use toolchains and libraries.
Interesting. Personally I find the $OFFICIAL_IDE repulsive, and strongly prefer just writing the code in $MY_IDE, with a Makefile on the side. OTOH I find the "branded" hardware attractive: it's a known quality in an ecosystem that I sometimes find complex and confusing, and I greatly appreciate the work they've put into making the whole process more approachable. Of course I have a couple clone boards at hand, but I will buy branded Arduino by default precisely because I instinctively associate the brand with less hassle.
< Insert famous HN comment, on why Dropbox is a useless business idea, berceuse you can easily achieve that for free with a self hosted FTP server[1] >
If you know what a Makefile is, then you're not Arduino's target market, but there are millions of people out there who want to turn a relay ON when some sensor gets too hot for some garage project, without first learning about Makefiles or registers.
I am arduino targey market and I know makefiles, I hate them with a passion. One must know his enemies better than he knows himself
I honestly don't see how such strategies work long-term though. As a former embedded SW engineer, the Arduino IDE seems very toy-like - which is excellent for people just starting out, but not something a company developing an embedded product is likely to use. I think PlatformIO is similar but I have only tried that once.
If these companies try to get vendors to pay them to support their boards, or try to start charging users directly, I really think that the hobby community will move on and someone will fork or create their own solution, and the whole cycle will start again.
Platformio is a package manager for embedded systems
That phrase encompasses a huge amount of value. VS Code+PlatformIO is free but I would happily pay for it. I was already paying for an Arduino Visual Studio plugin (Visual Micros) before I learned about it.
I've used to maintain my own set of Makefiles for AVR, and that was mostly OK because avr-gcc is in ubuntu repos, and all my computers are Ubuntu anyway.
But when I switched to ESP8266, this no longer worked, there are no nice debs with SDKs I could find. I could have created a complex set of Makefiles to download SDKs, compilers and tools.. but I switched to platformio instead to do it all for me.
This turned out to be a great idea when I later wanted to try STM8 and RP2040 - just 2 line change in ini file and you have a fully working toolchain, libraries, etc.. And the ability to easily share the programs with others and to know that they can use them even if they don't run Ubuntu is great too.