Comment

Comment by fifticon

I will add to the hundreds of comments.. Whatever happened to the thin waist of the wasp, in interfaces.. So, we design a system, for showing and interacting with data over networks. When we start with this, the outset is defining say a character set of 12-20-26 alphabet letters. Already with that, you could exchange information; at least the greeks could. We also managed to design the gopher protocol, the early world wide web protocol, telnet, and (god forbid) X-Windows. Early www already had some complications: Support for images, and form controls. A lot of these things were possible to do, even on a commodore 64.

But still, take a look at the monstrosities we have built since, presumably to serve the same purpose.. It now takes an effort apparently bigger than that required to land a controlled drone on the moon, to deliver a working/full WEB BROWSER..? An application supposedly intended to allow you to browse pages of mixed text and images, require approximately --two-- (nah, one?) full virtual OS environments to function, a turing-complete sub-language, and is more complicated to build than the OS's that host it..

I often wonder if all that was really necessary. It looks to me like we have made the 'interface' the most complex part of it all, leading to almost everybody just piggy-backing on the chrome investment (or what one chooses to call it.. It is an MS-like market control mechanism is what it is).

parent fifticon 1 year ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton