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.
Ruby 3.0 Preview 1
41–50 of 207 posts
Re: Ruby 3.0 Preview 1
#42So now there are basically no dynamically typed languages left. There's Scheme, JavaScript, what else? All languages nowadays are converging to TypeScript/Rust. It's kind of sad.
what do you mean? you can certainly use vanilla javascript if you really want, same with ruby. its not like types are forced down your throat
OTOH, by skipping typing you lose a lot of guardrails and won't discover bugs until runtime.
Re: Ruby 3.0 Preview 1
#43If you interested in seeing how the 3x3 initiative* has come along, here are the benchmarks so far: https://github.com/mame/optcarrot#readme Personally, I am very excited for this release. * Matz's goal to get Ruby 3 to be 3x faster than Ruby 2. -- @sosodev Thanks for the updated info!
Note: I have been using Roda with Ruby 2 and it is pretty fast. Can't wait to see what it would be with 3x3.
Re: Ruby 3.0 Preview 1
#44Earlier quoted context omitted.
Metaprogramming is an important part of ruby, so method_missing stays.
No, metaprogramming is a stain on software engineering that all ecosystems are moving away from. Except Ruby.
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.
Re: Ruby 3.0 Preview 1
#45So now there are basically no dynamically typed languages left. There's Scheme, JavaScript, what else? All languages nowadays are converging to TypeScript/Rust. It's kind of sad.
Re: Ruby 3.0 Preview 1
#46You can test your heroku app on the new ruby 3 preview already! ( https://devcenter.heroku.com/changelog-items/1889 )
Re: Ruby 3.0 Preview 1
#47So now there are basically no dynamically typed languages left. There's Scheme, JavaScript, what else? All languages nowadays are converging to TypeScript/Rust. It's kind of sad.
Re: Ruby 3.0 Preview 1
#48My 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…
> - Endless method: this one is cute, I love it! It's a weird name for it. It should probably be called something like 'equational method definitions'
Re: Ruby 3.0 Preview 1
#49Question: 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.
Re: Ruby 3.0 Preview 1
#50My 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…
Recent summary of scheduler, a little bit out of date (changes to interface): https://www.codeotaku.com/journal/2020-04/ruby-concurrency-f...