3 ms·
I think what's contributing to the whole hourglass thing is that browsers do not play nicely with native/low-level primitives. It's bascially yet another waist
by the8472 10y ago
I think what's contributing to the whole hourglass thing is that browsers do not play nicely with native/low-level primitives. It's bascially yet another waist above the OS waist (browser APIs) and the IP waist (HTTP).
Develop a nice decentralized solution? Maybe it involves some UDP multicast? Forget the browser.
Want to have two devices on the network talk to each other? Bounce it through a cloud provider.
Want to use "everything is a file"-files? The browser's interaction with the filesystem is incredibly clumsy.
So if you wanted to use the full strength of linux/any other lower layers, this would hamper adoption.
- sievebrain 10y agoThe browser is a terrible app platform that 'won' primarily because the incredibly minimal levels of holistic design in it meant everyone could agree on it, because doing so gave power to nobody in particular. The downside of that approach is, well, it's just a mishmash of things that don't work well or fit together properly. It's not even really decentralised. From the birth of the web it was driven by Netscape, then Microsoft, then MozCorp, then Apple for a while, and now Google, with bits of Opera thrown in occasionally. There has always been at least one dominating browser maker adding whatever random features they thought would be cool at the time.
- digi_owl 10y agoThere was also the case that admins routinely blocked all ports on the company firewall, except for 80 (http). Thus funneling anything and everything through the browser became the easiest way.