Recent submissions

Comment · 1 day ago
Good like trying to explain to your customers that their data is no more accessible because some api key ended up in a public git repo or since you admin panel is exposed to whole internet someone was able to log in.
Comment · 1 day ago
And so? This is true for any kind of infra!

You can't defend yourself from everything, but you can try to make you life easier by reducing the attack surface and make side movements more difficult.

Comment · 1 day ago
Yep, but the attack surface is much smaller!
Comment · 1 day ago
It's much easier to protect yourself if you have your infra behind a perimeter firewall you control.
Comment · 4 days ago
You don't say!
Comment · 9 days ago
> 29 of 35 answers were the same one.

Did they distillate from each other? :D

Comment · 14 days ago
You’re right, mine are assumptions are just as much assumptions as yours.

However, if you’ve worked with coding agents and seen repositories that were mostly vibecoded, you’ve probably also seen how complex they became in a very short time. Even the estimate of 200 LOC per PR was conservative, actual number is very likely much higher.

In any case, even if a large portion of those lines were documentation, tests, or comments, those count as LOC too, and it’s simply not humanly possible to keep up.

PS: They could simply release more data and stop the debate, but for some reason, they don’t.

Comment · 14 days ago
Actually LOC is a decent measurement, it becomes a bad measurement when you use it in the wrong way, like any other measurement.

Agree that 30k PR alone doesn't mean much, but there aren't other details on what's inside. Based on I saw on how LLM programming works, it's hard to believe that there are single-line fixes. If I have to bet I'd bet on 200 LOC on average, that is 6M/day. Even if only a small portion reach production, it's still insane.

Comment · 15 days ago
No human can stay on par with 30k pull requests per day ... they simply don't have control on what's going on and rely on AI itself to do the job.

PS: I really want to know what is the churn rate (and the cost per LOC) here. My gut is saying the cost per LOC is insane, and they are basically rewriting over and over the same code.

Comment · 17 days ago
If there are going to be multiple browsers with different implementation of the same standard frameworks will still matter.

If there are going to be no standard for basic things like a combo box frameworks will still matter.

Comment · 18 days ago
> as of September, we merged over 30,000 per day.

I just wonder what is the churn rate (and the cost per LOC) here.

Comment · 23 days ago
This is latests refactor, in older videos he stated more than once that llms are basically crap (and at the time he said that he was probably right, but it was very short sight)
Comment · 23 days ago
Zitron complained about a lot of things, one some he was wrong (eg. llm are not useful), on others(eg. "magic accounting" or datacenters ) he has very good points ... but we will see.
Comment · 23 days ago
You don’t say…

Anyway, if I had a hundred bucks to burn, I’d bet this is a move to undermine Anthropic’s IPO.

Comment · 24 days ago
It's much simpler: they want others to experiment (and pay them) and see what works, once they know what works they will drive out of market other players.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton