>>2 I really don't get this one, branch is beautiful.
Name:
Anonymous2016-01-10 21:04
>>4 Dijkstra once said 'GOTO Considered Harmful' and people who don't think for themselves started this cult where anyone using goto for any purpose is wrong.
In modern terms, it's a 'meme'.
Name:
Anonymous2016-01-10 21:46
MiB instead of MB. GiB instead of GB. TiB instead of TB.
Name:
Anonymous2016-01-11 1:07
>>6 that there are two different versions requires two different names.. but it's so fucking stupid that there are two :|
>>21 Beautiful. I think it's a form of art: purposefully break parts of your bbcode so that true connoisseurs could enjoy compiling it in their heads. Also, look at my twin diggits.
Name:
Anonymous2016-02-15 0:36
>>7 Idiots say "megabyte" and mean 103. Good programmers will instead mean 210 octets. And real men will have spotted the error in this post.
>>24 I get it too, but fail to see any "lol" in it.
Name:
Anonymous2016-02-15 4:14
/* comments */ instead of // comments in new code. Because K&R is sacred, let's all stick with K&R!
Name:
Anonymous2016-02-15 6:19
Kike and Richy!
Name:
Anonymous2016-02-15 18:53
>>23 They didn't invent Kibibytes and Mebibytes for nothing.
Name:
Anonymous2016-02-16 1:19
// instead of #. So annoying.
Name:
Anonymous2016-02-16 2:14
>>26 Satire is the lowest form of comedy and the lowest form of wit.
Name:
Anonymous2016-02-16 6:49
>>26 The most annoying thing is that when you want to comment a part of code that already has /* ... */ block in, you may fail because the end of outer comment would be at the end of inner comment block.
Name:
Anonymous2016-02-16 10:25
// instead of ;. So annoying.
Name:
Anonymous2016-02-16 14:26
/* コメント */ instead of 「コメント」. なんてうるさい.
Name:
Anonymous2016-02-17 2:49
>>31 (* OCaml to the rescue! (* I wish this shit wasn't such a bitch to type though *) *)
>>46-48 It's doubly annoying for vim since it has had per-directory .exrc / .vimrc support for forever. Emacs doesn't have an equivalent feature that's as widely used. Thus if you see a vim user with mode lines it means they are clueless, or an Emacs refugee.
Name:
Anonymous2016-02-24 14:56
>>26 They do it because they're writing C89 and // comments aren't C89
Name:
Anonymous2016-02-24 15:04
>>26,50 I came for the C89 but stayed because I decided // comments looked ugly (at least for big blocks).
Also, there's no shortage of little languages (mostly inputs for old Unix tools, like ld and variants) that only recognize /* */ comments.
Name:
Anonymous2016-02-26 11:23
People confusing Java with JavaScript. In 2016. Its like their only expirience with Java was some applet.
But Titor-san, it's no longer year 90. Thats what "new code" means, when you're using something better than Turbo C 2.0/VC6.
Some statists are also shocked and offended by free declarations, you know, those vile things not right after opening brace. Those dirty statements introducing variable scope anywhere surely can trigger the OCD-C habits formed in teens. Such anarchy! How can they allow this?!
Name:
Anonymous2016-03-10 14:46
>>55 If you're using a crap compiler (or a good one, with most optimizations disabled), non-free declarations are useful as they allow the function's stack usage to be appraised at a glance. Granted most compilers will try to keep only live variables around and in registers wherever possible, but a big pile of declarations up top is still a good sign that a function is doing too much.