Stubsack: weekly thread for sneers not worth an entire post, week ending Sunday 1 September 2024 - eviltoast
  • blakestacey@awful.systems
    link
    fedilink
    English
    arrow-up
    9
    ·
    4 months ago

    Dang it, am I going to have to learn a new programming language after 24 years of getting things done in Python because the edgelords are indulging in a fit of pique?

    • self@awful.systems
      link
      fedilink
      English
      arrow-up
      13
      ·
      4 months ago

      god I hope Python of all things has enough eyes on it that this throw yourself on the ground in agonizing pain and flood the community with a bunch of fash assholes because you got a 3-month suspension shit won’t work, but I’m still astonished it works at all given how obvious it is when it happens

      • froztbyte@awful.systems
        link
        fedilink
        English
        arrow-up
        8
        ·
        4 months ago

        what’s really lol is how this whole arc is developing

        at the start, the announcement about peters being canned for 3 months was really rather obtuse, not even naming the person or pointing at specific threads (just enumerating repeat problems). why, i have no idea

        so now mcdipshit et co are doing their utter best to publicise themselves as crybabies who just got told “no, bad, don’t do that” and did not like it one bit. but the friends they’re choosing… oi.

    • corbin@awful.systems
      link
      fedilink
      English
      arrow-up
      9
      ·
      4 months ago

      I mean, this is why I left during the Python 3 arguments. It was obvious that the core development team only functions to the extent that it can improve the (economic) exploitability of CPython by the consortium which has captured it, and that we’d become so technically dysfunctional that we were no longer able to implement forward-compatible syntax, something we’d had as recently as Python 2.5 but had lost by Python 2.7. The inability of the various “authority” groups like PyCA or PyPA to get things done once-and-for-all is another symptom; there is still no single holistic solution for cryptography or packaging in Python 3.

      Like, I recall having dinner with Guido and Barry (and others; like ten of us at a Chinese restaurant) in Montreal. It was very obvious that Guido not only didn’t grok concepts like pure functions or capabilities or asynchrony, but fundamentally not interested in how they could improve the state of software engineering; he is forever in the mindset of making a teaching language, not a professional language. I also recall discussing with him years earlier (Portland?) about how libraries like Twisted or Django fundamentally only justify their existence by pointing to deficiencies in the standard library, and he didn’t understand that a bad standard-library package can be worse than not having one at all. At least he’s a nice person; at no point was there any yelling or tenseness, and I appreciate that.

      That said, I use Python 3 all the time. I just keep in mind that I shouldn’t prefer it, and I only choose it when there’s a clear developer-time tradeoff, because I know that its maintainers are contemptuous of me merely for using Python 2.7 and PyPy.

      • froztbyte@awful.systems
        link
        fedilink
        English
        arrow-up
        7
        ·
        4 months ago

        and he didn’t understand that a bad standard-library package can be worse than not having one at all

        screams in mime, datetime, yaml, The Long Road To Py3.7+, and more

        That said, I use Python 3 all the time. I just keep in mind that I shouldn’t prefer it, and I only choose it when there’s a clear developer-time tradeoff

        not a week goes by that I am not still awestruck by still how many places there are to stub one’s toe with py3-cluster things

        samesies on still using python in some places. god I wish I could find something else that filled the same first-reach gaps as nicely.