I wrote a bit of BASIC on my Spectrum but there was a reason they had keyword shortcuts on that keyboard. It wasn't until I got my Dragon 32 which had I proper keyboard that I really got into coding.
My dad failed his 11+ so was sent to a technical school so he actually learnt how to lay a row of bricks or how to beat out lead flashing. He did end up doing a PhD in Physics but I suspect his early school years explain why he's always been much more practical than me. My wife was a stage tech during uni so I'll happily defer to her for joinery. I can just about solder a copper pipe or big pads on a PCB.
SystemReady is already a thing. When it becomes mandatory for design wins hopefully it will become more common place.
I wouldn't say that, it's just there is a lot in vendor kernels and little incentive to upstream stuff for older SoCs that have already shipped. It's true Google has come around to the importance of not drifting too far from upstream and hopefully we are starting to see the results of that change in attitude.
As I understand it my colleges in the QC landing team @ Linaro spend a lot of time getting stuff into the various upstreams.
It really depends how you see the firmware boundary. You can either treat it as a set of magic numbers you load onto the hardware so it works or see it as an intrinsically programmable part of your system that you should be able to see the source code for or live without support for the device.
I run Circe in Emacs because it's lightweight and integrates with the modeline for not overly distracting notifications.
I've just lugged an Ampere AVA to a conference for a demo. It's a nice beefy machine and I think will finally be able to be a daily driver once I get it back home.
Self hosting takes time and energy and most open source developers join projects because they are interested in the project not becoming admins. On top of that building a CI system is an expensive undertaking when a lot of hosting solutions provide a fair amount of compute for free to qualifying projects.
If the system is SystemReady then the EFI boot chain is fairly straightforward now. My current workstation just booted off the Debian usb installer like any other pc.
It's a web of trust. If the package maintainer is doing due diligence they should at least be aware how the upstream community runs. If it's a one person passion project then it's probably possible to give the changelog and diffstata once over because things don't change that fast. Otherwise they are relying on the upstream not shipping broken stuff.
I don't think Kamikaze's came about until much later in the war. I'm sure a few heavily damaged planes went down taking targets with them though.
Why do the $20 subscription when the API pricing is much cheaper, especially if you are trying different models out. I'm currently playing about with Gemini and that's free (albeit rate limited).