the state of the art

C sucks. how about a stdlib that doesn't encourage buffer overflows

c++ sucks. operator overloading?? templates??? what were you smoking bjarne!

c# sucks. it was made by microsoft. nuff said.

perl sucks. having your two year old kid design the syntax just isn't a good idea

phyton sucks. self.this self.that and a retarded community

ruby sucks. "it's OOP so it must be good!" suck my cock

lisp sucks. the syntax is so retarded nobody uses it despite it having some good ideas

ml sucks. does anyone even know what ml is?

haskell sucks. once in a while i'd like to have a mutable variable that doesn't require a phd in cs to use!

java just plain sucks.

...

the programming INDUSTRY sucks because you're all a bunch of cocks that were too stupid or narrowminded to study some worthwile natural science

>>28
Modern compilers tend to try and optimize code for speed and/or size (sometimes on and off etc. option). So although you told the compiler to use an int if it realized that only a byte is required it will change it assuming it can do it safely without damaging your program logic.

A starker example of the kind of optimization changes they can do is rolling out a loop, so for example code:

for (i=1;i<100;i++)
{print(i);}

The compiler may choose to sacrifice size for increased speed by removing the need to increment i. Changing the code too:

print(1);
print(2);
…
print(98);
print(99);

This is one of the many weird things compilers can do to try and speed up your code. Generally you would set your compiler not to optimize while still debugging the code otherwise you may get a nasty surprise when you cant find your loop counter =P