We don't "browse" the web anymore. We don't view "web sites" either. Let's face it, we run applications in what is essentially a bloated runtime with enough features to be its own OS.

@ryan659 Yes. That's for sure. Web browsers have grown into a rich client platform. There's a bunch of reasons for that, some better than others. Choice of technology aside, I still wonder whether this is all bad.

@z428 Web browsers have been on (then-) current platforms since the web has existed. But in that time the performance demands for web browsing have increased significantly. Does someone really need to write an application in the web, likely only optimised for one web browser (Chrome..) with relatively high resource requirements compared to a native application which doesn't need anywhere near as many features as a web browser provide?

Follow

@ryan659 Personal experience: People don't *want* to write applications on the web. They do so because in many ways it seems the easiest, sometimes the only feasible way if you need applications to be available from various (personal, corporate) networks, on devices of various kinds, on different operating systems in different versions. The web essentially has filled the gap left by the failure of platforms and approaches such as Java Web Start, rigid corporate firewalls (leaving HTTPS as in ...

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!