3 ms·

Knowing how so many devs are hungry to move to the new shiny thing, the question is often more like "why hasn't this been rewritten in Python3 already?". Possi

by joshwa 7y ago

Knowing how so many devs are hungry to move to the new shiny thing, the question is often more like "why hasn't this been rewritten in Python3 already?". Possible answers: • Legit technical or cost/benefit reasons • Probably a good idea but no budget/time for the effort • Somebody already tried and it was a disaster • No manager has been stupid enough to humor the devs

nine_k 7y ago
Most reasonable devs are not jackdaws and do not want a "new and shiny" thing for its shine. Mostly devs want to go away from the old and increasingly creaky thing. And when the cost / benefit ration is finally right (that is, it's creaking loud enough and slows things down much enough), the move hopefully happens.
- Aeolun 7y ago
  > Most reasonable devs are not jackdaws Most devs are not reasonable.