> The backend: from simple to absurdly complex...
> Here's where the real inversion happened...
> 2011 stack: PHP...
> 2026 stack: Next.js...
Welp, it's your choice to complicate the stuff. You could easily keep the PHP and just add ReactJs or even better - VueJs.
Have you ever checked out Laravel at all, considering your Rest API endpoint even?
And why use Docker in Production of personal projects that are supposed to be used for high load? Why not deploy on a finite VPS/VDS environment existing explicitly for this single workflow? Why add a separate layer in already isolated environment?
It was still likely possible to have retained the originality and novelty of the first site without succumbing to the plague of our contemporary blandness.
Stop using AI to “write” slop. It’s immediately obvious from the kicker of the article. Save us all some time and just post the bullet points you gave to an LLM.
16 comments
Have you ever checked out Laravel at all, considering your Rest API endpoint even?
And why use Docker in Production of personal projects that are supposed to be used for high load? Why not deploy on a finite VPS/VDS environment existing explicitly for this single workflow? Why add a separate layer in already isolated environment?
The posts rationalization of getting out of the way of the content makes sense and if there is the primary motivation it is perfectly rational.
But as a human user: I would like to explore the web again.