Live data from Hacker News

There's no reason for software to be slow anymore

danluu.com

481–490 of 532 posts

Re: There's no reason for software to be slow anymore

#481

If there's no reason for software to be slow anymore, then why, when I click on any item in my Windows 11 computer, does it take 30 secords for something to acknowledge I clicked? With a Ryzen 5 CPU boasting quite a few cores, an Nvidia gpu board, and 64GB of DRAM, why does it take so long?

I suspect MS Defender and other libraries loading, such as .NET.

Re: There's no reason for software to be slow anymore

#482

Earlier quoted context omitted.

But it will definitely improve, either speed or volume.

I'm really bothered by the mindset of the people against this. People act like induced demand is evil. In reality, if more people were able to go wherever they wanted to go, that's actually a good thing regardless of if the existing people didn't get to go somewhere faster.

It’s NIMBY in another form

Re: There's no reason for software to be slow anymore

#483
post #450

Earlier quoted context omitted.

This is an incomplete and quite superficial view of what is going on out there, in my opinion. I've worked on plenty of projects where the assumption was that since the round-trip to the server is going to take almost 100ms that'll dwarf anything that's going to happen on the server itself, justifying poor choices that lead to potentially adding a whopping 100ms onto that number. These numbers only get larger with a…

> These numbers only get larger with a larger perceived "Nothing we can do about it" God forbid you say anything about it in a code review lest you get shouted down about premature optimization.

"There're no metrics showing this is a problem (because it's not live yet), so I will not write it correctly!"

"This other unrelated thing in the code is slower, so writing this correctly is a poor use of time!"

Re: There's no reason for software to be slow anymore

#485
post #217

Earlier quoted context omitted.

1-5ms response time is clearly hard for most real world endpoints.

I don't know how hard it is. But I can certainly say there is no business inscentive for it. When it comes to improving performance by a few ms, or implementing a new feature, business people will always choose a new feature, unless the current performance is unbearably slow (we're talking regular 1.5s+ wait times for BE response). And it's not even a modern problem, legacy software written 20 years ago has the same…

When I worked at Cisco we had regular 10 second responses on our main flows (bad data model) and still couldn't get buy-in to fix it.

Re: There's no reason for software to be slow anymore

#486
post #414

Earlier quoted context omitted.

They literally unlicense the product out from under you as part of windows update. You’re the one having to sue, unless you never connect your machine to the internet anyway.

Okay then pirate the software while the lawsuit carries out. Or just pirate the software and let them sue you for pirating, which you will win since you have a license, even though the computer thinks you don't.

uh huh

Re: There's no reason for software to be slow anymore

#487

Earlier quoted context omitted.

So many developers do this, and it's infuriating. I have a device sitting there on my perfectly good LAN, yet if I want to remote control it, the brilliant software decides to send the commands to the Internet, then back to my device, then the response gets routed to the Internet, and back to my phone. Device developers, stop doing this! You people realize that LANs exist, don't you?

I was doing firmware + mobile a at large-ish startup a decade ago. Same story as Sonos; there was a push to go all cloud instead of our local network implementation that worked great. I argued breathlessly against it for days. I’ll never forget the sales chad raising his voice to shut me down with a cop-out:“This is the way the industry is going!”. It’s not the developers making these changes.

And look what happened to Sonos soon after that! I’m sorry, but I’ve gotten to the point where I would’ve just yelled back at the guy “Prove it, chudmuffin! You’re advocating for something you know nothing about and sending the company in a disastrous direction which will lead to its demise. If your idea is so great, then you prove it’s better than decades of established precedent at the largest companies in the world.” Then watch their head asplode and challenge me to a fistfight in the parking lot. Yes, I’ve had that happen with a sales “guy.”

Not saying that’s what you could or would have done, I’ve just gotten to the point in life where I’m alreaover it, ready to throw it back at them. Maybe it’s from living in this part of the world, but our plumber said “always be ready for people to be mean to you“ and while it doesn’t make for a very peaceful life, it certainly makes for fun ripping heads off.

Re: There's no reason for software to be slow anymore

#488

There's no reason for sites to look super ugly, full width and unreadable anymore.

His site didn't always look like that, for some reason he changed it a while ago and now I have to use a custom stylesheet so I can read his articles. It used to be more readable.

Re: There's no reason for software to be slow anymore

#489
post #45

Earlier quoted context omitted.

Nah, he's just trying to be different. It's vanity. He's had a usable website in the past. This one is explicitly made to be shitty. "Look at me, I'm such a geek" energy.

His site has always looked like this, i'm sure of it. This is what sites look like if you just write them as text. Not everybody knows how to use sql or css or java or whatever thing it is that lets you pick the font.

No it didn't. It used to be more readable and he changed it to look like this.

Re: There's no reason for software to be slow anymore

#490
post #475

Earlier quoted context omitted.

> Bro, what the fuck do you think I’m doing? Do you think I don’t know about spec driven development? Bro, I don't know you, and have no idea what you do, except for the parts you share in your comment, like talking to a LLM :) If you say "if you ask an agent to write a compiler" and don't expand on that, I'll take your word for it. I'm glad you got a laugh, and didn't take it so serious :) Not entirely sure why you…

I'm still interested in your claim: > If you instead spend a day writing a proper specification, then ask the agent to spend a week implementing that, you'll need zero tools and skills afterwards to clean it up, because there won't be any misunderstandings, assumptions or other things, just code fulfilling what the specification says. Are you claiming that you reliably get good software out of agents using this proce…

> Are you claiming that you reliably get good software out of agents using this process?

Yeah, for sure, I tend to be really strict about the overall design, keeping things minimal and only the abstractions needed, nothing more/less.

I don't know what "most complicated software" even is, I've only been writing software for 20 years or so, but mostly around startups, smaller companies and as a consultant/freelancer for companies of all sizes, so I won't even claim to know what "really complicated software" is. What I've done so far ranges from implementations of various ML models, native cross-platform applications, various types of games, simulation software and a bunch of tooling to help me with music production and VFX/animation/3D work.

Some of those I guess I wouldn't even have approached without LLMs, and probably would have taken me years if I did attempt, but following that process I basically end up with one spec, maybe 2K-3K lines in total, including step-by-step how things have to be implemented, then fire off Codex + GPT-5.3-Sol max with "/goal" saying exactly how things should be implemented, verified and so on, and update the specification file as it goes along, and not stop until everything from the specification been confirmed to be implemented correctly. Longest been 4-5 days until the goal is completed.

Always a lot of iterations afterwards of course, as I realize some things I put in the specification ultimately didn't made sense once it's implemented, so revise specification, figure out how to change, fire off "/goal", and repeat this until I have code that is better or at least equal to how I'd write it myself. It was a long time ago this process lead to something completely different being implemented, I usually get exactly what the specification says.

Post reply on HN