>> I agree the compatibility problem.
>> I hope the migration path, the magic comment and command line option,
>> mitigate the problem enough.
>> Current code can work for Ruby 3.0 with trivial one line addition:
>> "# frozen-string-literal: false".
>> If the performance improvement can be discarded, even the addition is unnecessary.
>> The only necessity is the command line option, --disable-frozen-string-literal.
>
> I worry those options will be disappeared in future versions. I need to make sure that the option will be guaranteed to remain exist in future versions.

Ruby is a open source project. You can contribute for a compatibility.


> As a person who is responsible managing for many Ruby-based enterprise products, I really care about the compatibility. It was a nightmare to migrate our 1.8.7 codes to 1.9, because of many small incompatiblity in the release. Even small incompatibilities, it's a real burden for users if there aremany...

I really don't understand why you can think other rubyist think a
compatibility isn't important.