What I don't get, which this article doesn't talk about, why would Apple’s Virtualization.framework expose a lesser Metal profile instead of reporting all capabilities supported by the host GPU?
I work in big-tech and we’re only allowed to use our companies internal tools that mimic Claude Code etc. There is certainly a push to use it, and I’ve noticed a significant increase in bugs that have come along. There are so many PRs now that no one reviews them and just slaps a LGTM. Specifically with junior or less strong engineers. It’s like they don’t code anymore and push everything on the AI and say ship it without a second thought. I’ve watched engineers push AI code with a nasty NPE and then they also had it write unit tests where the AI caught the NPE and passed the test. Literally if anyone spent the time reading the code you’d see it was a ticking bomb. We went from production breakages every couple of months to every couple of days.
It’s so bad but no one is saying the hard thing that less strong engineers need to be restricted on their use of these tools.
Huge caveat to hosting this server publicly is the codebase will accept any websocket connection to the /{connection_id} route. The author gives a small warning about implementing authentication in the README, but it essentially makes the project extremely dangerous to deploy as any person can use your domain to host their content.
Isn’t the whole reason the lawsuit started because the Internet Archive went above an own-to-loan ratio of 1? This blog post completely leaves this detail out and makes it seem they were always only doing 1 physical copy to 1 digital copy which is not true.