But do you actually gain anything if you need to write detailed specifications? That seems just as time consuming as writing code, but less gratifying.
Code is just detailed specifications on how things should operate.
All the things in between my commits is a messy soup. Looking there is not useful to anyone. I rewrite my history with git rebase so each commit is small and atomic. The story I create with my commits is what explains why things are as they are, it doesn't matter if it's the true chronological story on how it actually happened.
I agree with the author that reviewing pull requests is too late. The problem with pull request is that they make it hard to review individual commits since they are geared towards reviewing the result of an entire branch at once. But the answer is not to share all the noise, it should be to encourage small atomic commits so you can review the early work before the entire feature/fix is complete.
It would be hard to find manufacturers to use it. None of the existing Android phone manufacturers would be able to release phones with this fork without also abandoning the official Android platform on all markets. Google are very strict with this in their tos. You cannot release devices using non official Android builds without losing your right to use GMS and Android Brandice on your other Android devices.
They mention that there are mitigations in the kernel nowadays, so the mitigations they turned off here are now redundant. But I'm uncertain if that refers to the same cve that you mention.
in Sweden we use them a lot. Most of the time they work really well and it's not like they are useless just because it gets really cold. They still help a lot even if the traditional heater element might need to kick in for short periods. It's usually not until 20 below freezing that they don't add much, but those temperatures are not a daily occurrence for most of us.
You can do this in any shell already by placing the other language in a separate executable file.
With everything in the same file the risk of ignoring the separation of concern principle (each unit should do one thing and do it well).
You can get dumb panels if you look into the b2b offerings. These are ment to be mounted in various business settings (show commercials in the checkout line in the grocery store etc). Often they don't even have any speakers, but the normal builtin speakers are crap anyway. A chromecast or android tv box and a sound system and you have yourself a smart TV setup where each part can be upgraded separately.
The downside is the price and inconvenience (as a consumer they are not easy to find). Buying a consumer grade smart tv is usually cheaper than buying the same panel as a "panel only tv".
It's available in your profile if you browse to it on a computer. The apps and mobile web does not have these setting. The profile settings are global.
You could expose your library with a plex service. Now you can play it anywhere using any plex client. You could host a web client anywhere and have it play files from your local plex service (as long as the plex service is exposed to the internet)
Code is just detailed specifications on how things should operate.