https://blog.arduino.cc/2025/11/21/the-arduino-terms-of-serv...
I'm not saying the person(s) who wrote that is(are) lying. It's just that it doesn't seem to come from someone with authority to make decisions like that or even from someone well informed about the global strategy of the corporation.
To me "Arduino Team" is just a bunch of hopeful or even naive employees.
> 1.1 The Site is part of the platform developed and managed by Arduino, which allows users to take part in the discussions on the Arduino forum, the Arduino blog, the Arduino User Group, the Arduino Discord channel, and the Arduino Project Hub, and to access the Arduino main website, subsites, Arduino Cloud, Arduino Courses, Arduino Certifications, Arduino Docs, the Arduino EDU kit sites to release works within the Contributor License Agreement program, and to further develop the Arduino open source ecosystem (collectively, the “Platform”). The use of the Site, the Platform, and the Services is governed by these Terms including the other documents and policies made available on the Platform by Arduino.Certifications, Arduino Docs, the Arduino EDU kit sites to release works within the Contributor License Agreement program, and to further develop the Arduino open source ecosystem (collectively, the “Platform”). The use of the Site, the Platform, and the Services is governed by these Terms including the other documents and policies made available on the Platform by Arduino.
That list in 1.1 isn’t an exhaustive definition which is IMO, one of the causes of the fire. Again, "IMO", the list is an illustrative set of examples as there is no limiting language like "solely" or "only" and the clause even mixes services and purposes, which again signals it’s descriptive rather than definitive.
Saying that, whilst the list inside the definition of "the Platform" is illustrative, the category it defines seems scoped to Arduino-hosted online properties which could be argued is the intent. But its an argument alas...
Either way, ambiguous policy is being communicated by these T+C updates and that is a real problem.
"But Arduino isn’t SaaS. It’s the foundation of the maker ecosystem." is a giveaway, but the whole set of paragraphs of setup before that is chatgpt's style
Not a lawyer obviously - but lets see how this plays out.
> This means Qualcomm could potentially assert patents against your projects if you built them using Arduino tools, Arduino examples, or Arduino-compatible hardware.
Yep, the complete opposite of "open".
This is a reminder - never sell out your baby unless you're willing to see it squeezed for every penny, community be damned.
https://arduinohistory.github.io
https://hackaday.com/2016/03/04/wiring-was-arduino-before-ar...
The Arduino HAL and the overall comfort of the Arduino IDE are genuinely valuable. I didn’t have to learn new flashing tools or a new debugging toolchain just to light a few LEDs, read some buttons, and emulate keypresses on a PC. The learning curve was basically zero.
I’ve worked with embedded systems before, and this level of simplicity is incredibly useful for people who just want to ship simple solutions to simple problems without fighting through vendor-specific, arcane tooling.
I've got some RP2350s since then with Micropython, now those might be even better for getting stuff done (without network or extreme low power needs)
Other reasons I'll reach for an Arduino over alternatives like ESP, RasPi (Linux or 2040/2350) include:
Simplicity. I very much ascribe to KISS. Having WiFi or Linux as part of my hardware _always_ leads me into scope creep. If the idea could be done on an AT328 (or similar), in my head it _needs_ to be.
Robustness. I probably have thrown out dozens of 3.3V microcontrollers/SOCs with dead io pins because I fucked up. An Arduino will often shrug off shorting 12V to an io pin (or even vcc) without blinking. RasPis seem to sometimes get damaged just because you looked sideways at them while thinking about 12V.
Experience. For me, the way I come up with project ideas seems to often be fundamentally linked with "knowing" how I'll do it on an Arduino. I've been using them over 20 years now, practically since they first appeared. And I'd been writing code for ATMega chips since a Burningman project in 1999, struggling with a cross compiling gcc toolchain. Arduino IDE was both instantly familiar, and such a breath of fresh air for me back then. It allowed me to easily experiment, and lowered my barrier of entry to random weekend or evening project ideas.
Separateness from work. I find the low level coding on a bare 8 bit microcontroller to be almost a completely different thing to coding for work. When work is going badly and I'm approaching burnout, any personal time Linux based coding for RasPis pretty much grinds to a halt. I'll find myself reading a book or doomscrolling social media instead of tinkering with that kind of project. The Arduino IDE is different enough to "work tools" that it doesnt get affected quite as
I have dozens of Arduinos that I will never use.
With a similarly priced (sometimes cheaper) platform like the amazing rp2040 / rp2350 which is roughly 100 times more powerful, I have no idea what the niche is for them any more.
The way they dropped the ball with their IDE is amazing. It still looks and feels like something that was rejected during beta testing in 1993
Arduino is following roughly the same trajectory as BlackBerry, with the current phase being "rapidly fading into obscurity"
Indie devs who need testable builds might be a smaller market than tinkerers, but they're there.
It's a pain anticipating money flow into the future in more ways than one.
I semi-attribute this to my lack of willpower but perhaps arduino also isn't as tinker-epic as I thought it may be.
But take a room full of kids and get them to write a program that blinks an LED, or drive a simple 'robot' forward, and it's awesome. Easy to use. I've never burned out a board (even driving considerable current through them). Things are tolerably well marked. Lots of teaching tools. Lots of different suppliers of easy to connect motors, servos, lights, sensors, etc.
For the same reason, if you are not an embedded engineer, but need a simple micro-controller to turn something on an off like a heater in a chicken coop, it's fantastic. And if you want, buy the $5 knock-off Uno. It should be the same, except that it doesn't support the (now defunct) foundation.
It's true that you can (and always could) use avr-gcc and libc, but the core sale was what makes it not this.
The "locked in"/captured API and IDE were directly extensions of a language and IDE called Processing.
Processing overlaid an art-focussed layer on top of Java, providing a simpler API, and an IDE with just two buttons.
Arduino was based on this - the same IDE format, similar API conventions (just on top of C++), precisely to allow these same artists to move into physical installations and art.
Arduino was not designed initially to be so general, it was tool written by and for this specific group of people, so has opinions and handrails that limit the space to provide the same affordances as Processing specifically.
Now, I imagine the bias pushing everyone to learn on arduino is even more intense? Who out there is programming these chips in pure C using open source compilers and bootloaders?
Edit: Of course there's other platforms like Esp32; teensy; seed. But I've only programmed Esp32s using the arduino dev environment. Are there other good ways of doing it?
I wouldn't be where I am if it wasn't for Arduino. Thank you to the OSH community for making these boards open to all back then.
Nonetheless, this looks like another step toward robbing everyone of something useful and reducing our options... not to mention encouraging others to do the same thing. Depressing.
License: GNU Affero General Public License v3.0
Who does the fork? Paging e.g. Adafruit and Sparkfun.
(I always wanted something in the middle. Some QNX-like OS in ROM, but will run without a file system. About 1-2MB of RAM.
its happy ending for both investor