4 ms·
A tiny mostly static website written by one person certainly doesn’t need anything special. A website/webapp with millions of visits per day and a ton of stake
by Xenoamorphous 3y ago
A tiny mostly static website written by one person certainly doesn’t need anything special.
A website/webapp with millions of visits per day and a ton of stakeholders requesting features every week, on the other hand...
It all depends on the use case, like most stuff.
- oneeyedpigeon 3y agoAgreed. I wonder what the ratio is between the former and the latter...
- Dah00n 3y agoCrazy. I wonder how cars would look if stakeholders had a say.
- Lio 3y agoTotally agree. I think where complexity really creeps in is as you add multiple new content editors with varying skill sets. If you want a team of people that don't know HTML or rest of the stack to edit, manage and deploy it then you're going to need a more complex abstraction. The alternative might be a training programme for new staff in HTML, CSS, git and rsync. You're trading one type of complexity for another. As you say, it all comes down to use cases.