you are viewing a single comment's thread
view the rest of the comments
[–] 31 points 16 hours ago (5 children)

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.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 15 points 15 hours ago (3 children)

    If its so antiquated why is it still used? For a lot of things its perfectly fine. Even this vulnerability is just a case of run the update command for your package manager.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 21 points 14 hours ago* (last edited 14 hours ago) (2 children)

    It's still used because momentum is a powerful factor. That doesn't make PHP better, but it can make it a more expedient choice.

    PHP is a preprocessor that grew too big for its britches. It's a monolithic monster that runs only one thread per request in an interpreter. It works well enough if you need to manage the data of an internet forum, but it becomes increasingly unsuitable as the task's complexity grows. If you need threading or background tasks, or if scalability is important, PHP is not it; just read any number of Nextcloud vs OpenCloud comparisons.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 13 points 14 hours ago

    "one thread per request" , "interpreter"

    (Looks confusingly) That's JS and Python as well

    PS: being obtuse on purpose, but PHP lends itself well to typical requirements of web hosting and you can always call out to a diff process if needed

  • source
  • parent
  • [–] 4 points 12 hours ago

    You realize that the language evolved over the years and it's not even close to the same language it was 15 years ago?

    The fact that you also mix frameworks and languages also tells me that you have no idea what you're talking about

  • source
  • parent