#rubyists — Public Fediverse posts

## Please Don't Nerf RubyLang Because #StyleGuides

Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

## Please Don't Nerf RubyLang Because #StyleGuides

Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

## Please Don't Nerf RubyLang Because #StyleGuides

Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

## Please Don't Nerf RubyLang Because #StyleGuides

Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

Hey #rubyists and #ruby people! At $DAYJOB, I've been using the #racc and #rexical gems to create a grammar and parser for an internal sql-like query language. I was initially nervous because I didn't have much experience at this type of thing, but it's ended up being a very fun thing to work on. When finished, it will eliminate some years-old code written by some blithering idiot that's been source of odd bugs for a long time, and improve the user experience considerably. #programming

@cedx I think it's a great option for #Rubyists that need some #JS without having to master the whole JS language or one of its many frameworks first. However, transpilers are abstractions, and all abstractions are leaky. Native idioms can sometimes be more optimal, and it can be hard to debug transpiled code if you haven't mastered the target language too.

Choosing #CoffeeScript as a transpiler over native #ECMAscript is therefore a trade-off. There's no canonical right answer.

#ProTip Never waste an opportunity to rant against language/ecosystem misfeatures! I never tire of complaining about the overuse of #FrozenStringLiterals in #RubyLang, or the over-reliance on community style guides as a stand-in for #codequality instead of using #TDD, intentional semantics, or good variables/comments.

If you don't trust other #Rubyists to understand `[].any? ? complain : shut_up` without an extra 4 lines of if/else bloat in your method, the real problem isn't the ternary!