3 ms·

Well there's a strong argument to be made that there are plenty of people making web applications for information that doesn't need to be a web app. For example

Well there's a strong argument to be made that there are plenty of people making web applications for information that doesn't need to be a web app. For example: your generic company website does not need to be a SPA with every conceivable JS feature thrown in. You are only presenting me some information, HTML and CSS is more than adequate, stop making things more complex than they need to be. In these case, I'm more than happy to break their stuff as it's seemingly the only way to get them to pay attention.

Klathmon 8y ago
But that's an entirely different argument, and it's one that always muddies up the conversation whenever I bring this up. This isn't a blog that loads 50 trackers and tons of superfluous animations and video, this is an application which is designed to do things for the user. It's stuff like a music making app, or a medication reminder and tracker application that takes a lot of your personal information to help you find accurate dosages. It's stuff like games or offline-caching documentation browsers with IDE integration and powerful client-side search, or self-hosted home automation controller systems, or chat applications, or a barcode scanner app that checks for coupons for things that you scan in a web browser, etc... And again, i'm fine if you don't want to run one aspect of it, you are the client and I can't technically control what you do, but complaining that the car won't work when you ripped the spark plugs out is dumb, and a mechanic that goes around taking out spark plugs every chance he/she gets so that people won't speed isn't helping.