> I have to assume you have never written a large scale project for the web?

Can I ask, what classifies as large scale project for the web?

I previously created and exited a trading platform that did billions in transactions via our servers with thousands of users streaming real time data. It's certainly more complicated and "larger" than 99.9% of things you'll ever do. So does that qualify?

If so, I can tell you that I did it with PHP and no JS frameworks. Hosted on a couple of VPS servers from digital ocean. From idea to execution to exit in ~9 months.

You know what the weird part is? I see your take repeated over and over by "shovel peddlers" and grifters. And every single time it comes with 0 substance or merit.

▲

vanviegen 3 days ago | parent | next [-]

> I can tell you that I did it

The 'I' here reveals that this is indeed not a large scale project, though perhaps impressive. When working on a piece of software with tens of people, using more tooling really does makes sense.

▲

timeon 3 days ago | parent [-]

'I' here reveals that it is on topic in context of posted article. Which is purpose of this thread.

Sorry I do not want to sound like a dick re-stating the obvious but threads often are going off the rails and I find it bit absurd.

	▲	vanviegen 2 days ago \| parent [-]
		I've tried to parse your comment from various perspectives, but can't seem to make sense of it. A 9-person-month project is just not a large scale project by any definition.

▲

2 days ago | parent | prev | next [-]

[deleted]

▲

sublinear 2 days ago | parent | prev [-]

Congrats to you, but yeah the other comments have already said it.

I'm talking about projects that have a lot of people working together across multiple teams where not everyone is even a dev. This is routine with e-commerce. The build will have assets from design teams, copywriters, analytics scripts, etc. and a CMS isn't always the correct or even scalable solution for that. The original commenter I was replying to seems to be stuck in the past. These days it can all be done with a simple CI script, but yeah ultimately that means build tools.

Above all else, like I said in another comment, there cannot be server-side rendering because it deploys to a CDN for hosting. These are projects that require huge amounts of content, but need to stay responsive. The final build result and upload is many files, but the initial load for the site is minimal JS and HTML to render for the user.

> billions in transactions via our servers with thousands of users streaming real time data. It's certainly more complicated and "larger" than 99.9% of things you'll ever do.

Large scale doesn't have to be complicated, but it does need some way to coordinate the effort which means there's a build and there will be requirements that are beyond any one person's control and expected for the modern web.

I want to also point out the obvious that there's insane money being made in e-commerce since it's now the default way to shop for everyone. It's a very common type of web project and if the typical HN web dev is getting paid a decent salary it's likely that the sites they maintain have several orders of magnitude more users than what you're talking about.