in reply to I failed today

> They went with Python2 instead, imagine that

Choosing Python 2 as a sexy new language for a brand new project in 2023 certainly surprised me.

That is just the tip of the iceberg in my experience, with the younger guys eager to use a multitude of Infrastructure as code tools, such as Puppet and Ansible ... and new DevOps tools, often requiring JVM languages, such as Groovy ... and Microservices ... and trendy new statically typed languages, such as Golang and Rust, and ... :)

> my work is pushing most of us Linux deployers to start using Windows now for our client machines

In case it helps, I recently installed Ubuntu on Windows 11 - it's been working well and has made working on Windows much more enjoyable.

Replies are listed 'Best First'.
Re^2: I failed today
by LanX (Saint) on Apr 13, 2023 at 02:47 UTC
    > Choosing Python 2 as a sexy new language for a brand new project in 2023 certainly surprised me.

    Yep!

    > I recently installed Ubuntu on Windows 11

    Well that's Microsoft, if you can't buy them, or ruin them, embrace them...

    Though occasionally they sell too early -> microsoft-once-owned-a-chunk-of-apple xD

    Cheers Rolf
    (addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
    Wikisyntax for the Monastery

      >> Choosing Python 2 as a sexy new language for a brand new project in 2023 certainly surprised me.
      > Yep!

      I admit I checked the date: was it really April 12 ... or April 1? :) ... OTOH, I shouldn't have been surprised, given what I predicted back in 2011 :)

      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.

      ... 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 ...

      See also: Re^6: Improving p5p: Perl is going to stay Perl (Backwards Compatibility)

        Perversely, despite cruelly abandoning its many happy and loyal Python 2 users (by breaking Backward compatibility), Python won the language adoption war! At least, it's been leading the TIOBE index for quite a while now (from Perl holds its own against Python Ruby et al, note that Perl (No. 6) was one ahead of Python (No. 7) in the TIOBE Index back in 2008).

        The Why Perl Didn't Win essay argues that this is because an ecosystem focused on maintaining existing projects, rather than creating new projects, will be less attractive for new projects :) ... and being adopted for new projects is how you win the language war in the long run.

        This topic is analysed in more detail at: Organizational Culture (Part VI): Sociology

        I'm not very proficient with Python, but AFAIR it seems to be quite normal to have multiple Python versions installed.

        Somehow these incompatible modules seem to be able to communicate.

        Update

        In a pythonista way of understanding communicate

        Cheers Rolf
        (addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
        Wikisyntax for the Monastery