Comment by MountDoom

If life is so sweet for them, why sell arduino?

Indeed, at this point, there are possibly hundreds of Arduino compatible boards, and the other pieces of the puzzle are more important. Arduino is the Python of microcontroller development.

Come for the odd little microcontroller board. Stay for the community.

and their x86 cpu's were of little value within that space

Intel could've attracted the entire retrocomputing community if they realised that the peripherals around x86 and the PC ecosystem were what got them to where they were in the first place, and made Galileo/Edison actually PC-compatible, but they ended up making a SoC with a 486DX+ core and mostly-incompatible peripherals (one would think they should've learned their lesson with the 80186/88...) and somehow convinced Microsoft to make a special version of Windows(!) for it despite a complete lack of any video output capabilities.

"WTF were they thinking!?" is the most concise summary of that fiasco.

Intel Edison/Galileo didn’t work because everything they could do is replaced by purpose built ASICs, much cheaper at scale and energy efficient, important metrics for IoT. They were at best PoC material in the lab.

> Arduino got obsoleted by the Raspberry Pi and its clones/compatible devices.

Not entirely. Arduino was always targeted at the "casual DIY" segment - artists, school robotics clubs, and other folks who wanted automation without a steep learning curve. This was a notch below the "serious hobbyist" tier where you could save a lot of money by just buying a bare-metal version of the same chip and write some code in C (or Rust). Or the pro tier, where there's way you're paying $20+ for a glorified breakout board.

Casual DIY always had a ton of inertia. It's also the reason why every other design for an analog guitar pedal or whatever is using components that are 50 years old: ancient designs are just copied-and-pasted forever. So I don't think Arduino is dead there, although other platforms are definitely eating some of their lunch.

Getting a full-fledged PC is an anti-feature for a small project. I don't want to fart around with a Linux install just to set the thing up. I don't want to worry about SD card longevity or power supply compatibility. And I definitely don't want to spend $50+. I'll buy a cheap Arduino-compatible board that will immediately run whatever code I load it with. I've built several Arduino projects and RPi would have been more annoying and much more expensive.

The RPi Pico looks great for this, but that's pretty much an Arduino equivalent. You can even used the Arduino IDE with it.

I feel like the raspberry pi pico is more of a competitor to the arduino than the raspberry pi - there's quite a few applications where having a whole linux operating system is a hindrance compared to running on bare metal, especially anything that needs real time control of signals. (Although you can get around this on the pi by connecting peripherals via USB/serial/i2c which themselves might use MCUs).

Then again, one of the more accessible (IMO) ways of using pi picos is with the arduino environment, or its cousin platformio. I do think that even if in some ways the arduino abstractions can be limiting in some ways, in practice it's often a big timesaver for more casual (and not so casual) applications. It gives you easy access to a large ecosystem of libraries across a lot of hardware platforms.

Perspective: Former college robotics team member a while ago (2022) (IEEE SoutheastCon)

I definitely see niches for both. Even if you've got some experience an Arduino uno or mega is just an atMEGA with good software support and IO headers.

We'd usually use an RPI and Arduino - connect our 'out of the box' modules to the pi, pi to arduino via uart serial, and wire arduino to the meat and potatoes. The RPI's IO was generally not as good in terms of latency but also if the wrong wire gets crossed suddenly we'd have a dead Pi but the Arduino would shrug it off.

> If you want to learn programming microcontrollers, then locking yourself into Arduino's abstractions is probably counterproductive.

Arduino isn't a pipeline from zero to professional embedded dev. It's a stepping stone, and a crucial one at that. I'd know. I'm an embedded firmware engineer. Got my first Arduino when I was 11.

Arduino's success comes from the legibility of their API and the simplicity of their tooling. It allows kids or a novice to get comfortable with core principles of the trade (GPIO, other basic peripherals, limited memory, etc) without the cognitive overhead of makefiles and JTAG adapters. You aren't getting "locked in" by anything, you're building skills that you'll need for the next step.

If all you're doing is twiddling some GPIOs, as is the case with most beginner/educational projects, RPi isn't teaching you any skills that translate to industry. So there's one niche: Arduino is a practical educational tool.

That simple tooling and API also make Arduino great for small side projects that don't demand a sophisticated uC. Once that project is finished, you can plop an ATMega328 onto a piece of perfboard with a crystal and a couple caps, and your Arduino is free to use on whatever your next project will be. Can't do that with a Pi.

Also, I'd much rather just plug an Arduino into my PC and throw some code on it, than clear off half my desk to make way for a monitor and keyboard for the Pi. Point Arduino.

Arduino is used by many professionals. It is cheap enough that you can buy it on your corporate cards and you boss won't ask many questions. As such many products start with an Ardunio based demo, and if/when the demo is a success it moves to a real company project with a real budget.

The question though is does this add value for the owners of Arduino? All too often when a project moves from the demo to real engineering (making a demo something you can sell is typically about ten times harder than the demo) you select all new hardware.