5 ms·

Let me quote myself from 7 years ago. “ It's kind of disappointing that developers aren't self-aware enough to understand that they are essentially screwing th

Let me quote myself from 7 years ago. “ It's kind of disappointing that developers aren't self-aware enough to understand that they are essentially screwing themselves by not moving quickly in dropping "legacy" support. "Python 3 will be available in 2008 but we understand that you won't use it for at least 5 years." There's an entire class of developers who won't upgrade until they absolutely have to. There's also a class of administrator that won't upgrade their current PC browser from IE6-IE8 until they absolutely have to. Developers are basically screwing themselves by not drawing a firm line.” https://news.ycombinator.com/item?id=7372913 https://news.ycombinator.com/item?id=7372913

Wowfunhappy 6y ago
Or, everyone leaves your platform because they can't keep up with the breaking changes.
- adamc 6y ago
  Less a problem with languages, in my experience, than libraries. Django updates are a pain in the rear.
  - deleted 6y ago
    [deleted]
  - Wowfunhappy 6y ago
    idk. I think there's an alternate universe somewhere in which Python just got hard forked by the community, and the python foundation lost its influence over the direction of the language. The split today would be even larger, or Python 3 would have become an intellectual curiosity rarely used in the real world.
adamc 6y ago
There isn't really a good solution. Forced migrations always create a decision point, at which point people may gather their resentments and move to something else. But if you don't eventually force a change, you have to live with all of the language's historical mistakes. My shop was interested in migrating long ago, but we had to wait until languages and frameworks (such as Django) supported 3. On projects where that wasn't a risk, we moved to Python around 2014 or so. But: I totally get that for some shops, the feasibility of migrating was low.
jacquesm 6y ago
Developers of tools that ignore their users are doing so at their own peril.

Wowfunhappy 6y ago

Or, everyone leaves your platform because they can't keep up with the breaking changes.

adamc 6y ago
Less a problem with languages, in my experience, than libraries. Django updates are a pain in the rear.
- deleted 6y ago
  [deleted]
- Wowfunhappy 6y ago
  idk. I think there's an alternate universe somewhere in which Python just got hard forked by the community, and the python foundation lost its influence over the direction of the language. The split today would be even larger, or Python 3 would have become an intellectual curiosity rarely used in the real world.

adamc 6y ago

There isn't really a good solution. Forced migrations always create a decision point, at which point people may gather their resentments and move to something else. But if you don't eventually force a change, you have to live with all of the language's historical mistakes. My shop was interested in migrating long ago, but we had to wait until languages and frameworks (such as Django) supported 3. On projects where that wasn't a risk, we moved to Python around 2014 or so. But: I totally get that for some shops, the feasibility of migrating was low.

jacquesm 6y ago

Developers of tools that ignore their users are doing so at their own peril.