Ruby 3.3

#1

Post by dduugg » Mon, Dec 25, 2023, 7:01 AM UTC

Ruby 3.3
ruby-lang.org

Re: Ruby 3.3

#2

Post by ksec » Mon, Dec 25, 2023, 7:34 AM UTC

I think Ruby 3.3 is perhaps one of the most important and feature rich Ruby release in the past 10 years. I never thought Ruby would have a shipping and production ready JIT before Python. And Prism, Lrama, IRB. A lot of these were discussed in previous HN submissions.

But one thing that is not mentioned or discussed enough, is Ractor, M:N thread scheduler, Fibre and Async. Especially in the context of Rails. I am wondering if any one are using these features in productions and if you could share any thoughts on the subject.

Re: Ruby 3.3

#3

Post by phaedryx » Mon, Dec 25, 2023, 7:37 AM UTC

Prism is interesting. Any Ruby code analysis tools that use it? I've been looking for ways to analyze my code at work.

Re: Ruby 3.3

#4

Post by alberth » Mon, Dec 25, 2023, 7:39 AM UTC

Every Christmas, like clockwork, Ruby Lang drops a new release.

Re: Ruby 3.3

#5

Post by revskill » Mon, Dec 25, 2023, 7:43 AM UTC

I hope Ruby 4.0 could allow explicit import and avoid implicit, global namespace gem import mechanism like nowsdays.

Re: Ruby 3.3

#6

Post by pgib » Mon, Dec 25, 2023, 7:45 AM UTC

Very much looking forward to upgrading our application to ensure 3.3 compatibility.

Re: Ruby 3.3

#7

Post by t-writescode » Mon, Dec 25, 2023, 7:45 AM UTC

revskill wrote: post #5

I hope Ruby 4.0 could allow explicit import and avoid implicit, global namespace gem import mechanism like nowsdays.

I'm feeling a bit ignorant, but isn't this a Rails thing and not a Ruby thing? I know that for most projects that's a distinction without a difference; but, that may be a decision from the Rails devs and unrelated to what Ruby's devs do?

Or I'm speaking out of my ear and completely wrong (and I don't know which :D)

Re: Ruby 3.3

#8

Post by nirvdrum » Mon, Dec 25, 2023, 7:47 AM UTC

phaedryx wrote: post #3

Prism is interesting. Any Ruby code analysis tools that use it? I've been looking for ways to analyze my code at work.

The Ruby LSP uses Prism. Kevin Newton has implemented a Prism-based backed for the white quark/parser gem [1] that can be used with Rubocop.

[1] https://github.com/kddnewton/parser-prism

Re: Ruby 3.3

#9

Post by quickthrower2 » Mon, Dec 25, 2023, 7:59 AM UTC

alberth wrote: post #4

Every Christmas, like clockwork, Ruby Lang drops a new release.

It is a cute thing about Ruby

Re: Ruby 3.3

#10

Post by byroot » Mon, Dec 25, 2023, 8:01 AM UTC

t-writescode wrote: post #7

revskill wrote: post #5

I hope Ruby 4.0 could allow explicit import and avoid implicit, global namespace gem import mechanism like nowsdays.

I'm feeling a bit ignorant, but isn't this a Rails thing and not a Ruby thing? I know that for most projects that's a distinction without a difference; but, that may be a decision from the Rails devs and unrelated to what Ruby's devs do? Or I'm speaking out of my ear and completely wrong (and I don't know which :D)

It's a Ruby thing. Ruby only has a single global namespace, no imports.

If anything Rails autoloading (Zeitwerk really) make it much easier to find where constants come from as it enforce a constant name -> file name convention, so all you need is fuzzy file search.