The article clearly points out that it wasn't autism for which Mei was treated, but Snijders Blok–Campeau syndrome, of which autism is just a single symptom. That goes way beyond neurodivergency.
I feel like the quickstart is missing something. It's referring to its tech blog for actual benchmarks, but K3 isn't mentioned on there, the last thing on that blog was K2.6, 2 releases ago.
Food tends to be a lot easier to produce, and many countries do often subsidize their food production, as well as have mercantilistic policies to ensure food production is kept locally.
Vaccines is a more interesting one, and would be something that might indeed be of interest to a nation. On the other hand I don't think many governments are that concerned about another pandemic, sometimes the discourse regarding it very much sounds like "what are the odds it'll happen again"
It's probably not a bad idea. Steel is one of the things that an industrialized country needs to produce to protect its own sovereignty. Letting it shut down and just hope you'll always be able to import enough steel from other countries is a bad long-term strategy. You'd be left unable to fend for yourself.
For your first two questions, I can't recommend Crafting Interpreters enough, it's probably one of the best entry-level books that goes into that entire process.
This entire issue is a disaster of a Github issue. It looks like its on the entirely wrong repository. I did eventually find the text in another repository; the one for the Android reference implementation: https://github.com/eu-digital-identity-wallet/av-app-android...
It was removed from there to clarify the entire "Hey, this application is not done yet"
It being in the reference implementation instead of the spec is a massive difference. One means that it's just there to show an example, and we should push national governments to do it better in their implementations, while the other would mean that it'd be a requirement for all implementations, which it doesn't appear to be.
When I last played with it checking out its capabilities, I found the thing I was mostly missing to really make use of it was the thing referenced in this article, the Component Model. Without a type model and binary specifications, interop was made a lot harder than it'd have been otherwise. Now that that's in, it becomes a lot more useful.
I was mostly looking at it for its state as being a cross-platform supported output platform of bytecode that's fairly well sandboxed. That makes it an excellent target for things like running untrusted plugins in an application in a performant manner.
I'm going to be honest, this very much reads like an exciting new way to burn up as many tokens as possible. Large amounts of parallel agents that all have all their work double-checked by multiple other agents, and that keeps running for a longer period of time?
I feel like there are more efficient ways to tackle the issues given.
I don't know about that. I don't think it'd have been a major issue in the country if it were a Belgian or German takeover. It may still not have been desirable, but I doubt the government would have stepped in like they did here.
The issue was less privacy concerns, and more "hey lets not hand over one of the most critical pieces of infrastructure to a potentially hostile state". DigID is the user authentication platform for basically every government site in The Netherlands. A foreign government could use sanctions to pressure Dutch individuals to comply by limiting access to it.
That factoid always hides the real issue. The biggest reason that that factoid is true is that the 100 biggest companies includes a large amount of the fossil fuel industry, and that that industry produces most emissions in the world. A company like Saudi Aramco produce 4% of global emissions.
We need to reduce our dependency on fossil fuels.
For full clarity, it's also not the 100 biggest corporations that produce most emissions, but the 100 biggest companies. A massive amount of the global emissions are done by state-owned companies.
Let's be real, a lot of organizations never actually finish that R&D phase, and just continue iterating on their prototypes, and try to untangle the spaghetti for years.
I recently had to rewrite a part of such a prototype that had 15 years of development on it, which was a massive headache. One of the most useful things I used LLMs for was asking it to compare the rewritten functionality with the old one, and find potential differences. While I was busy refactoring and redesigning the underlying architecture, I then sometimes was pinged by the LLM to investigate a potential difference. It sometimes included false positives, but it did help me spot small details that otherwise would have taken quite a while of debugging.
Thankfully they are actively working towards upgrading, Unity 6.8 (they're currently on 6.4) is supposed to move fully towards CoreCLR, and removing Mono. We'll then finally be able to move to C# 14 (from C# 9, which came out in 2020), as well as use newer .NET functionality.
For .NET only the old legacy .NET Framework, SqlClient was moved to a separate package with the rewrite (from System.Data.SqlClient to Microsoft.Data.SqlClient). They realized that it was a rather bad idea to have that baked in to your main runtime, as it complicates your updates.