Live data from Hacker News

Ruby 2.0.0 Released

ruby-lang.org

211–220 of 303 posts

Re: Ruby 2.0.0 Released

#211

There are some nice features here: Keyword arguments, which give flexibility to API design This looks good to replace all those options hashes in rails for example, though I wish they'd made it an all or nothing thing, apparently you can still do this: def foo(x, str: "foo", num: 424242) i.e. use some named and some unnamed in the same method which looks ugly. Module#prepend, which is a new way to extend a class Comp…

Speaking of the video you posted, go to 8:43.

"I know someone who is working on a Ruby implementation and making very good strides and is not talking about it publicly at all--and I think you'll be surprised when you find out about it."

Is Brian Ford talking about Topaz [1]?

[1] http://docs.topazruby.com/en/latest/blog/announcing-topaz/

Re: Ruby 2.0.0 Released

#214
post #13

Earlier quoted context omitted.

I'm a huge Python fan and there is nothing in the world that would force me to switch to Ruby =P

That's exactly what I mean. People feel very strongly for one or the other. Yet, even you, can't deny that they are very similar! Compare them to Java, Lisp, C, Go, Haskell, Perl,...

This thread is full of people saying "I use (python|ruby) and (ruby|python) seems fine. There's just no reason to learn it" and you respond excitedly to this comment as if it's representative.

http://en.wikipedia.org/wiki/Confirmation_bias

Re: Ruby 2.0.0 Released

#215

Earlier quoted context omitted.

I maintain rails-api, and both Yehuda and I have commit to Rails. I just want to mention that while Ember + Rails will be a potent combo, Ember will work great with non-Rails backends as well, and rails-api will work great with other frameworks too. That said, we're working really hard to make sure that Rails 4 + rails-api + Ember 1.0 is a fantastic experience, so watch that space for sure.

Thanks for all the hard work Steve. I have been waiting for ember 1.0 to really give it a proper go but I'm looking forward to it. It seems like a slightly steeper learning curve than something like backbone but I'm sure it will do more for you once you get to grips with it.

"All his hard work" ?? Blah, more B.S from steveK, the guy is a total fraud who has barely done anything on value on ANY project. Look at all his contributions there's barely anything more than a docfix or merging someone ELSE's pull request: https://github.com/rails-api/rails-api/commits?author=stevek...

Hell, even "shoes" and "hackety hack" the two projects that made him famous he's barely done any work on, and the work he has done is just (you guessed it) merging other people's pull requests. The guy is a fraud.

Far as i can tell, all he actually does is crying about gender equality and babbling on twitter. He's not a real programmer. He's a full-time "celebrity", a fraud.

Re: Ruby 2.0.0 Released

#216

Earlier quoted context omitted.

Thanks for all the hard work Steve. I have been waiting for ember 1.0 to really give it a proper go but I'm looking forward to it. It seems like a slightly steeper learning curve than something like backbone but I'm sure it will do more for you once you get to grips with it.

"All his hard work" ?? Blah, more B.S from steveK, the guy is a total fraud who has barely done anything on value on ANY project. Look at all his contributions there's barely anything more than a docfix or merging someone ELSE's pull request: https://github.com/rails-api/rails-api/commits?author=stevek... Hell, even "shoes" and "hackety hack" the two projects that made him famous he's barely done any work on, and the…

[deleted]

Re: Ruby 2.0.0 Released

#217
post #81
post #10

Today, I'll lose at least 50 karma points, but it's worth: Why people still use Ruby? 1. Because they get dream day rates for maintaining rusty slow legacy systems 2. Because they do not want to learn new languages and can stay in their comfort zone 3. Because they think it's still 2005 and nobody cares about slow server response times And now Ruby lovers, click on downvote or give your reasons why you still use Ruby…

Ruby lovers are all about "feelings" and "style", they don't care if their language of choice is objectively worse than, say, Python or Lua. Ruby truly is the Apple of the programming world.

I fought with Python for weeks before I picked up Ruby. It clicked perfectly and I've never had to fight with it.

I don't see how Python can be objectively better than Ruby.

I don't know enough about Lua to comment.

Re: Ruby 2.0.0 Released

#218

Earlier quoted context omitted.

That's exactly what I mean. People feel very strongly for one or the other. Yet, even you, can't deny that they are very similar! Compare them to Java, Lisp, C, Go, Haskell, Perl,...

This thread is full of people saying "I use (python|ruby) and (ruby|python) seems fine. There's just no reason to learn it" and you respond excitedly to this comment as if it's representative. http://en.wikipedia.org/wiki/Confirmation_bias

[deleted]

Re: Ruby 2.0.0 Released

#219

Earlier quoted context omitted.

That's exactly what I mean. People feel very strongly for one or the other. Yet, even you, can't deny that they are very similar! Compare them to Java, Lisp, C, Go, Haskell, Perl,...

This thread is full of people saying "I use (python|ruby) and (ruby|python) seems fine. There's just no reason to learn it" and you respond excitedly to this comment as if it's representative. http://en.wikipedia.org/wiki/Confirmation_bias

The above comment happened to be one of the first responses. The others came later. That's why.

Re: Ruby 2.0.0 Released

#220
post #153
post #111

Earlier quoted context omitted.

As a Ruby user that finds Rails annoying and not something I like working with, I don't think that's all that relevant. A lot of people have come to Ruby because of Rails, but a lot of Ruby people dislike Rails too. There's a plethora of web frameworks for Ruby that have sprung up exactly because of people who want to use Ruby but don't like Rails. In terms for barrier to entry with Python, the issue is that a lot of…

You seriously would turn down a good job or other opportunity if the only downside was having to write in a whitespace-sensitive language? Most of the good developers I know have their preferences for sure, but can be productive in all sorts of languages.

Python has enough other design mistakes (statements vs expressions, destructive sort by default, and crippled lambdas to name a few) to keep away anyone with exposure to a more functional style even without whitespace issues.
Post reply on HN