I rebuilt the same project after 15 years: What changed in web development
1–10 of 18 posts
Re: I rebuilt the same project after 15 years: What changed in web development
#2 > 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?
Re: I rebuilt the same project after 15 years: What changed in web development
#3Re: I rebuilt the same project after 15 years: What changed in web development
#4Re: I rebuilt the same project after 15 years: What changed in web development
#5The 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.
Re: I rebuilt the same project after 15 years: What changed in web development
#6Re: I rebuilt the same project after 15 years: What changed in web development
#7// > 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 suppos…
Regarding Docker, we have quite a bit running on a single EC2 instance: PostgreSQL with PostGIS (about 13 million rows), Redis, Nginx, theAPI and web app. Using Docker Compose lets us keep everything versioned and spin up or redeploy the whole stack in seconds. Without it,we'd dealing with dependencies manually, and that's where things tend to get messy fast.
Re: I rebuilt the same project after 15 years: What changed in web development
#8It was still likely possible to have retained the originality and novelty of the first site without succumbing to the plague of our contemporary blandness.
The tradeoff was deliberate though. Serving 261 countries in 4 languages with an API and MCP Server pushes you toward structure over personality. But I do miss some of that original energy.
Re: I rebuilt the same project after 15 years: What changed in web development
#9Personally really liked your maximalist design form 2011: it was original, it looked fun. 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.
We're trying to keep some of that. You can browse countries, compare them, explore cities, look up universities. It's not just an API docs page. But I hear you. :)
Re: I rebuilt the same project after 15 years: What changed in web development
#10Stop 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.
The site runs in 4 languages (English, Spanish, Portuguese, Italian) and covers 261 countries. Back in 2011 we relied on the machine translators available at the time, you probably remember how rough those were for the end user. AI finally lets us produce content that people can actually read in their language without those painful translation artifacts.
I apologize if that's off-putting, but the alternative would be less content for fewer people, or content full of bad translations.