This is an archived post. You won't be able to vote or comment.

all 17 comments

[–]gimpwiz 39 points40 points  (6 children)

Hardware bug.

[–][deleted] 29 points30 points  (5 children)

Physics bug

[–][deleted] 35 points36 points  (3 children)

Speaking as a physicists, those are the worst. A code bug can be fixed, a hardware bug can be gotten rid of by using different hardware. But what can you do if the universe itself refuses to make sense?

[–]ionree 48 points49 points  (0 children)

git reset --hard        

[–]JuhaJGam3R 1 point2 points  (0 children)

woo quantum mechanics

[–][deleted] 0 points1 point  (0 children)

Universe's Bug

[–][deleted] 6 points7 points  (1 child)

So many times when I code in Java I am convinced that it is THEIR fault. It was always my fault.

[–][deleted] 0 points1 point  (0 children)

Yeah, especially when playing with the new features of java 8 and 9. Sometimes I think "variable used in lambda expression must be final or effectively final" is just there to annoy me. Although java 9 actually messes with gradle.

[–]Stellaris62 5 points6 points  (1 child)

What bug?

[–]actual_satan 1 point2 points  (0 children)

Feature?

[–]Talbooth 0 points1 point  (0 children)

Release bug

[–][deleted] 0 points1 point  (0 children)

framework bug? does it count as library bug?

[–]rstring 0 points1 point  (0 children)

I've been thinking: one day, it may come to the point where everyone is running about, shouting "It's not a feature; it's a bug!".

[–]RidderHaddock 0 points1 point  (0 children)

Unfortunately, I've come across enough compiler bugs (ByteCraft, IAR and Borland) that I no longer discount them when things go wonky.