Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby 2.6

anamaria.martinezgomez.name

Post reply on HN
Print view View original

61–70 of 164 posts

Re: Ruby 2.6

#61

Post by Rafert »

maxfurman wrote: post #29

I am always happy to unwrap my Christmas present from the Ruby team! Some questions about this release: - Are there any benchmarks for the new JIT? - Why was `(Date.today..(Date.today + 1)) === DateTime.now #=> true` false in Ruby 2.5? It seems correct that right now is between today and tomorrow. Is it because one is a Date and the other a DateTime?

Benchmarks here: https://medium.com/@k0kubun/ruby-2-6-jit-progress-and-future...

tl;dr: your Rails app is not faster with this feature in this version, but might be in the future.

Re: Ruby 2.6

#62

Post by hamandcheese »

igouy wrote: post #48
jb3689 wrote: post #7

Earlier quoted context omitted.

Ruby isn't perfect but it's a great utility language and can do a lot of powerful things with very little effort. Read through Eloquent Ruby The only problems I wouldn't go to Ruby for are CPU intensive ones or ones where I need parallel threads (which you already have Java for)

> CPU intensive ones Truffle Ruby ? https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

From the Truffle readme:

> TruffleRuby is progressing fast but is currently probably not ready for you to try running your full Ruby application on. However it is ready for experimentation and curious end-users to try on their gems and smaller applications.

> TruffleRuby runs Rails, and passes the majority of the Rails test suite. But it is missing support for Nokogiri and ActiveRecord database drivers which makes it not practical to run real Rails applications at the moment.

Emphasis mine, but that puts it firmly in the "fun toy" category rather than a viable technology for anything mission critical.

Re: Ruby 2.6

#63

Post by briandear »

yxhuvud wrote: post #38
ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

Try Crystal and you get the joy of Ruby enumerables together with a static type system.

Crystal is nice, but my love affair with Swift is going strong. Not exactly Ruby syntax but pretty similar in terms of simplicity. I am a Rubyist who feels right at home with Swift. But for the new year, I definitely want to give Crystal a fair shot!

Re: Ruby 2.6

#64

Post by mmahemoff »

pulisse wrote: post #33
augustl wrote: post #26

Really like the idea of using lazy ranges instead of magic negative indices! I.e `xs[6..]` instead of `xs[6..-1]`.

Negative indices aren't magic. They follow the obvious wraparound (modular) pattern: Negative `i` indexes the element in array `a` located at `i % len(a)`. If they worked any other way it'd be madness.

True, they're not magic, it just looks ugly for the most common case of fetching to the end of the array. The new syntax is much nicer than -1.

Re: Ruby 2.6

#65

Post by ekvintroj »

ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

You should try smalltalk :)

Re: Ruby 2.6

#66

Post by DevKoala »

ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

My thoughts exactly. I feel it isn’t the library, but the grammar, which is why the same feel cannot be replicated by other languages. Ruby is just easy on collections.

Re: Ruby 2.6

#67

Post by tanin »

astazangasta wrote: post #51
ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

Can you comment on why a good type system became so important to you? I can understand the value in interfaces but not really in any other context.

For a non-strong-typed language, it's difficult to dive into the code after you haven't work on that codebase for a while.

We were on a really old Mongoid (or carrierwave, or some other gem, can't remember), It was difficult to find the right methods to use and etc.

I understand it was our own fault not to write comprehensive tests or keep all gems up-to-date.

But a dynamic typing language is a lot more "punitive" when we aren't writing perfect code, using perfect design, and/or exercising perfect engineering practices.

Re: Ruby 2.6

#68

Post by Koshkin »

maxfurman wrote: post #29

I am always happy to unwrap my Christmas present from the Ruby team! Some questions about this release: - Are there any benchmarks for the new JIT? - Why was `(Date.today..(Date.today + 1)) === DateTime.now #=> true` false in Ruby 2.5? It seems correct that right now is between today and tomorrow. Is it because one is a Date and the other a DateTime?

> (Date.today..(Date.today + 1)) === DateTime.now #=> true

It took me a minute to parse this. (I have never had this problem with Python or JS.)

Re: Ruby 2.6

#69

Post by anothergoogler »

ilrwbwrkhv wrote: post #58
ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

what bout clojure?

Clojure's stdlib is unintuitive, and `into` is the poster child.

It's easy to find what's available in Ruby: https://ruby-doc.org/core-2.5.3/Enumerable.html

Good luck with Clojure: https://clojure.github.io/clojure/clojure.core-api.html

Re: Ruby 2.6

#70

Post by abecedarius »

ajmurmann wrote: post #37

Ruby used to be my most beloved language. I've since developed a strong appreciation for good type system. However, working with collections of any kind in Ruby is just such a joy. The methods around it are so well thought throug and make writing code a joy that in most other languages just would be tedious. On top of that the Ruby team is constantly working on making that aspect even better. I truly don't understand…

Can you recommend a post/article explaining some of what makes Ruby's collections especially pleasant? Studying Ruby's stdlib design has been on my 'someday' list, but there's so much else there...
Post reply on HN