cowboylowrez

of course not lol

yeah I've never personally used a language that when compiled, has a runtime that has a roulettes wheel chance of going hacking lol

lol I saw the exact same JIT non determinism argument on reddit. The thing is, if JIT cannot replace a hotspot with a 100 percent functionally identical snippet of code then the JIT is just in time wrong and will be either patched, repaired or orphaned.

So all of a sudden all focus is on the word "determinism", and before even going down this route you have to agree on what aspect of the subject are you declaring to be "deterministic?"

Its sort of like chatting with libertarians, as soon as you agree that taxation is theft and democracy is tyranny then all problems melt away!

right now thats my sweet spot, I want to still be able to be the llm's "dumber pair programming partner" lol

I like the idea of white listing tools and their targets. Course that means no bash access. An interesting case would be programming workloads, since big corp bots are incentivized to destroy infrastructure for "marketing points" for instance, it'd be pretty damn dodgy to let it even compile a program even if you limitted it to certain files because it'll just write a program to bypass. So an extra step in my thought experiment for c programming tasks is to disallow header incusion and the like by never letting it write a main() or call anything in stdio or whatever that thing is called. I mean why would a coding bot be bothered to calling fopen, when tasks this minute yet glaringly unguarded security wise can be easily be built and vetted by the armed guards supervising the agent about to enter a programming run.

Now there are still obviously holes everywhere remaining in my bot slaves cell that still need to be closed off, like syscalls, inline asm, taking address of, calling anonymous functions all that mess, I mean how can you make c secure against fundamentally insecure input like web server contact forms, or llm outputs?

So sure, c sucks but I'm still into it so why not just give the llm access to parts of c required for what I want done? Why not just write a "pass through" for a small subset of c that looks more like the old timey pascal but with curly brackets instead of begin / ends?

Sort of like what they did with javascript, because fundamentally your web browser javascript engine is tasked with running unsecure input.

ngl thats a nice looking clock!

I love how Anthropic has created Frankensteins monster security wise and then pointing at it and yelling "DANGEROUS" haha

let me get this straight, the complaining user had "--pwned=true"? that option could be better named in my opinion.

agree 100 percent, I write prompts, and at some point I'm going to adjust my style when I see my prompt is ambiguous or something and I bet subconciously I'm going to try to talk like my robot pal when making these adjustments so I could see it happening

I'm not surprised some folks are getting bad results. I was just in /r/openrouter on reddit and even the pro AI folks don't know anything. I also won't deny how messed up some of the external costs are, and the carelessness, nay, complete recklessness of the OpenAI folks and others. Hell there are still folks saying we aren't even paying the actual costs of these things, and certainly we're not adjusting our economic systems in any meaningful way to account for the massive shift in the skills marketplace. And whether it works or not, well it'd be a hell of a hoax if I've spent a dollar and a half and there's some poor thirdworlder somewhere who actually typed code for maybe a quarter hahaha

I can understand it, but it dawned on me that I needed to figure out some cope for AI's presence in the industry, the upside is that AI is the real deal, this stuff really works, the downside of AI are the fucked up ways its being capitalized and its costs externalized, and the crash and inevitable bailouts I see coming, especially for OpenAI, and lets not even mention the morons who can't control their deployed agents, oh yeah security anyone? (crowd yells no thanks)

Being a now hobbyist programmer, AI is just fun for me chatting with it, throwing structs and snippets at each other, but boy am I reading some horror stories about what it does for jobs, working conditions and code quality. The thing is, its just humans making great inventions and then as usual, fucking everything up with them.