Lack of staff and funding likely led to the recent PHP security snafu; project has only one full-time employee, but that's just the tip of the iceberg — a dreary situation caused by services running old versions with no support
www.tomshardware.com
Never underestimate the power of complacency, the destroyer of internets.

70% of the world’s internet btw, but out-of-support deployments and little funding for permanent staff to manage the open-source project.

  • PorkrollPosadist [he/him, they/them]@hexbear.netEnglish
    4·
    13 hours ago

    MediaWiki is also a huge piece of PHP infrastructure which probably won’t disappear for a long time.

    With the separation of front-end and back-end development, the language becomes less important. The front-end is going to be JavaScript (or TypeScript) because that is the hell Google+Mozilla has consigned us to, but on the back end the only requirement is to throw up some REST API. This can be done in Node, Rust, Go, C++, Python, you name it. With CDNs, load balancing, cloud computing, and reverse proxies, everything is basically required to be swappable anyway. An API can be implemented in Python or Node, then ported to Rust if there is a performance justification. I can’t see a monoculture re-emerging the way things were 20 years ago.