AI generated Nix is equally deterministic and repeatable. The deterministic behavior makes Nix well suited for AI yolo code, either it evaluates and builds or it doesn't, and if the result isn't functional you revert back to the previous generation.
That is the use case for NixOS yes, can you clarify how it is no longer deterministic? I have been using it for a few months and was not aware of this change
Your understanding of not-containers is incorrect.
In non-containerized applications, the data & state live outside the application, store in files, database, cache, s3, etc.
In fact, this is the only way containers can decouple programs from state — if it’s already done so by the application. But with containers you have the extra steps of setting up volumes, virtual networks, and port translation.
But I’m not surprised this has to be explained to some people in 2025, considering you probably think that a CPU is something transmitted by a series of tubes from AWS to Vercel that is made obsolete by NVidia NFTs.
Also, Instaface doesn’t need developers. Their product was completed at least a dozen years ago. And it was created by a team of a dozen or so engineers.
I think most engineers/developers/scientists would welcome, or at least be fine with, being a member of a guild like writers and actors. Their parent poster is suggesting that a traditional US union is the way, which I personally don't agree with and don't think I am unique in that regard.
To be honest, I'm not sure I know the difference. I got invited to SAG-AFTRA after doing a TV commercial and it seemed pretty union-y to me. Not that it's inherently a bad thing, and maybe I'm wrong in that there are differences but not aware of them.
Could you say more about the differences you see between a traditional US union and a modern day guild?
What I meant is that something like SAG-AFTRA provides some benefits and sets minimum standards for a work environment but does not limit your ability to negotiate a higher rate for your work, does not require promotion (whatever that would mean in this context) based on seniority, etc.
In the US, doctors, lawyers, and to some extent professional engineers and other licensed professions operate under a somewhat similar model in that they restrict supply of that class of labor through some sort of accreditation, apply minimum standards for the profession, and otherwise stay out of your business for the most part.
This is a frustrating comment. Please elaborate with a real point! Just highlighting something that used to be the case, does not imply that it should always be the case, nor does it imply that it reflects the case now.
We already have POST, PUT, and PATCH that do the exact same thing. Why not have another version of GET that looks the same as POST and is subject to personal interpretation.
FYI:
QUERY is for GET requests where the query string make the URL too long. It does this by sending a body like POST.
In the past, POST meant you were sending a body, and GET meant you received a body. And the people got religious about a pseudoacronym called REST.
Apart from the sectarian conflicts about what REST means, having a HTTP method that proxies can cache like a GET but allows bodies is pretty useful from a purely practical standpoint. You can do this with POST, but it requires proxy-specific configuration.
The point of the HTTP verbs is to communicate expected behavior. While a server could treat POST, PUT, and PATCH the same, the point of having the verbs at all is to give a standard way to signal clients what is going to happen. While a server can ignore the expectation, it doesn’t mean the expectation isn’t valuable; it allows conforming implementers to communicate what is happening using standard language.
