The main feature of classic Arduino boards has always been a thin abstraction layer on bare metal. RPi is not that at all.
(As mentioned by the other commenter, I'm referring to their Linux boards, not the Pico)
But most people know them for their Linux boards. And that's what OC was talking about.
I don't think anyone was arguing they cared about Atmel vs ARM. In fact, the point of Arduino is to make that not even something a user would need to know.
The argument is Linux vs Bare metal Arduino are vastly different user experiences and complexities.
There are meaningful disadvantages to replacing an Arduino with even the Pi Zero.
Yeah, makers will move to Raspberry Pi products for the ecosystem and documentation, but it will be to the RP2040/2350 products.
But also the ESP32 series, particularly Adafruit's kit.
But I'm not using Arduino, so idk.
Not all platforms give you the right to do this. For example, if you buy a dev board from STM - it's only licensed for research and development. Also, because you might want to continue to sell the same thing for years, and the board designs were open-sourced, you could buy the same part for years and years. So you can continue to sell your CNC kit that uses an Mega 2560 without worrying about Arduino coming after you or that they'd discontinue that part.
With the exception of a handful of applications for their higher-end boards, I would think most of this flotilla of ships has already sailed, just on a cost basis?
Especially lately. So much more choice.
You can do gpio, pwm etc from a linux pi but the hardware is worse at it and you'll be fighting against the system quite a bit. It's a lot of boring complexity to be allowed to do something simple; and the next update might break it.
If I need a linux system AND hardware interfacing, I'll usually use a regular pi + a pico for the hardware stuff and connect them via serial or something
I’m not sure what the value proposition is overall, though. The IDE, perhaps? I never particularly saw the draw, but it clearly met the needs of some real market niche.
MCUs are lower power, have less overhead, and can perform hard real-time tasks. Most of what Arduino focuses on are MCUs. The equivalent is the Raspberry Pi Pico.
In my experience, the key thing is the library ecosystem for the C++ runtime environment. There are a large number of Arduino and third-party high-level libraries provided through their package management system that make it really easy to use sensors and other hardware without needing to write intermediate level code that uses SPI or I2C. And it all integrates and works together. The Pico C/C++ SDK is lower level and doesn’t have a good library / package management story, so you have to read vendor data sheets to figure out how to communicate with hardware and then write your own libraries.
It’s much more common for less experienced users to use MicroPython. It has a package management and library ecosystem. But it’s also harder to write anything of any complexity that fits within the small RAM available without calling gc.collect() in every other line.