Yep, that made sense when it was a "mere" microcontroller, but in computerland it's not the best option. Actually it's bad. There are add-ons that can be attached, but I doubt you can stuff them in there.
Indeed. However the root problem were CPU and other hw drivers AFAIK, not Google. Making their own SoC made it possible to bypass those greedy manufacturers and extend support.
Please don't give them ideas. They have to fix core issue first - catalogue quality where albums from same named bands are often attributed to wrong ones.
I don't think those are the problem, but rather how they are used. And in case of managed languages like C#, it's almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷♂️
They might work, but then one is bound to be online. Also different computers might have different configurations and that is something to pay attention to as well. Alternative is a synchronisation to source (nextcloud sounds a good fit) but then you might bump to synchronisation conflicts and such. Both ways will produce a lot of traffic unless you redirect creation of build artifacts to a local directory. Which might not be always possible.
A remote machine might not be always possible, such as when you develop mobile apps or when you have more than one monitor available. Sadly all options have problems. And (auto) pushing is not an option when you work on a team project where pushing non compilable code is not a welcome option.
Cars are probably covered differently by law, like minimum years producer has to offer replacement parts and such. Probably all boils down to the contract for that exoskeleton.
Definitely not an excuse for that petty company trying to suck tens of thousands of dollars instead of a simple repair.
C# is awesome, however it has one big issue when it comes to games - garbage collection that can start at any moment and you have no control over it. There are ways to workaround but none is 100%. OTOH from similar level languages there is Swift that does reference counting instead and doesn't have this problem, albeit has a reference counting problem (where cyclic reference would create a memory leak, but this problem is solvable).
Bring back NNTP!