this post was submitted on 13 Nov 2023
96 points (92.1% liked)
Programming
17492 readers
36 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
What do you mean regarding weird typing?