Comment on If you had to choose one programming language that you had to use for the rest of your life, what would it be?

iceywhatyoumean@lemmynsfw.com ⁨1⁩ ⁨year⁩ ago

• Fal@yiffit.net ⁨1⁩ ⁨year⁩ ago

  I just can’t comprehend how anyone can think ruby is enjoyable to work in or beautiful. To me it’s a dumpster fire. I would almost rather write php.

  source

  • iceywhatyoumean@lemmynsfw.com ⁨1⁩ ⁨year⁩ ago

    I can’t imagine thinking the opposite either. People are different. Matz’s attempts at backwards compatibility in Ruby 3, particularly wrt typing haven’t been kind to its more elegant origins, but ‘dumpster fire’ is baffling to me. Some people do like php , though, so 🤷🏻‍♂️

    source
  • zagaberoo@beehaw.org ⁨1⁩ ⁨year⁩ ago

    Ruby’s === operator actually serves a useful purpose at least.

    source
• Pyroglyph@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Crystal is very similar to Ruby, but is compiled to native code instead. Would you consider that? Why or why not?

  source

  • iceywhatyoumean@lemmynsfw.com ⁨1⁩ ⁨year⁩ ago

    Yeah, I’ve tried out Crystal. I like it, I think it’s got a lot of potential. I like the improved performance, and the concurrency model. The community and ecosystem isn’t as strong, though. If I had to pick one right more, it would still be Ruby! I love Elixir too, for different reasons. It’s a completely different language, but with a similar style.
    I had a look at Mirah back in the day. It’s like Ruby, with stronger, more static typing, that is designed-in better than Ruby’s bolted on typing additions.

    source
• amju_wolf@pawb.social ⁨1⁩ ⁨year⁩ ago

  Ruby seems like a clusterfuck for anyone who doesn’t work on a project alone, change my mind.

  source

  • zagaberoo@beehaw.org ⁨1⁩ ⁨year⁩ ago

    Ruby gives you all kinds of tools to make clusterfucks, but it’s not hard to keep your hands out of the metaprogramming cookie jar.

    But with careful application even fucky features can be put to good use. Like monkey-patching a problematic method to only throw an exception rather than allow accidental misuse. With a nice verbose error message and good testing practices there’s almost no risk.

    source

    • amju_wolf@pawb.social ⁨11⁩ ⁨months⁩ ago

      Oh I didn’t even mean that; just the (possible, shorthand/unreadable) syntax alone, weird typing, etc. seem like it’d be hard to work with.

      It’s also funny because “allowing clusterfucks” is a huge reason why PHP was so hated; when you took care to write it properly it wasn’t bad even in the early days.

      source

      • zagaberoo@beehaw.org ⁨11⁩ ⁨months⁩ ago

        The thing with Ruby clusterfucks is you have to go looking for them. Languages with implicit type coercion and loose comparison like PHP and JS have clusterfucks lying in wait for you and it takes concerted effort to avoid them.

        source