The Floor Is Java

Content C, do you ever get sad about not. having boolean variables? Python, that's just silly. Who needs booleans, when integers are so much better! Huh! How would you know, anyway? Fine. Let's ask Java. Java. wnica co vourink are better, bools or ints? Geez, that's a hard one. Come on Java, you must know! You have both types! Well. Sorry, guys... just can't compare them.

Content 13k I like VIM. Favorite editor: VIM javascript Tike working with haskell vim reactis node.js prefer not to work with mouse

Content Java Programming Who is the father of Java? O Dennis Ritchie O James Cameron Guido Van Rossum James Gosling Submit answer 70f15 15m 22s remaining ProdrammerHumor.io

Content br br Greg Kill fuck marry: java, c, python Kill c, fuck python, marry java That was an easy one I'm in love All I want is for you to blame my death on c I think it's assumed C - artificial intelligence - artificial alcohol - not artificial death Liked by Greg string quote gravestone; Liked by Greg You should let me buy you a drink or six sometime I'll take six please then the "" will bitwise swap into an "e"

Content Ash system.out memeln( ) guys literally only want one thing and it's fucking disgusting 2017-10-22, 1:56 AM All 22307 tests passed - 681 ms optjavajdk1.8.0121binjava Compiled with 0 errors and 0 warnings Process finished with exit code 0

When you're dealing with a critical security vulnerability and someone suggests using pre-decrement (--i) instead of post-decrement (i--) as the "fix," you're basically asking a genie to reduce your problem count to zero... and getting exactly what you asked for. The joke here is that the programmer wants to make their problem count "0" (meaning no problems), but the genie interprets this literally and just sets their wish count to 0 instead. It's like changing i-- to --i in your code and calling it a security patch when you've fundamentally changed nothing about the actual vulnerability. You've just shifted when the decrement happens—before or after the expression evaluation—but the exploit is still there, laughing at your PR. Classic "technically correct but completely useless" energy that every code reviewer has seen at 3 AM.