The Death of Arduino?

To your reply-writer, how do you think those products came to be, many of them are productization of hobbiest projects.

The arduino project jumpstarted a whole ecosystem, but I don't that ecosystem needs arduino anymore.

[0] https://youtu.be/-zRN7XLCRhc?t=33m1s

Now this announcement where users get deprived of their copyright for anything they write by Qualcomm makes this fork more pressing.

I have a special kind of hatred for people who steal other folks work (even if it is freely given) without any acknowledgement.

It would be just desserts if Barragan teamed up with some high profile lawyers and went after Qualcomm/Arduino like the Winklewoss twins went after Mark Zuckerberg and Facebook.

Also Adafruit being a store, isnt there a matter of conflict of interest with posts like this?

As soon as it becomes a PR nightmare, they might just take that clause out.

> 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”).

> 8.2 User shall not: translate, decompile or reverse-engineer the Platform, or engage in any other activity designed to identify the algorithms and logic of the Platform’s operation, unless expressly allowed by Arduino or by applicable license agreements

So yeah, it seems like the definition of "Platform" is limited only to their hosted services.

https://docs.arduino.cc/learn/starting-guide/cores/

Stuff like https://www.adafruit.com/product/4062

The CPU cores aren't the problem (just use Hazard3) - it's all the rest, particularly the WiFi.

The RP2350 has two RISC-V cores (and two Cortex M33 cores).

Ahem. One upon a time I was the tech lead for one of the many software components in Qualcomm's GPU software stack. At one point there was customer interest in caching certain blobs of data that were relatively costly to compute, in order to reduce the startup times of a wide range of apps.

Since the caching needed to happen across different processes over time, we needed some sort of persistent storage with some metadata to track stuff like usage stats, limit storage requirements, etc. Simple stuff, right? I decided that we didn't need to reinvent the wheel, and thus suggested to the team's most recent hire to use SQLite.

Oh, Dear Lord. That was a mistake. SQLite worked great, no, no. That wasn't the issue. The problem was obtaining approval from Legal to use SQLite in our little project.

"Does SQLite have one of those viral licenses that require you to open-source your own code?" -- you may ask. No, it doesn't. It is the most lax OSS license that you could ask for. Super friendly to commercial closed-source projects.

No, the obstacle was that Legal wanted to audit SQLite line by line, down to the books and research that was mentioned in the comments, searching for anything from copyright infringement within SQLite itself, to patents that may be associated with any of its features. IIRC, it was going to take months and would require approval by my management chain. And any time we wanted to upgrade the version of SQLite we shipped with would require another extensive review.

The feature was canned unceremoniously. Fin.

For the rest of the world: it's a children cartoon with a grandpa beaver telling stories to his grandchildren, and has been immensely popular for decades.

So yeah, please do! War stories are always cool

Turns out a kernel is just a kernel after all, and you really do want GNU+Linux, not just Linux.

It was launched without NDK, which only came later in Android 2.0 after pressure from game developers, and to work around Dalvik being a primitive VM, thus NDK has always explicitly listed NDK use cases and nothing else.

It is the rest of the community that built false hope that only because it uses the Linux kernel, the NDK should offer more than it does.

Even the Android IoT project that initially started withouth the Java userland with the target to use a C++ based alternative instead (Brillo) didn't last long, and the final version Android Things, even required writing the device drivers in Java.

By the way, Trello drivers are language agnostic, talk via Android IPC with the kernel, and some of them are indeed Java based.

What happens as a result of this is that someone spends a lot of time tinkering and then they think they know what they are doing. With that confidence, they might apply for a job or take on a more dangerous project. The job will say they don't actually have the skill, even though they have been putting in the time. And the overconfidence could lead to trying to do more dangerous things than they should on projects.

A tinkering culture is fine, but it needs to have safety and skill progression as its foundation. Most Maker Spaces I have been to have done a good job trying to keep things safe, but ultimately, people are people.