2025: The Year in LLMs
11–20 of 643 posts
Re: 2025: The Year in LLMs
#12Re: 2025: The Year in LLMs
#13Re: 2025: The Year in LLMs
#14On this including AI agents deleting home folders, I was able to run agents in Firejail by isolating vscode (Most of my agents are vscode based ones, like Kilo Code).
I wrote a little guide on how I did it https://softwareengineeringstandard.com/2025/12/15/ai-agents...
Took a bit of tweaking, vscode crashing a bunch of times with not being able to read its config files, but I got there in the end. Now it can only write to my projects folder. All of my projects are backed up in git.
Re: 2025: The Year in LLMs
#15Remember, back in the day, when a year of progress was like, oh, they voted to add some syntactic sugar to Java...
> they voted to add some syntactic sugar to Java... I remember when we just wanted to rewrite everything in Rust. Those were the simpler times, when crypto bros seemed like the worst venture capitalism could conjure.
Re: 2025: The Year in LLMs
#16Re: 2025: The Year in LLMs
#17[flagged]
Re: 2025: The Year in LLMs
#18Great summary of the year in LLMs. Is there a predictions (for 2026) blogpost as well?
Re: 2025: The Year in LLMs
#19Re: 2025: The Year in LLMs
#20> Vendor-independent options include GitHub Copilot CLI, Amp, OpenHands CLI, and Pi ...and the best of them all, OpenCode[1] :) [1]: https://opencode.ai