> this is just a regression that occurred during regular software development
From a cursory look, it looks like a security fix in response to a CVE surfaced a coding error which (as far as i bothered to check) has been present in the code since 2007.
This is so banal that it's actually hilarious to see people lose their shit over it. But of course nobody is talking about the actual issue but about the _hypothetical potential for issue_ introduced by potential use of AI. It's so meta i don't even know how to make sense of it.
If you have an Android box, you can set Kodi as the launcher (so the home button will always take you to Kodi home). It has a section that lists Android apps and lets you run them from there.
It's a bit backwards but I did it for years, and it works really well if you're ok with the Kodi experience.
I think the author is saying that a specific crowd, which happened to be very vocal and excited about web3 and NFTs, is also very vocal and excited about AI. In my personal experience they are right, a lot of the hustler types around me who were trying to get everyone to "invest" in digital land are now doomposting about AI.
It's not a very legible situation for people outside of the profession, and a lot of them believe it's just another grift that will blow up in a few years.
The worth is zero because the producer doesn't pay for the externalities (pollution, landfill usage etc). So essentially it is "free" because it is subsidized by everyone.
The "headache" is just : produce what you sell, sell what you produce, don't fill the world with your shit.
I think that's actually an interesting feature of society as a macro system. It is very fault tolerant, which is frustrating for any power user but without which the system as a whole would not function at all.
Next.js bundles the code and aggressively minifies it, because their base use case is to deploy on lambdas or very small servers. A static website using next would be quite optimal in terms of bundle size.
I've found this approach brings slightly better result indeed. Let the model "think" in natural language, then translate it's conclusions to Json. (Vibe checked, not benchmarked)
Someone more knowledgeable might chime in, but I don't think two corpuses can be mapped to the same vector space. Wouldn't each vector space be derived from its corpus?
From a cursory look, it looks like a security fix in response to a CVE surfaced a coding error which (as far as i bothered to check) has been present in the code since 2007.
This is so banal that it's actually hilarious to see people lose their shit over it. But of course nobody is talking about the actual issue but about the _hypothetical potential for issue_ introduced by potential use of AI. It's so meta i don't even know how to make sense of it.