Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

2025: The Year in LLMs

simonwillison.net

Post reply on HN
Print view View original

71–80 of 643 posts

Re: 2025: The Year in LLMs

#71

Post by SauntSolaire »

OGEnthusiast wrote: post #15
throwup238 wrote: post #4

Earlier quoted context omitted.

> 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.

Crypto bros in hindsight were so much less dangerous than AI bros. At least they weren't trying to construct data centers in rural America or prop up artificial stocks like $NVDA.

Instead they were building crypto mining warehouses in rural America and propping up artificial currencies like BTC.

Re: 2025: The Year in LLMs

#72

Post by noodletheworld »

bandrami wrote: post #58
noodletheworld wrote: post #45

Earlier quoted context omitted.

I know it seems like forever ago, but claude code only came out in 2025. Its very difficult to argue the point that claude code: 1) was a paradigm shift in terms of functionality, despite, to be fair, at best, incremental improvements in the underlying models. 2) The results are an order of magnitude, I estimate, better in terms of output. I think its very fair to distill “AI progress 2025” to: you can get better res…

Did more software ship in 2025 than in 2024? I'm still looking for some actual indication of output here. I get that people feel more productive but the actual metrics don't seem to agree.

I am not making any argument about productivity about using AI vs. not using AI.

My point is purely that, compared to 2024, the quality of the code produced by LLM inference agent systems is better.

To say that 2025 was a nothing burger is objectively incorrect.

Will it scale? Is it good enough to use professionally? Is this like self driving cars where the best they ever get is stuck with an odd shaped traffic cone? Is it actually more productive?

Who knows?

Im just saying… LLM coding in 2024 sucked. 2025 was a big year.

Re: 2025: The Year in LLMs

#75

Post by DANmode »

bandrami wrote: post #55
n2d4 wrote: post #50

Earlier quoted context omitted.

This is extremely dismissive. Claude Code helps me make a majority of changes to our codebase now, particularly small ones, and is an insane efficiency boost. You may not have the same experience for one reason or another, but plenty of devs do, so "nothing happened" is absolutely wrong. 2024 was a lot of talk, a lot of "AI could hypothetically do this and that". 2025 was the year where it genuinely started to enter…

Did you ship more in 2025 than in 2024?

I definitely did.

Objectively 0->1 lots of backlog.

Re: 2025: The Year in LLMs

#76

Post by zahlman »

DrewADesign wrote: post #40

You’re absolutely right! You astutely observed that 2025 was a year with many LLMs and this was a selection of waypoints, summarized in a helpful timeline. That’s what most non-tech-person’s year in LLMs looked like. Hopefully 2026 will be the year where companies realize that implementing intrusive chatbots can’t make better ::waving hands:: ya know… UX or whatever. For some reason, they think its helpful to distrac…

As much as I side with you on this one, I really don't think this submission is the right place to rant about it.

Re: 2025: The Year in LLMs

#77

Post by sothatsit »

blibble wrote: post #65
dmd wrote: post #23

Earlier quoted context omitted.

People denied that bicycles could possibly balance even as others happily pedaled by. This is the same thing.

people also said that selling jpegs of monkeys for millions of dollars was a pump and dump scam, and would collapse they were right

JPEGs with no value other than fake scarcity is very different to coding agents that people actively use to ship real code.

Re: 2025: The Year in LLMs

#78

Post by zahlman »

OGEnthusiast wrote: post #15
throwup238 wrote: post #4

Earlier quoted context omitted.

> 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.

Crypto bros in hindsight were so much less dangerous than AI bros. At least they weren't trying to construct data centers in rural America or prop up artificial stocks like $NVDA.

Speaking of which, we never found out the details (strike price/expiration) of Michael Burry's puts, did we? It seems he could have made bank if he'd waited one more month...
Post reply on HN