I think it's a bit iffy to argue that the bootloader code is covered by the GPLv3. In programs for standard computers running a big OS, the distinction lies in whether you are linking a library into your program. If the GPL code isn't a library but an external program, it isn't linking, and OK by the GPL. Now on to the bootloader code: in order to flash your device you have to put everything into a single image file. I guess the claim is that this process constitutes linking. But I don't think that is how most people think. Some possible arguments:
When linking, symbols pointing to addresses are involved. The main program calls functions in the library, and you end up with a whole program. On the other hand, a bootloader just does its thing and then jumps to a fixed address in the main program. The main program doesn't call anything in the bootloader. (Note, the Linux kernel has a special clause that explicitly allows the userland to programmatically interface with the kernel.)
I realize this sort of depends on the microcontroller toolchain. I'm familiar with a few, but not much with STM32 stuff. If the toolchain is dumb and implements the bootloader in a way that resembles linking, i.e. making it possible to resolve all the symbols in the bootloader from the main program then it could very well make the bootloader subject to the GPL.
Even as far as linking goes... If you're not actually deriving from the code in a copyright sense then the GPL is limited in what it can demand. The advice from the FSF on linking is not exactly unbiased. The part about the intimacy of the communication between pieces of code seems a lot more solidly based in copyright law.
IIRC this was talked about in Cory Doctorow's Enshittification book.
Here's my bookmarklet to get rid of sponsored results, it's survived a couple years:
A while ago I learned that very early versions of 3.5" floppies didn't have the auto shutter mechanism and you had to open and close the shutter manually. (I think that was probably just used on some Japanese Sony machines.)
Interesting! I tried to find a demonstration of the manual shutter. This is the closest thing I’ve been able to find. Apparently, it was one of the earliest Sony models to feature a semi-automatic shutter.
In the end I wasn't able to read it on my ebook reader and reading it on a PC or smartphone kinda makes it annoying to read on the commute. So I've only read the first two chapters or so but it seemed like a lot of fun. All this talk about using Lean in AI-powered proofs kinda makes me want to pick it up again.
If you want to make all developers working on a project happy about the way the project is being designed/implemented, it's best to reduce the number of developers to 1 or less.
No, it is impossible to keep them. Computers are not that far advanced yet. The melodies can only be played by pressing a button located at the end of the train.
My line lost its departure melodies in March this year :/
We should get our top frontier models on the task. Perhaps they can devise a motorized finger contraption to push the button without human intervention.
Basically it just clusters same characters and asks the human to find the problems, which is easy when you're looking at a series of pictures like ssssss5sss.
The UI is kinda least-effort. Should ask a modern AI agent to make it look nice and intuitive, sometime maybe.
