[squeak-dev] Poll | 60Deprecated in Squeak 6.0 ... opt-in or opt-out?
marcel.taeumel at hpi.de
Wed Jun 8 09:30:18 UTC 2022
Well, what's definitely going to happen is that the next Trunk (6.1alpha) will not have 60Deprecated loaded. Your version-number-based argumentation is void in Squeak as our version numbering does not follow a bigger agenda. :-)
I don't see any issues in having 60Deprecated loaded by default in the final 6.0 release.
Am 08.06.2022 10:35:21 schrieb Tobias Pape <das.linux at gmx.de>:
> On 8. Jun 2022, at 10:32, Marcel Taeumel wrote:
> Hi Tobias --
> > Deprecation is not the same as removal.
> For Squeak, there is no real difference between disabling deprecation warnings and loading that 60Deprecated package. Same kind of effort.
The difference is knowing whats happening before stuff is gone.
That cognitive effect cannot be circumvented by just going fast and burning bridges.
Don't tackle a social issue with a technical solution.
>> Am 08.06.2022 10:23:04 schrieb Tobias Pape :
>> > On 8. Jun 2022, at 09:00, Marcel Taeumel wrote:
>> > Hi all --
>> > I explained my plans on this weeks or even months ago. Yet, only now, people are beginning to understand what this means and are complaining that the package 60Deprecated should be loaded by default in the 6.0 release image.
>> > "opt-in" would mean that users have to make an extra tick in the preference wizard.
>> > "opt-out" would mean that users can unload that package manually as they see fit.
>> > What are your thoughts on this?
>> Here's My view:
>> People learn about deprecations in the release they are announced.
>> This should not be the release these deprecations are removed, the earliest it should be removed in the next major release, better in the one after.
>> People learned about the deprecation of CrLfFilestream in 5.1.
>> CrLfFilestream hence can be removed the earliest in 6.0.
>> Deprecation is not the same as removal.
>> Deprecation is:
>> "hear me out, we promise not to use this from this release on,
>> please also stop soon"
>> Please do not forget that not everyone is (and I'd suggest the majority of user are) following trunk; for them, deprecation and removal would happen at the same time, which is too surprising.
>> I vote for 60Deprecated to be removed in 7.0 the earliest.
>> A thing that would work for me:
>> 60Deprecated is opt-out in 6.0
>> 60Deprecated is opt-in in 7.0
>> 60Deprecated is not expected to load in 8.0
>> Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev