Hard no. There is such a thing as the right to forget. At least in Europe. Stackoverflow likes to take that right away as it earns them more money, but that is never a good reason.
So by your definition a real artist should have more than 1000 plays. I listen to small artist from my country which will probably never reach a global audience and they definitely do not get 1.000 plays but are verified artists according to spotify. This policy basically drives more drivel music and leaves out alternative and indie bands. It's a bad policy that needs an investigation by the authorities to force Spotify not to discriminate smaller artists.
Maybe companies, but they are not what should matter. As far as know the amount of poor people in the usa is also way higher than in Europe. If we take that into account i'd say that Europe is doing just fine.
The main thing that i remembered from thread/matter is that vendors can lock out devices and other users hostile stuff. I sure hope plain zigbee is here to stay as having bigtech decide the brand of my in-wall switches are wrong would truly suck.
The pi is largely undocumented and otherwise proprietary. It's owned by broadcom who are otherwise known for putting everything behind an nda. No, the pi is a lot, but it's not a platform i would bet on to be available in 50 years.
No, getting a 100% equivalent working Java system is trivial. But the goal is having something that looks like it was Java from the start not Java as written by a cobol expert. So proper use of classes. Not al globals. Sensible naming etc. The real cost is in maintenance of the code: having in idiomatic Java could help. Translating to idiomatic Java is very hard
I have the pleasure of supporting a transpiled rpg (system i) to Java codebase. Shit that's come up: almost everything is a global. State machine are used for crud logic which is implicit in the rpg runtime and explicit in the Java codebase. Magic constants all over the place. Magic blobs of screen configuration mapping. Transpiling and directly supporting the transpiled codebase is basically masochism.
The ultimate root of the problem is thinking healthcare works like a bakery: if the bread is too expensive i'll go shopping elsewhere or even choose something else besides bread. This last option is basically off the table in healthcare: you either get healthcare or die. Which in the usa seems to be the options indeed.
As I see it, there is no free market when it comes to healthcare: there is no real choice, only choices that we introduce. What i mean is: when I get hit by a bus, i want to be in the nearest hospital asap and don't have the time nor the consciousness to play the healthcare market game.
Where to begin...
If the schema is not there you are in the same position as with receiving some json or yaml: a bad one. Is 20230806 and integer or someones idea of sending a day?
Parsing the data into a memory structure is a one liner in any language. Assigning meaning however..
Object graph between languages as you subscribe works only in a very small number of cases. Sent your data to a mainframe and see it disappear faster than you can sent it.
Extensions is where xml shines: use an extension namespace. Hell use a namespace per plugin. Unknown namespaces are normally ignored during deserialization if you use a schema, so no line of code needed at al.
All the issues you describe boil doen in my book as: i don't know how to do this properly with xml so xml is bad.
Json is simple, but the common idiom is to read it al at once into memory and forget the difficult stuff (which encoding is this json in anyway). Then don't do the other difficult stuff (is this a string or a date type)... so it's faster (maybe) to parse but it doesn't scale for large datasets and your application will need additional deserialization logic. A broad sweeping performance statement like this is just spreading fud.
Regarding security: entity expansion bugs have been fixed long ago. In the other hand: people still use eval() on json objects to parse them. So i don't get that.
Json schema: which one? Afaik it's not there and there is no single json schema with the tooling depth and breadth of xsd.
Protobuf: nice but unreadable for humans. Might as well use corba or asn.1 coding.
Your not alone: it's verboden requiring " around anything that is a string. Commas to separate array elements. It's a technical format without the technical foundation. It's the civil engineering equivalent of building the Golden Gate Bridge out of wooden beams as that is what you have, not what you need.
At least xml has xpath ;-) the implicit Jason to object mapping has failed me on character encoding (no way to specify that in json). Stupid type errors (date/large numbers).
The main reason i avoid any typeless language is dates... how do i represent a date/time including a time zone has been badly reinvented so many times. A string type is never the way to go there in my opinion.
I've done my fair share of systems integrations and the number of teams that did not know xml or have never used it in a professional settings was around 20%. Of those who did use it a staggering amount of people never understood namespaces and started testing for equality on the element name and namespace prefix string instead of the namespace declaration. When somebody claims they "know" xml I initially treat it as a developer saying that he/she knows 'sql' while reviewing their code and seeing them do joins in the application logic.
Why? I can store it in version control. I can validate if the file has syntax errors or schema errors etc. etc. With a proper platform it's easy to generate or parse. It allows for both hierarchical structures (looking at you .ini). The only downside might be that you need a larger library to parse it. But i probably encounter xml somewhere along the line anyway due to interactions with a 3rd party system, so that point is moot.
Maybe, but if everyone starts using heat pumps we have a problem in getting enough copper in the ground everywhere on time. So even if it's temporary (20 years or so) this is still a great solution.
So we come full circle it seems. Apt update/upgrade already does this and has been doing this for a few years now. So if i drop docker and just run a container with Debian I get this with a few years of testing behind it.
Regarding carbon neutrality: yeah, by using their enourmous capital/pricing power to buy all green power relegating the rest of the country to either use greenwashed grey power or outright grey power. So learning is green, it's just the rest that is poluting....
What worked for some older think machines (haven't tried it on my thinkpad though) is to update the bios (can be to the same version) and change the serial nr.to all zeroes (the update script asks if you want that). That got rid of the wifi whitelist i encountered.
No it does not: if you google this and restrict the time to before 2021 (the learning cutoff date) you will find the same answer. Without having access to the training data it's impossible to tell what we seeing.
Uh, using /dev/disk/by-id to assemble a zfs array is pretty standard for zol. I never use device names and shuffling disks has never required any manual intervention on my part. Was this a very old ZoL?
Nobody wanted an arm laptop because it doesn't run windows/existing software. Apple bundles an is and a decent emulator for old software. If they didn't nobody would want it.