[ruby-core:90813] Re: [Ruby trunk Bug#15478][Assigned] [RFC] erb: remove deprecation warnings from ERB.new

[e-mail] wrote:
> Status changed from Third Party's Issue to Assigned

Thanks for fixing.

> > Why change existing behavior at all? 

> That's because leaving a legacy code might confuse those who
> read the code and decreases the maintainability. I like to
> keep implementation simple so that we don't lose the speed of
> implementing new features. Otherwise Ruby implementation will
> stop evolving in the future for maintaining unnecessary legacy
> stuffs. That's why I'm pushing unnecessary things towards
> removal.

I don't believe forcing users to change their code and usages
is worth the trouble.  As far as maintaintability goes, we have
tests to enforce this behavior.

The burden should be on the few of us, the developers.
Not thousands of users.

These warnings and annoyances gives users an excuse to abandon
Ruby for something new (I saw this often where I used to work).

Fwiw, I have many sh/perl5/awk scripts from decades ago which
still work today without modification.  I believe Ruby is a
better language, but I also long for the UI/API stability of
older languages.

> I don't know how to send a patch to your git repository, so I attached it in this ticket.

Thanks.  I'm not sure if my version check or Method#parameters check
is better than my version or if it's even worth the trouble to push
out either patch+release for a limited-scope project olddoc.

Improving email/public-inbox integration with cgit and other
repository viewers is my goal for 2019.  So hopefully I can make
things easier for you and others to figure out in the future
(without relying on centralized or proprietary services)

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>