Ruby 3.2.0 is from another dimension

Post by bdcravens » Wed, Jan 04, 2023, 9:59 PM UTC

hk1337 wrote: post #213

michaelteter wrote: post #14

Ruby is my favorite language, and often it is a joy to use because of its combined attributes of brevity, expressive power, and feature consistency. It's disappointing that there are so many more jobs for another popular language - one that lacks the elegance and consistency but which has a larger ecosystem. As far as I know, the only well known reason for a company to choose Ruby is if they want Rails (and obviously…

I love Ruby. Sinatra was actually my entry into using Ruby and recently have been working on a side project with Rails 7. I work with PHP and Laravel too and after working with Rails 7 for a bit Laravel is like a cheap imitation. I also work with python a lot and I wouldn't want to do the web work in python as much as I would ruby but I would rather do the data crunching in python.

Post by claudiug » Wed, Jan 04, 2023, 10:28 PM UTC

tomstuart wrote: post #24

pmontra wrote: post #13

This https://github.com/ruby/ruby/pull/5407 is how to run Ruby with WASI.

While the original Wasm PR description is a useful historical snapshot of the cross-build instructions, the copy in the official documentation is being updated over time: https://github.com/ruby/ruby/blob/master/wasm/README.md

Post by zem » Wed, Jan 04, 2023, 10:30 PM UTC

petre wrote: post #157

robertlagrant wrote: post #115

Earlier quoted context omitted.

The Python one looks fine to me, although I am a Pythonish person. It uses what people already know: the for something in somethings syntax of the for loop, and the if syntax. Also it's nice that this works in dictionaries, generators and lists. It also has the same narrative flow of Haskell's list comprehensions, which I think come from set theory: [x^2 | x As for your Ruby examples: I think you could argue that the…

> As for your Ruby examples: I think you could argue that the filter_map version is very readable, but not necessarily more so, but the select one looks pretty painful. The select does two passes, which makes it quite inefficient. One does not even need filter_map, since the example is essentially a reduce operation. res = (1..10).reduce([]) { |a, x| x != 5 ? a.push(x**2) : a } This works in ruby 2.5.1. Probably work…

Post by bhaak » Wed, Jan 04, 2023, 10:45 PM UTC

mypalmike wrote: post #290

bhaak wrote: post #269

Earlier quoted context omitted.

> To be fair though, my vim-memory of using % to bounce between start/end brackets doesn't work in Ruby because of the begin/end words instead of matched symbols :( Put "runtime macros/matchit.vim" into your .vimrc. Or for even better support add the matchup plugin. https://github.com/andymass/vim-matchup

I'm not a vim user, but I think the problem with Ruby here is that it's not begin/end. It's anything that evaluates to an iterable/end.

Post by lcnPylGDnU4H9OF » Wed, Jan 04, 2023, 11:05 PM UTC

Ancapistani wrote: post #251

xigoi wrote: post #52

Earlier quoted context omitted.

One aspect in which Ruby is much more consistent than Python: sorted(arr) arr.sort() versus arr.sort arr.sort!

I'm definitely a Python person, having used both fairly significantly - Python about ~12y, Ruby ~3y. One thing I think Ruby gets right is the naming convention for methods that modify the object they're called on ( . !) and callables in general that return a boolean ( ?). My biggest gripe with Ruby is the class implementation. I find metaclasses a bit more difficult to understand in Ruby. I hate that I can't easy det…

  def index
    p method(:render).source_location
    render params[:id]
  end

  my_object.method(:my_method).source_location # returns /path/to/file.rb:[line number]