Why doesn't /prog/ love ruby?

I mean hey, fix the slowness (it's already as fast as python), and it's a perfect language. The whole "everything as an object" concept and easy to understand syntax makes it both flexible and simple.

And having everything as an object makes even lambdas able to be passed as single variables, so you can pass an entire function as an argument to another function, without having to have that function evaluated till later.

WHY AREN'T YOU USING RUBY, /prog/?

Reasons why ruby sucks?
Blocks are not lambdas are not procs are not methods are not blocks are not procs are not lambdas are not blocks are not methods. In a decent language they're all the same. (a decent language has a multiple dispatch object system with generic functions if any)

Other reasons?
      end
    end
  end
end

Variables are not declared (or declaration looks the same as assignment) variable = 1; variabIe = 2; if variable == 2 then puts "foo" end

Not to mention it's slow as fuck.

>>41
It's only as slow as Python. RoR is Ruby as fuck, thanks to all the damn monkey patching. Moot point I guess, Ruby wouldn't be cool without its coke habit.

I prefer end to } 9 days out of ten.

I prefer end to } 9 days out of ten.
Why? It's arbitrary.

x = do this
       that
       somethingelse $ do
         more stuff
         more
         andThen $ do
           morestuff

No need for ends.

>>40
And thank fuck you can't write 5.times in Perl. Or 5->times for that matter.
They changed -> to . in Perl 6.

>>44
Glad you mentioned it. Now I get to point out that .times isn't Cool. You'd have to go full retard and monkey patch it.

>>40
My pleasure:
perl6 -e 'use MONKEY_TYPING; augment class Int { method times($c) { $c.() for (1..self) } }; 5.times: { say "fuck off" }'       
fuck off
fuck off
fuck off
fuck off
fuck off

>>39

Ruby is very well capable of not looking like crap, but there is absolutely no problem with letting the programmer go nuts if he so pleases. Adding restrictions only makes a language worse.

>>41

For any do end block you can use { and } instead... everything else I can't help you with, but luckily vim uses different syntax coloring for an end to an if/else/case statement than it does for a class/module/method/block definition.

>>43

Indentation without something to close it looks like crap.

JAVA

>>1
Because all Ruby programmers are pretentious gen-Y faggots with no background past Java or PHP who think first-class functions are a subset of OOP.