Ruby 3.0 Preview 1 • Hacker News Board

_odey wrote: post #21

My thoughts: - RBS: meh... might get more useful in the future (in 2-5 years maybe). - Ractor: Wohooo! I'm writing a DAG library where I was thinking of implementing something like this, good to know I can use it and get real parallelism on top. - Scheduler: :shrug: don't know about this one, might be relevant with future concurrent ruby code, any ideas? - Rightward assignment: it's a bit awkward but I see the use ca…

You may be interested in precompiled native Nokogiri: https://github.com/sparklemotion/nokogiri/issues/2075

Re: Ruby 3.0 Preview 1

#54

Post by sigzero » Fri, Sep 25, 2020, 10:54 PM UTC

whitepoplar wrote: post #10

stevebmark wrote: post #9

I really wish Ruby would grow up and deprecate method_missing

What's wrong with it?

Nothing. There is nothing wrong with it at all except he "doesn't like" it.

Re: Ruby 3.0 Preview 1

#55

Post by sickcodebruh » Fri, Sep 25, 2020, 10:55 PM UTC

Didn’t see it linked in the preview announcement, here’s the RBS syntax guide: https://github.com/ruby/rbs/blob/master/docs/syntax.md

Glanced at it from my phone but it looks good! I’m looking forward to seeing it in RubyMine. Still sad that we can’t write these in .rb files but I wonder if the plan is to go the other way, eventually permit typed code in .rbs?

Does anyone know what the story will be with third-party definitions? Are we headed towards a DefinitelyTyped style repository for Ruby?

Re: Ruby 3.0 Preview 1

#56

Post by onekorg » Fri, Sep 25, 2020, 11:11 PM UTC

JohnBooty wrote: post #37

_odey wrote: post #21

My thoughts: - RBS: meh... might get more useful in the future (in 2-5 years maybe). - Ractor: Wohooo! I'm writing a DAG library where I was thinking of implementing something like this, good to know I can use it and get real parallelism on top. - Scheduler: :shrug: don't know about this one, might be relevant with future concurrent ruby code, any ideas? - Rightward assignment: it's a bit awkward but I see the use ca…

My thoughts: - A Ruby "Preview 1" release? Oh crap, I have to start Christmas shopping soon.

I just realized why I have a lot of christmas memories of me sitting around with family while reading hacker news comments in a thread about a ruby release.

Never noticed it's always released on December 25th.

Re: Ruby 3.0 Preview 1

#57

Post by stevebmark » Fri, Sep 25, 2020, 11:20 PM UTC

cknoxrun wrote: post #44

stevebmark wrote: post #40

Earlier quoted context omitted.

No, metaprogramming is a stain on software engineering that all ecosystems are moving away from. Except Ruby.

This comment sounds so joyless. The programming language ecosystem allows for all sorts of approaches, some many folks love passionately, and some you may not like. However, your comment seems to suggest a whole swatch of software engineers are simply wrong/ignorant because they enjoy one of these paradigms that you don't. Burned or not in the past, I can't help seeing your comment as a form of anti-intellectualism.

Plenty of people also probably loved GOTO

Re: Ruby 3.0 Preview 1

#58

Post by maxpert » Fri, Sep 25, 2020, 11:21 PM UTC

jasonhansel wrote: post #29

Question: will the nonblocking scheduler start to make Ruby concurrency competitive with e.g. Node.js and Go? Currently Ruby mostly uses heavyweight threading mechanisms that cause trouble for I/O-bound microservices.

In theory yes; but if there is something native that uses blocking API then your thread will be still blocked.

Re: Ruby 3.0 Preview 1

#59

Post by wrp » Fri, Sep 25, 2020, 11:30 PM UTC

reader_mode wrote: post #17

>Rightward assignment statement is added. >fib(10) => x This is exactly the kind of stuff I hated when I had to work with ruby in my last gig and why I will never accept a job using it again - soo many pointless and inconsistent ways to do the same thing ... they have method aliases for collection operations like map/filter in standard library ! .NET went with non-standard SQL-like names (select/where) and I'm not a…

Ruby has been referred to as Smalltalk meets Perl, and the problem of dealing with other people's code is one of the main things that kept me in the past from using Perl on text processing projects. The problem of collaborating in Perl was lessened a lot by adhering to Damian Conway's Perl Best Practices. Is there anything similar for Ruby?

Re: Ruby 3.0 Preview 1

#60

Post by burlesona » Fri, Sep 25, 2020, 11:31 PM UTC

JohnBooty wrote: post #37

_odey wrote: post #21

My thoughts: - RBS: meh... might get more useful in the future (in 2-5 years maybe). - Ractor: Wohooo! I'm writing a DAG library where I was thinking of implementing something like this, good to know I can use it and get real parallelism on top. - Scheduler: :shrug: don't know about this one, might be relevant with future concurrent ruby code, any ideas? - Rightward assignment: it's a bit awkward but I see the use ca…

My thoughts: - A Ruby "Preview 1" release? Oh crap, I have to start Christmas shopping soon.

Yeah playing with new Ruby is one of my favorite parts of Christmas :)