3 ms·
The optional parenthesis kills it for me. It makes scanning the code impossible: you have to understand each line context.
by BiteCode_dev 4y ago
The optional parenthesis kills it for me. It makes scanning the code impossible: you have to understand each line context.
- endorphine 4y agoHow long do you program in Ruby? I understand this coming from a newcomer but after a while it felt like second-nature to me. I was curious about parent poster, because they said they are using Ruby for years.
- rubyist5eva 4y agoHow? I’ve been writing Ruby and Rails for over a decade and I can’t really say it’s ever been a problem for me.
- batiste 4y agoYeah, the optional parenthesis is one my biggest complaint with the language. It just makes things less readable, with not other benefits than making the code look more clever than it is.
- msbarnett 4y agoHow does this make it confusing? What information do you feel () gives you? You might say: foo().bar().baz() Ah well these are clearly method calls, they have (). But this is Ruby: foo.bar.baz These are clearly method calls too, because in Ruby there’s nothing else they could possibly be. The ()s don’t actually disambiguate anything. Unlike C or Java or some other languages with some notion of bare access to internal fields, there are always and only method calls.