2 ms·
In fairness, I suspect the author would agree that it was a mistake to use Django in the first place. I think that's what he was trying to get at! > Python 3 w
by philwelch 7y ago
In fairness, I suspect the author would agree that it was a mistake to use Django in the first place. I think that's what he was trying to get at!
> Python 3 was first released in 2008. Python 2 EOL is 2020. If I built an app in 2010 using a Python 2 stack you have to know by 2019 you're going to have to rewrite it completely using a new stack or modify it heavily (assuming Django would move to Python 3 and be active 10 years later).
In 2010, the conventional wisdom was still, "nobody uses Python 3, there is no library support for Python 3 so just use Python 2". Django itself didn't support Python 3 until 2013.
- pfranz 7y agoIn hindsight he can say it was a mistake, but it was glaringly obvious back then that Django, Python 2, or Python 3 wouldn't give you a situation where you would have minimal maintenance for the next 10 years because of the volatility already publicly discussed. But maybe you're right that this isn't something people think enough about when choosing technologies and the author is trying to raise awareness.