To go back to my original post, my main beef is with turning an imperative language into a declarative one. If you've seen enough of these types of languages degrade, you start to see a pattern.
I don't really know what you're saying, can you say it another way? "Most realistic evolution"... why is that needed? If the problem is different database engines implementing the SQL spec differently, that's not something that can be papered over with another abstraction without a lot of wrinkles.
Pulumi serves as the strongest contender to Terraform when doing IaC (infrastructure as code). Terraform attempts to be a declarative markup language (HCL) but it has a lot of weird imperative quirks due to (understandably) trying to support common complex use cases. In the end they have a clunky custom language that tries to do what general programming languages have done well forever. Pulumi doesn't re-invent the wheel, and lets programming languages do what they do best. Pulumi only really cares that the programming language generates a declarative spec that can be used to compare with your infrastructure. It's the best of both worlds.
An admirable ideal, but declarative languages always seem to devolve towards some frankenstein imperative/declarative hybrid. We need to stop going down this path and embrace Pulumi's pattern: use existing general purpose imperative languages to generate a declarative structure. Instead, people try to take their not-mature declarative language and fit a weird general purpose language inside it.
EDIT>> I'm not suggesting that SQL needs to be declarative, only that if a problem space would benefit from declarative structures, generate them imperatively instead.
Here's EPIC's statement on why Worldcoin is a "potential privacy nightmare":
>Worldcoin is a potential privacy nightmare that offers a biometrics-dependent vision of digital identity and cryptocurrency, and would place Sam Altman’s Tools for Humanity company at the center of digital governance. Worldcoin’s approach creates serious privacy risks by bribing the poorest and most vulnerable people to turn over unchangeable biometrics like iris scans and facial recognition images in exchange for a small payout. Mass collections of biometrics like Worldcoin threaten people’s privacy on a grand scale, both if the company misuses the information it collects, and if that data is stolen. Ultimately, Worldcoin wants to become the default digital ID and a global currency without democratic buy-in at the start, that alone is a compelling reason not to turn over your biometrics, personal information, and geolocation data to a private company. We urge regulatory agencies around the world to closely scrutinize Worldcoin.
>And yet we know perfectly well that there were many people who were vaccinated who did get breakthrough infections and some of those have gone on to get long Covid, but we know that in those breakthrough cases in the vaccinated people, your chance of long Covid is further reduced perhaps by another 50 percent.
As far as I see, they aren't referencing a specific study. But they are clearly making a connection between your long covid chances and vaccination. Does anyone have a link off hand to this data?
How do you do science on LLMs? I would imagine that is super important, given their broad impact on the social fabric. But they're non-deterministic, very expensive to train, and subjective. I understand we have some benchmarks for roughly understanding a model's competence. But is there any work in the area of understanding, through repeatable experiments, why LLMs behave how they do?
I was going to post about "use a UUID", but I was surprised to learn that no UUID uses both timestamp + a random component. You can either get fully random with UUID4, or have a time + MAC based UUID with UUID1. Strange, I would have thought there would exist a UUID that uses time + random to minimize collisions like described in the post.
I was talking with a small startup founder about a project I had licensed under AGPL. He asked, "How do you know if someone uses your project against your licence though?" with a smile. His point wasn't anything new, but I still didn't have a great answer. I just said that it would require the company being honest and purchase a commercial license, and that I have personally worked at companies that evaluate their licenses to make sure they are in compliance.
But his immediate reaction being the thought of abusing the license was irritating. I can't say that I have never thought this way (of using "free" software, licenses be damned) when I was younger & in school. But as the owner of legitimate business, it seems so perverse. It screws small creators and discourages them from sharing their work with everyone.
I haven't felt the need to write my thoughts as much, but not because I have any concerns about it being used as part of some training data. Mostly it's because I don't know if I'm interacting with real people anymore.