3 ms·
That's a mouthful.
by hajhatten 5y ago
That's a mouthful.
- szszrk 5y agoI've read that sentence three times and still were not sure if it's meant as a joke or not.
- ManuelKiessling 5y agoIt’s not – I like to summarize my tutorials comprehensively. I am not a native speaker though; I apologize if the sentence isn’t structured correctly or sounds inelegant. Corrections welcome.
- 9dev 5y agoI guess it's just the mind-bogglingly huge number of components involved to display HTML to someone :)
- ManuelKiessling 5y agoThat is absolutely true in some sense - then again, it is one solution where you start with a decent architecture that can grow and is scalable at linear, and very low, costs. If you were to really only deliver some HTML, it's overkill. For this reason, my blog is hosted with an old-school 90s-style FTP-backed "webspace" provider. But the architecture described is used to develop-build-deploy a full-flegded web-based application, with a persistence layer for user data and a potentially complex user-interface. And for this, having a sound architecture and tech-stack where you do not need to care about low-level server issues is, while certainly not a silver bullet, quite a productive experience.
- szszrk 5y agoOh, your language is perfectly fine. It's just that your article description reveals a sad truth about modern web technologies: it's a tangled mess.
- datavirtue 5y agoHighly complicated jacked up messes that you can't explain to your customers...and they don't care.
- seumars 5y agoThat’s frontend for you.