3 ms·

Here is a simple example. Ruby's start_with? method which is confusing because its bad grammar. So AS added an alias and called it starts_with? https://github.c

Here is a simple example. Ruby's start_with? method which is confusing because its bad grammar. So AS added an alias and called it starts_with? https://github.com/rails/rails/blob/main/activesupport/lib/active_support/core_ext/string/starts_ends_with.rb https://github.com/rails/rails/blob/main/activesupport/lib/a... Why is this bad? Makes total sense to me. Now both forms work and hopefully it eventually makes it into the language like often happens. But until it does, why not monkey patch obvious mistakes?

Fire-Dragon-DoL 5y ago
Because Ruby has been consistent: there is no method starting with S. Array has `include?`, Regexp has `match?` and String has `match?` and `start_with?`. This is consistent: there is no S. Now when I'm in a codebase, depeneding on ActiveSupport and which parts of it are included, the consistency is now missing. Is it with S or without S? And what methods DO have the S version and which one do not?
- joelbluminator 5y ago
  It's a fair point about consistency but its still bad naming. AS accepts both so I don't see a problem. I do hope Ruby will eventually deprecate and rename it to includes? , starts_with? etc.