AI agents like claude is slowly moving to config hell, as we often see in deployment pipelines, project setup etc. This is always a neverending timesink, and because of AI can/will probably need to be altered very frequently.
In the end it will still produce slop you need to review line by line.
The question is: Do you want to write code you know and verified that works, or review code written by AI that is of junior dev quality that is not verified.
Right! ed was the first one, and its ideas and commands influenced sed (a "streams" ed), and ex (an "extended" editor, which also had a "vi"sual mode).
With all due respect, I'm fairly sure that anyone using "VM" the same way as you do here really think of it as a container or what.
It's a runtime, and go also has a similar, fairly fat runtime. It's just burnt into the binary instead of being shipped separately. (Hell, even Rust has a runtime, it's just very very lean compared to languages featuring a full GC like go and java)
What started in Ukraine, this is modern warfare. Like most "consumer" goods that are mass produced, you can now get a capable strike force for peanuts.
The russians have taken close to 1.5 million casulties because ukraine engineering for cheap drones. Putin really, really f-ed up his "3 day military operation".
VAC is actually an AI based anticheat. I guess IF (a big if) it ever gets good enough it will be better than any kernel level AC, because it analyzes the gameplay, not the inputs, meaning a DMA cheat would also be caught.
"VAC" is a catch-all term for all of Valve's anti-cheating mechanisms.
The primary one is a standard user-mode software module, that does traditional scanning.
The AI mechanism you're referring to is these days referred to as "VAC Live" (previously, VACNet). The primary game it is deployed on is Counter-Strike 2. From what we understand, it is a very game-dependent stack, so it is not universally deploy-able.
I don't think that's what VAC is. I think VAC just looks for known cheat patterns in memory and such, and if it finds indisputable proof of cheating it marks a player for banning in the next wave. Maybe there is some ML involved in finding these patterns but I think it's very strictly controlled by humans to prevent fase positives. That's why VAC bans are irreversible, false positives are supposed to be impossible.
Valve has some AI detection stuff for CS2, but it’s remarkably ineffective. VAC itself delivers small DLLs that get manual mapped by Steam service, do some analysis and send that to Valve (at least to the best of my knowledge, there may be more logic implemented in Valve’s games or in Steam/Steam service).
This is pretty lame. I WANT to write code, something that has a formal definition and express my ideas in THAT, not some adhoc pseudo english an LLM then puts the cowboy hat on and does what the hotness of the week is.
Programming is in the end math, the model is defined and, when done correctly follows common laws.
In the end it will still produce slop you need to review line by line.
The question is: Do you want to write code you know and verified that works, or review code written by AI that is of junior dev quality that is not verified.
reply