• PieMePlenty@lemmy.world
    6·
    60 minutes ago

    When I was a wee high school kid, asp.net was windows only back then and getting cheap windows hosting was harder than it was getting cheap linux hosting, so I focused on PHP more.
    I haven’t touched it in forever, but its probably still good, right?

  • cub Gucci@lemmy.today
    1·
    12 minutes ago

    Everyone has forgotten java applets+ java servlets combo. I have no idea why it didn’t survive, but if it would have, it’d defeated PHP (in amount of vulnerabilities ofc)

    • Err(()).unwrap()@lemmy.world
      111·
      1 hour ago

      Or, if you spin it another way: you could’ve picked up the skills to develop for and support various frameworks, or get stuck in a rut for 30 years with just a single antiquated server-side language.

    • MangoCats@feddit.it
      13·
      4 hours ago

      Python was an even bigger mess in 2022 than it was in 2010. The version control hellscape intensifies with the more things there are to have version incompatibilities with.

      • im_fine_sandy@nord.pubEnglish
        62·
        3 hours ago

        I have lots of experience with node and a little with python.

        Python seems great for working with large data sets and I really like jupyter notebooks. The available libraries are really great.

        However, the thought of installing a Python CLI app makes me twitchy.

        I suspect that node has all the same problems and that I’m used to working around them, but all the Python environment stuff is a nightmare.

        • Joe@discuss.tchncs.de
          1·
          1 hour ago

          Python is great for standalone scripts/CLIs with standard system dependencies. For actual apps you want venvs, probably managed by uv these days.

          I’ve written 1000s of python CLIs/scripts over the years, typically wrapping APIs for otherwise shitty enterprise and SaaS software (also many one-off scripts for ETL).

          Nowadays, AI writes these scripts in a fraction of the time (and reads the shitty API docs / otherwise figures it out) and my CLI toolkit is better than ever (with $0 ongoing cost). Calling MCPs from CLIs is also interesting, as some vendors never had usable APIs before now.

        • grue@lemmy.world
          31·
          3 hours ago

          Python environment/packaging sucks, but at least the language itself doesn’t.

          • esc@piefed.socialEnglish
            31·
            2 hours ago

            It’s fine actually, all of the problemswith python packaging and env are overblown to insane degree.

            • grue@lemmy.world
              1·
              5 minutes ago

              I used to work at a place that used Jython (which never got updated to Python 3, BTW) and was responsible for trying to keep that shit working even as various libraries started dropping Python 2 support.

              I still get a thousand-yard stare when I think about it.

              (Still worth it vs. writing actual Java code, though.)

              • esc@piefed.socialEnglish
                1·
                25 minutes ago

                Yep, they are.

                Just recently there was an article here, where a person claimed that recommended python tooling is inadequate because they needes to read two paragraphs of documentation. Endemic problem really.

    • Err(()).unwrap()@lemmy.world
      102·
      4 hours ago

      Fuck me, if my choice is between five flavours of Javascript, I’d rather use PHP. I’m developing a QML application and having to work around that abomination that the clinically insane want to call “arrays” in Javascript makes me want to fucking die. There’s also a QList type implemented by QML. It doesn’t help. Array.isArray(qlist) returns false.

      • rumschlumpel@feddit.org
        1·
        1 hour ago

        Node is the only JS framework out of these that could 1:1 replace PHP, Vue.js, jQuery and Ajax (aka vanilla JS) are all clientside which PHP doesn’t do at all, Bootstrap is a CSS library and Spring is Java. That said, clientside JS is usually an anti-user mess and both you and the user are usually better off not using it at all.