Ruby 2.0.0 Released

Post by Mon_Ouie » Mon, Feb 25, 2013, 10:51 AM UTC

grey-area wrote: post #116

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…

     class Processor
       def process
         puts "Very important stuff here"
       end
     end

     module Logger
       def process
         puts "Entering process."
         super
         puts "Leaving process."
       end
     end

Post by damncabbage » Mon, Feb 25, 2013, 11:34 AM UTC

ubernostrum wrote: post #280

michaelwww wrote: post #246

Earlier quoted context omitted.

I prefer my white space to not mean anything because I normally can't see it. If I show white space then I see meaningful and non-meaningful white space. I find this aggravating and figure the designer of such a language is a control freak who will likely continue to aggravate me in other stupid ways. I don't need this in my life. I don't know how this disagreement between myself and the language designer seems 'supe…

ialsoagreewiththisandfindthatshowingwhitespaceisacompletelyunnecessarythingandonlygetsinthewayofhowawesomelysmartiamtobeabletoreadallthecodeiwrotewithoutanywhitespaceinit

Post by BITCOINATOR » Mon, Feb 25, 2013, 1:24 PM UTC

kawsper wrote: post #279

marvwhere wrote: post #99

my personal best new feature is: "The UTF-8 default encoding, which make many magic comments omissible" because i'm from Germany and we had to add: # coding: utf-8 in every freaking controller to get our german stupid letters (öäüß) to run without problems. so i'm looking forward to my next project where i can use 2.0 from the scratch. thank u!

Why are you writing special characters in your controllers? We are Danish, and are writing comments in English, and all locale strings is placed in i18n-files.

Post by pifflesnort » Mon, Feb 25, 2013, 1:37 PM UTC

Tomte wrote: post #268

pifflesnort wrote: post #226

Earlier quoted context omitted.

You don't implement HTTP caching, except in very specific cases. You cache generated data where you need it. This is 1) Easy to add later, 2) Doesn't sacrifice the flexibility of being able to recompose that data on-demand, and 3) Doesn't require a bunch of complex front-end infrastructure to support.

Of course "you don't implement caching". I think it was clear that I was talking about designing a cache-aware application. Cf. http://www.mnot.net/cache_docs/ .

Post by wyuenho » Mon, Feb 25, 2013, 3:41 PM UTC

kamaal wrote: post #271

wyuenho wrote: post #269

Earlier quoted context omitted.

You should note that there's a huge gap in the definition in the English language between "trolling" and "defending". Also, stop putting your words into other people's mouth. Who here is advocating Python indentation as a cure-all? Point is, you can talk about Ruby all you want, but when you diss on Python indentation, you'd better back up your opinions with facts instead of substituting your opinion as facts. The on…

What exactly are Python defending in a "Ruby 2.0.0 Released" thread? What is the there to defend here? The title is "Ruby 2.0.0 Released" not "Ruby 2.0.0 Released against Python". Why did the OP of this thread even question the relevance of Ruby as compared to "Python". And why is it that only Python people feel a need to do that in every thread on other languages? Its always the Python guys who do this, I never see…