[malfist]

Hundreds seems attainable.

Today, for me: * Firefox mobile didn't load the keyboard on a textbox making me kill and restart the app to get it to work. * Firefox mobile pull to refresh triggered while scrolling up * I ask Alexa to turn on some lights and she dinged like she did it but nothing happened. * I turned on my office light that has a routine to turn on a space heater and another light. Only the first light turned on * The Roomba got lost and ignored its keep our zone and ran into the Christmas tree skirt. * When I ran out to get groceries android auto wouldn't connect until I restarted the car. * On another errand, apple car play refused to play music even though it said it was. * A website told me I had unsaved changes and wanted to know if I wanted to navigate away from the page without saving.... While clicking the save button. * I got a letter in the mail from Amex telling me that they couldn't reach me by email and I needed to log into my account and pay a zero dollar balance. This is after I closed all my accounts months ago, I get two letters each month to sign into an account that was deleted to pay a bill that doesn't exist. * Octopi said it's webserver wasn't running, a refresh fixed it. * Build tools at work linked the wrong binary for some tools and I had to manually correct the symlinks. * Insert 10 or more bugs with pipe wire and pulse audio on Ubuntu.

I'm sure there's more, every day is like this. Yesterday I had a plethora of bugs trying to get screenshare and webcam streaming to work for a video conference despite working for a dry run a few minutes prior.

And right now, line breaks aren't working in this reply

[MichaelZuo]

This sounds like a plausible list.

Often times on HN it can be hard to distinguish between scoundrels/trolls/losers/etc… with ulterior motives and genuine people with accurate information, but for this case since Dan Luu has done a lot of credible actions, he should be given the benefit fo the doubt.

[lmm]

Many of those things may not be software bugs as I would normally understand the term, but rather software behaving as specified/intended, where that specification/intention has unexpected and/or undesirable consequences. (The line break thing certainly is, for example). I find it unhelpful to conflate the two.

[eterm]

> software behaving as specified/intended, where that specification/intention has unexpected and/or undesirable consequences

Unexpected behaviour is how I choose to define "bug".

It doesn't matter if the programmer intended it. It's still a bug if it behaves contrary to the user expectation.

It might be that the best resolution is better documentation / training, but it's still worth of a bug being raised to fix.

[homebrewer]

You've never had contradictory user requirements thrown at you, with the expectation that you somehow implement them both? By this definition all software with more than one user is buggy, and it's impossible to do otherwise until we get AGI to do everything.

[c22]

It's a bug if it behaves contrary to the programmer's expectation. Full stop. There is too much diversity in users to go the other way on this.

If a product doesn't meet a user's expectations it may be a poor fit, improper usage, or even a braindead terrible design, but these are not bugs.

[DangitBobby]

I personally don't mind when people lump intentionally bad behavior along with the bugs.

[Dylan16807]

Which ones? I could see the pull to refresh maybe not being a bug, but every single other one sounds like a bug to me.

[lmm]

I mentioned the line breaks are by design. Roomba could be a hardware error or sensor noise. Text box not bringing up the keyboard it's hard to be sure whether that's a bug or intended. The auto thing not connecting could easily be hardware or deliberate. Letters from Amex might well be as specified by their processes. Webserver not running might have been deliberate maintenance.

Many of them could be software bugs, sure, but without actually figuring out what's going on and what the root cause is it's hard to tell.

[Dylan16807]

Oh, I wasn't sure which direction the line break "certainly is" went in. But they have line breaks elsewhere in their post...

I would say failing to deal with hardware error that strongly is a bug. Keyboard I'm pretty sure is a bug, I've had plenty of situations where the keyboard code locks up and needs app restarts. Auto not being auto would be a weird thing to lie about, otherwise it's a bug. "Specified by their processes" a process is an algorithm, sending incorrect messages for $0 could be an algorithm bug or an implementation bug but either way it's a bug in the software, it's not doing that because someone decided it actually should do that. It said the webserver wasn't running but it was, that's a bug if they didn't have a exact unlucky timing.