Very true. The thing is you don’t fix it. You say “the implementation of that sucks, but bear with it.” Or you deprecate the behaviour, print boring warnings for at least one major version further and only then you change it.
Yeah, true that, they should have put warning signs everywhere for 2.6 and maybe fixed it in 2.7 (or Ruby 3?).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, true that, they should have put warning signs everywhere for 2.6 and maybe fixed it in 2.7 (or Ruby 3?).