←back to thread

The story of Max, a real programmer

(incoherency.co.uk)
129 points surprisetalk | 1 comments | 30 Jun 25 12:57 UTC | HN request time: 0.205s | source
Show context
brazzy ◴[03 Jul 25 13:11 UTC] No.44454676[source]▶
Early 2000s PHP was a DSL for very simple web apps. So it's no surprise it excels at that.

People soon found out that it was not very good at complex web apps, though.

These days, there's almost no demand for very simple web apps, partially because common use cases are covered by SaaS providers, and those with a need and the money for custom web apps have seen all the fancy stuff that's possible and want it.

So it's no surprise that today's languages and frameworks are more concerned with making complex web apps manageable, and don't optimize much (or at all) for the "very simple" case.

replies(3): >>44454915 #>>44454987 #>>44455055 #
timw4mail ◴[03 Jul 25 13:47 UTC] No.44455055[source]▶
I disagree. I would say most of the migration from PHP was due to the appeal of one language for frontend and backend, and fashion/hype. PHP is still very usable for server-side rendering and APIs. You say "very simple" as if you can't have complex systems with PHP.

I see the current state of web development as a spiral of complexity with a lot of performance pitfalls. Over-engineering seems to be the default.

replies(1): >>44456530 #
1. brazzy ◴[03 Jul 25 16:12 UTC] No.44456530[source]▶
> I would say most of the migration from PHP was due to the appeal of one language for frontend and backend

Definitely not. PHP lost far more market share to Java,C# and Ruby on Rails than to node.js

> PHP is still very usable for server-side rendering and APIs.

Not "is still", but "has become". It has changed a lot since the PHP 3 days.

> You say "very simple" as if you can't have complex systems with PHP.

With early 2000s PHP, you really couldn't, not without suffering constantly from the language's inadequacies.

> I see the current state of web development as a spiral of complexity with a lot of performance pitfalls. Over-engineering seems to be the default.

I don't disagree, but that seems to happen most of all in the frontend space.