Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

If an unsafe wrapper can be mis-used, it's not actually safe, and so the bug still lies inside the wrapper.


sort by: page size:

Nonsense. You can twist any bug into "irresponsible behavior".

This is one of those misleading headlines. A bug is a bug.

To be fair, usually bugs don't expose people to criminal liability.

That isn't a bug, it's a felony.

Bugs are inevitable. No matter how much you think about the problem, there will always be things that slip between the cracks.

Bugs are not the same as intentions.

Designed bugs are still bugs.

How long ago was this? I wonder what the bug was. I want to try this, but don't want to go through a painful uninsall experience

There is also a possibility to stumble upon a bug accidently.

Is that really a bug?

A bug is a bug regardless of what the original specification mentioned.

Wait, so his bug has a bug in it and if tested would bug-out by working properly?

When do legit bugs turn into active negligence?

Shoot, apologies for that, this was a silly reading error on my part... I quickly read that comment while outside and didn't realize 'redcalx' was referring to the user above, and instead somehow my brain just glossed over that part as a typo.

Disregard that part of my comment and look at all the rest of what I've actually been saying. The problem I have been trying to point out with the definition (as in the last comment, but I'll repeat here) is that the definition of a "bug" might be "just semantics" to you, but that doesn't make it irrelevant; those semantics make all the practical differences here. If you consider any undesirable behavior in unintended situations to be a "bug", then it sure sounds good, but won't get you anywhere, given that practically anything you buy can be used in weird ways with unforeseen (and hence unintended) consequences. If you consider a "bug" to be a deviation from the manufacturer's specified behavior, then it's obviously more limiting, but I would expect it's closer to the semantics a court would use to decide whether to hold the manufacturer responsible.


That's what was thought to us years back in CS grad school... A paper tape sucked in a bug and the issue was circled in pen on the tape with someone writing "bug" on it.

“Bug” is an unverified assumption. For all we know this could be a designed outcome.

Bugs are possible and even common.

If every PR you put up is "likely" to contain a bug, you're doing it wrong.

What if it's, you know, a bug
next

Legal | privacy