Where does Ruby go from here? • Hacker News Board

Re: Where does Ruby go from here?

#91

Post by MrBra » Sat, Sep 06, 2014, 4:24 AM UTC

AlexeyBrin wrote: post #78

JonnieCache wrote: post #11

I don't want to leave ruby, but at the end of the day, it's slow. Jruby is pretty decent, but the clunkiness of the JVM takes the fun out of it. Maybe it's just the lack of a corporation pouring billions into it like google did with V8, but I suspect that ruby can never be fast, due to ObjectSpace and the like. That awesome/insane object model we all like so much is just impossible to optimise. All the other weird sh…

Ruby is not inherently a slow language. An ideal setting, will be a Ruby open source compiler (similar with what RubyMotion does) that could be used to package your code. I would use the the interpreter to test/develop the code and the compiler to actually package it.

Exactly. People is on Ruby because of its semplicity to test ideas and craft things. That's the same reason so many devs started using Rails.

So, one immediate solution that would drive again Ruby to a stellar embracement and adoption could be preserving, in development, this immensely useful hyper-reflective environment which gives us hyper productivity and then have a parallel production environment where all of this is stripped down and code compiled without it.

In the wait for better solutions this could be a possible path, and I am sure a lot of people and software in the Ruby ecosystem would still prefer to adapt to this, rather than having to code in a more performant but ugly language.

Re: Where does Ruby go from here?

#92

Post by MrBra » Sat, Sep 06, 2014, 5:30 AM UTC

jshen wrote: post #60

programminggeek wrote: post #44

Earlier quoted context omitted.

You can get close if you don't use Rails. Seriously, Cuba + JRuby + Torquebox 4 is fast, nearly as fast as Go. http://madebymarket.com/blog/dev/ruby-web-benchmark-report.h...

I'm sorry, a hello world benchmark is meaningless.

For concurrency-testing-alone it might be not. If it works good at it, then it's a good indication that the concurrency model implemented in the language is not flawed and if there is a problem, then it might be somewhere else in the language.

So that benchmark it's still valuable information in the sense that tells you that that particular language running on that particular runtime its not intrinsically bad at concurrency.

In this particular case (JRuby) moreover, the language gets its concurrency layer thanks to Java, so I'd go really easy with that, unless you really want to say that Java is bad at concurrency or that this is not known and thus a "Hello World" example would not show it.

Which are both wrongly proven statements.

Nonetheless I must admit though that some of those combinations of runtime/server/frameworks are admittedly unstable to replicate or to work with in a real scenario.

Re: Where does Ruby go from here?

#93

Post by MrBra » Sat, Sep 06, 2014, 5:42 AM UTC

toupeira wrote: post #85

bam365 wrote: post #68

Earlier quoted context omitted.

No, there really hasn't. And it's a little embarrassing. Lawyers, doctors, carpenters, electricians, engineers, etc. don't feel the need to produce countless rhetorical manifestos. I'm not sure why our profession (or craft, or whatever you want to call it) has to come with so much cultural baggage, especially when there are so many real problems left to be solved.

I think it's only natural because software development is an intrinsically creative endeavour.

Unless he had to solve boring problems.