Because there are liabilities issues for others. What if your structure falls down on visitors? You cant repair some heath damage or death. Since this kind of problems is easily prevented by professional review, legal constraints make lots of sense.
Actually the accident is more that it became so successful for embedded computers in professional environments (factories, logistics etc.). This contributed to the lack of availability around the COVID crisis and opened opportunities for competitors to appear and gain rapid market share.
Surely you aren’t talking about Android as “open source”. To a first approximation no one wants a phone running only AOSP without Google’s proprietary parts.
You're free to use the same Android that the Chinese OEMs (and Amazon) built their phones on yourself, without traveling to China. It's true that a reasonable definition of "no one" wanted Amazon's phones, but a much more lenient definition has to be used for the Chinese OEMs.
No APIs have been moved out of AOSP. Google Play Services is itself built on top of AOSP. If you mean they removed the email client, that's because there are now other open source email clients that are much better.
Around here it's usually a lot harder to get open source software approved with IT because they tend to dislike products where they can't call a compant. Licensing is easier of course, but for a lot of software licensing is virtually automatic. With Docker it's billed by the amount of people in the Docker AD group, and it tells EU tax deductable automatically.
Not that this should be an argument for docker. The idea that having someone to call makes a piece of software "safer" is as ridiculous at it sounds. Especially if you've ever tried "calling" a company you buy 20 licenses from, and when I say call what I really mean is talking with a chatbot and then waiting a month for them to get back to you via email. But IT's gonna IT.
That assumes that you can, in fact, install that software in the first place. "Developers" sometimes get a bit of a pass, but I've been inside more than a few companies where... no one could install anything at all, regardless of whether there was a cost. Requesting some software would usually get someone with too much time on their hands (who would also complain about being overworked) asking what you need, why you need it, why you didn't try something else, do you really need it, etc. In some scenarios the 'free' works against, because "there's no support". I was seeing this as late as 2019 at a company - it felt like being back in 1997.
At work I need often smaller, short lived scripts to find this or that insight, or to use visualization to render some data and I find LLMs very useful at that.
A non coding topic, but recently I had difficulty articulating a summarized state of a complex project, so I spoke 2 min in the microphone and it gave me a pretty good list of accomplishments, todos and open points.
Some colleagues have found them useful for modernizing dependencies of micro services or to help getting a head start on unit test coverage for web apps. All kinds of grunt work that’s not really complex but just really moves quite some text.
I agree it’s not life changing, but a nice help when needed.
You need to ask a contractor to check your roof orientation and potential shade sources (trees, big mountain? You should be aware about those already). Other factors are pretty much not relevant. Also remember that light, not sun shine, matters. Light clouds might still allow the panels to work very efficiently.
