Re:Mercurial’s journey to and reflections on Python 3
by raymondh on Monday January 13, 2020 @03:42PM
(#22038347)
This criticism of the dev team seems naïve, "It should not have taken 11 years to get to where we are today." Core developers can make tooling available, but they can't control adoption. That is a user decision. Users switch-over on a timetable governed by their own individual cost-benefit analysis.
[ Parent
| on HN ]
Re:Mercurial’s journey to and reflections on Python 3
by yjftsjthsd-h on Monday January 13, 2020 @03:53PM
(#22038443)
> Core developers can make tooling available, but they can't control adoption
Core developers made the design decisions that made nobody want to adopt it.
> the ecosystem of users and projects are collectively much better-off than if the transition had not occurred at all.
The question seems more like, "could the same benefits have been had with less pain", and a reasonable reading is that the answer is yes. (ex. 4 years of not being able to work with bytes reasonably even if you did need them)