• anewfox@lemmy.zip
    1064·
    4 days ago

    i maintain that the reason everyone on the internet hates php is because the devs who write php code all day go home to their spouse and kids after work instead of arguing on the internet.

    cuz, nobody really treats any other language like this, even though… gestures to npm and pypi’s constant security flaws

    • expr@programming.dev
      47·
      4 days ago

      We are fully capable of thinking PHP, NPM, and PyPi are trash simultaneously. Though it should also be said that only PHP has had decades of security flaws in the language itself, rather than a package manager.

      It’s just a very poorly designed language with countless footguns and fucking idiotic standard library functions, on top of being a running joke, security-wise.

    • deegeese@sopuli.xyz
      25·
      4 days ago

      If you treat programming as a job, PHP is good because it lets you get things done.

      If you treat programming as a craft, PHP is gross for a whole bunch of reasons.

    • boonhet@sopuli.xyz
      17·
      4 days ago

      cuz, nobody really treats any other language like this, even though… gestures to npm

      I usually see more Javascript hate than PHP hate these days, mostly because everyone had forgotten that PHP exists.

    • lobut@lemmy.ca
      16·
      3 days ago

      JavaScript gets a lot of shit and part of that’s from me, a JavaScript dev.

      • ChickenLadyLovesLife@lemmy.worldEnglish
        4·
        3 days ago

        The most insane thing I ever worked in was Qt Creator, which used JavaScript for the UI and C++ for the lower level back end stuff. The switching your brain had to do to go back and forth between the two languages was remarkable. I think Qt is the real reason the suicide and alcoholism rates in Finland are so high.

        • lobut@lemmy.ca
          2·
          3 days ago

          I used Qt before as a library for C++, never knew there was a Qt Creator but that was eons ago.

          My heart goes out to all those Fins.

    • Skullgrid@lemmy.world
      14·
      4 days ago

      Nooo but how do I hecking pad things on the left?!?!!!1!! I need 600 npm packages before I can put a div on a page

    • carrylex@lemmy.world
      41·
      3 days ago

      i maintain that the reason everyone on the internet hates php

      let me finish the sentence:

      …because they knew about the vulnerability since 2024 and simply forgot about it.

    • KubeRoot@discuss.tchncs.deEnglish
      22·
      2 days ago

      Or because people had bad experiences with it. Like hosting software built in PHP, which seems to have uniquely terrible hosting mechanics and version and dependency management.

        • KubeRoot@discuss.tchncs.deEnglish
          1·
          1 day ago

          “Isn’t” what? If you’re referring to the hosting experience, I’m talking based on experience setting up some PHP software from the last year or two. Unless you just slap docker on it, it seems to be a pain getting php running, it might want a very specific version (extra pain to get that specific version running), and I remember dependency management giving me trouble, possibly also being weird with the older version of PHP.

          • SkaveRat@discuss.tchncs.de
            1·
            18 hours ago

            *It really isn’t

            every project I set up in the last 10 or 15 years was just “composer install” and done. (plus whatever configuration like DB etc you need)

            Sure, might need to check what minimum version you need, but backwards compatibility is pretty good, so along a major version you can often just pick the latest

            I don’t know what weird projects you checked out, but that might just be on them instead of the language

  • farmgineer@nord.pubEnglish
    17·
    4 days ago

    I’m trying to find a new job here in Japan. So much of it is PHP and Ruby. I’m already depressed enough as it is!

    • ChickenLadyLovesLife@lemmy.worldEnglish
      5·
      3 days ago

      I had a coworker adopt Ruby for a major project about 20 years ago. He didn’t know it, nobody on his team knew it, and nobody else in the entire state had ever heard of it, so when the project failed after two years there was nobody around who could save it. I’m sure Ruby (on Rails) is a perfectly viable language/platform, but you wouldn’t know if from these guys.

      • farmgineer@nord.pubEnglish
        2·
        3 days ago

        Lots of stable stuff in Japan is (or until recently was as at least some omve to go or java) ruby. It’s not that it’s horrible per se, but it’s not going to be the most performant in some situations. I worked in grails in the past (the jvm version using groovy unsteady of ruby) and it’s not the worst.

        As someone with his own preferences, I would never implement something in a language no one else knew, at least without leading courses on it first and confirming ability. Bus-factor 1 is no good.

        • ChickenLadyLovesLife@lemmy.worldEnglish
          1·
          3 days ago

          TBF, my colleague also managed to produce complete disasters in a language (C#) that he knew, the entire company knew, and lots of other programmers in the area knew very well.

          • farmgineer@nord.pubEnglish
            2·
            3 days ago

            Yeah, when process and oversight fail, that can absolutely happen. As someone who’s been in the industry for 20 years, though, doing a thing that puts me as a single point of failure in production is just irresponsible. Maybe this is why I can’t find a job; too much sense (I work for a shitty japanese company and want out)

      • farmgineer@nord.pubEnglish
        5·
        3 days ago

        The guy who made ruby was japanese so lots of adoption and documentation. I spent years doing perl in the past and ruby was based on that, but I generally prefer compiled to interpreted. I would take ruby over php though