4 ms·

This argument is a reasonable one and is why we all support IE6 for web dev. However, at a certain point it is worth your time to move forward instead of doing

This argument is a reasonable one and is why we all support IE6 for web dev. However, at a certain point it is worth your time to move forward instead of doing nothing, you gain a little time savings now and you run into few moments of "Oh @#$%^!!" later. Real world example: You don't bother updating ssl to deal with weak DHE and suddenly chrome users can't see your payment site. My approach has always been to try to front load the work instead of doing it in crisis mode later. It sorta sucks but that's just how software is right now.

hartator 10y ago
Except Python 3.x is bringing controversial changes and was slower than Python 2.x for several years. If IE7 was slower than IE6, you can't blame people to not move over.
- Too 10y ago
  There's no controversial changes in python3? Except if you consider print() controversial but that's so silly it's laughable. There are however non backwards compatible changes, like unicode by default, IE7 was also non backwards compatible so the comparision still holds. (with the exception that IE had a compatibility mode if you sent some magic http headers)
  - hartator 10y ago
    It can be silly, but that was one of the reason I picked Ruby over Python 5 years ago for a project. I felt at the time, Python is awesome, however they are taking a weird path.
    - js8 10y ago
      Do you still feel that way or anything changed?
      - jrumbut 10y ago
        As a different person who made the same choice for the same reason at the same time I think I was very right then to avoid the whole mess. It seems fine now, but there is nothing, as far as server side application coding is concerned, that would make me want to switch from Ruby/Rails.
- int_19h 10y ago
  All changes are controversial. In a large enough group, there's no way to make everybody happy. The question is whether the new arrangement makes more people happy long term. Judging by the rate of Python 3 adoption, it took a long time indeed, but it got there. As for Python 2... well, there are still people signing petitions for Microsoft to bring back VB6. Last one was this year, I think.

hartator 10y ago

Except Python 3.x is bringing controversial changes and was slower than Python 2.x for several years. If IE7 was slower than IE6, you can't blame people to not move over.

Too 10y ago
There's no controversial changes in python3? Except if you consider print() controversial but that's so silly it's laughable. There are however non backwards compatible changes, like unicode by default, IE7 was also non backwards compatible so the comparision still holds. (with the exception that IE had a compatibility mode if you sent some magic http headers)
- hartator 10y ago
  It can be silly, but that was one of the reason I picked Ruby over Python 5 years ago for a project. I felt at the time, Python is awesome, however they are taking a weird path.
  - js8 10y ago
    Do you still feel that way or anything changed?
    - jrumbut 10y ago
      As a different person who made the same choice for the same reason at the same time I think I was very right then to avoid the whole mess. It seems fine now, but there is nothing, as far as server side application coding is concerned, that would make me want to switch from Ruby/Rails.
int_19h 10y ago
All changes are controversial. In a large enough group, there's no way to make everybody happy. The question is whether the new arrangement makes more people happy long term. Judging by the rate of Python 3 adoption, it took a long time indeed, but it got there. As for Python 2... well, there are still people signing petitions for Microsoft to bring back VB6. Last one was this year, I think.