Well, I've always thought we are stuck in a local minimum when it comes to programming languages. Like, programming shouldn't be this hard and shouldn't require so much boilerplate after almost a century. If the actual important logic can be inferred pretty well from markdown specs, that means most of what we write in JavaScript, Go, Java is redundant.
Hopefully someone smarter than me is working with trying to develop a new programming language given what we know to be possible with LLMs
Well it "works" only because LLMs have the context baked in. The problem is, that this context is something like world-knowledge. Defining the context you need for your exact problem, e.g. your company, will add so much more information that programming is probably the better way.
Honestly every developer needs to increase those default limits, they are too low for modern development... So you are just crippling them and a proof of that is they keep getting this error while in their regular workflow
I don't even hit 256 on my desktop with a shitton of things open and 75 firefox sandbox processes, much less on a remote server. What in heaven's name are you doing to cross 256?
Honestly I think this thread has just devolved to HPC admins vs people who don't understand how shared multiuser sytems work cause they've been stuck on a laptop for too long to remember.
> Honestly every developer needs to increase those default limits, they are too low for modern development...
The users can develop on >100 compute nodes, but choose not to bother doing any kind of forwarding/proxying/jumping to them and just do stuff on the login nodes.
If they can't be bothered to do a "ssh -J …" then it's on them. The resources are there.
Using AI is a pretty good indicator that the reader will need to exert more effort than the writer did. Unless the reader also decides to use AI to summarize it, but then what's the point?
