2 ms·
This is because often the "cause" is actually jut time ticking : - What was fun 3 years ago isn't anymore - That feature that was useful to your customers is
by IMTDb 8y ago
This is because often the "cause" is actually jut time ticking :
- What was fun 3 years ago isn't anymore
- That feature that was useful to your customers is no longer serving purposes
- It was about new feature, and now it's about maintaining compatibility
- ...
There is no real cause to "treat", you just need to adapt to the new environment you are facing.
- xg15 8y agoThat seems too easy. That guy was the core of the Python community for over 20 years. Supposedly he has seen a lot of ups, downs and drama and experienced the downward slope of the motivation curve often enough and still held on - until now. So what was different this time? > There is no real cause to "treat", you just need to adapt to the new environment you are facing. Maybe, maybe not. The purpose of a deeper analysis should be to find out whether or not it might be like this - but you can't just assume it's like this from the start.
- IMTDb 8y ago> That guy was the core of the Python community for over 20 years Exactly. I can't imagine keeping the same job/role for 20 years. Guido even says it : he is tired. He has had the energy, drive and will to steer the python ship for 20 years. He now feels that it is time for him to take a well deserved holiday/vactaion/time off. As other have said, this has probably already been discussed within the core devs already. But people need to find a "reason" to explain what is just a very natural process. And will spend countless hours looking for it instead for just moving to the next adventure.