Re Windows 95, thanks for the correction, I'll update the root node. It seems that Windows NT was a rewrite of Windows 3 and that Windows 95 was derived from the Windows 3 code base.

Python 3: I only claimed it was meeting "substantial resistance". Maybe that's unfair, depending on your interpretation of "substantial", but it's certainly meeting some resistance based on random web chatter on the subject. Well, I'm a Python user and I'm resisting it. ;-) My personal opinion is that breaking backward compatibility was unwarranted for a release with relatively modest improvements. Many businesses with large investments in Python 2.x code will resist Python 3 indefinitely because upgrading will prove too risky and/or too expensive.

Update (2017): Even a company as wealthy as Google, according to this Hacker News item, are still heavily using Python 2. This is hardly surprising. Where is the ROI on spending millions of dollars rewriting millions of lines of already working code, without adding any customer value, while being almost guaranteed to suffer numerous breakages to critical business systems? You also pay an Opportunity cost. Curiously, I see some of Google's legacy Python 2 systems are being rewritten in Go perhaps because at least there is some perceived customer value (faster performance) in a Go rewrite. For smaller less wealthy companies, rewriting millions of lines of working Python 2 code in Python 3 could well put them out of business. Of course, if you don't have much Python 2 code, switching to Python 3 is a no brainer.

Update (2020): I see Jython is still Python 2 and IronPython3 unfinished. At least Perl doesn't have to worry about updating Java and CLR versions of the language. :)

Update (2023): Despite (or perhaps because ;-) it abandoned its many Python 2 users, Python won the language adoption war, at least it's now No. 1 in the TIOBE index. This topic is analysed in more detail at Organizational Culture (Part VI): Sociology.

See Also

In reply to Re^2: Nobody Expects the Agile Imposition (Part VI): Architecture (Python 3) by eyepopslikeamosquito
in thread Nobody Expects the Agile Imposition (Part VI): Architecture by eyepopslikeamosquito

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.