13 ms·
Unpopular opinion... but I think this is a too limited view of the web. My contrary opinion is that the actually important feature of the web is the URL, and th
by flohofwoe 7y ago
Unpopular opinion... but I think this is a too limited view of the web. My contrary opinion is that the actually important feature of the web is the URL, and the important feature of the browser is that it provides a sandboxed platform for running untrusted code without a builtin "walled garden moral police".
It would be nice if operating systems would be exactly that, but for some reason "commercial" OS vendors are not able or willing to provide a safe "native" sandbox completely uncoupled from curated app stores.
The ability of a browser to be a document viewer with a very limited layout system should be implemented in an optional layer on top of a bare bones browser.
Again, this should all be provided by the underlying operating systems (click an URL and instantly run cross-platform applications in a safe sandbox), but for some reason we didn't get that. It's the same with Electron apps by the way, those wouldn't exist if operating systems would come with cross-platform UI frameworks that are actually better than the unholy mix of HTML+CSS+JS. But Microsoft, Apple etc... had decades to get their act together without delivering.
- ecmascript 7y agoI don't think that is an unpopular opinion, since I am of the same. I agree with you that the URL is the most important feature of the web. Without it, you could just as well deploy native apps because it wouldn't really make that much of a difference. Without javascript and a heavy client side, I wouldn't have a job today since the application I build is simply not possible to create with just html+css. Sure there are many web pages that don't need to be a SPA, but a lot of other webpages do need it. I think an increasing amount of webpages are not simply text documents but we can easily see a move from traditional applications to web applications. It's obvious why, it is truly a "write once, run everywhere" scenario, it's easy to scale on many different devices and there is little to no advantages to write a native app in most circumstances. The document web has already been done, just use wordpress or whatever framework to create those sites but the new exciting web for me is the more interactive web where we can seriously move heavy apps into the browser.
- godshatter 7y agoWhat we need, in my opinion, is a new protocol. Leave http(s) for documents and make a new protocol designed from the ground up for interactive applications. That solves the problem of trying to shove an application into a document viewing sub-system and should allow for more creativity and efficiency, depending on what this new protocol turns out to be. What's happening now is like trying to force ftp to show documents, with markup, and forms, and so forth when it's just supposed to transfer data.
- krapp 7y agoThe possibility for HTML documents to support inline scripting was considered even prior to HTML 4[0]. The script tag itself is decades old now, it's supposed to be there and it's as legitimate an element as any other. The web was never intended to only ever be static, nor is scripting in the browser somehow a corruption or aberration of the web's original purpose. If anything, the web should have been a lot more programmable[1] than it turned out to be. [0]https://www.w3.org/TR/2018/SPSD-html32-20180315/#script https://www.w3.org/TR/2018/SPSD-html32-20180315/#script [1]https://eager.io/blog/a-brief-history-of-weird-scripting-languages/ https://eager.io/blog/a-brief-history-of-weird-scripting-lan...
- ecmascript 7y agoMaybe that would make it better, maybe not. It's hard to get everyone on the same page working together on a platform that noone ownes. If it was easy, there would have been several protocols in use already. I am content with what we got and are happy about it. I think it works pretty great after all.
- godshatter 7y agoI'm not so happy with it, since I'm tired of trying to figure out which domains to allow javascript from when practically every page has a list of a dozen or more. I'm tired of trying to run pages that don't work with any of the browsers I have access to on linux, despite html being a standard. The whole paradigm seems broken to me. It just feels like a monumental kludge.
- BlueTemplar 7y agoIsn't it pretty hacky to use a Web browser for that instead of a dedicated virtual machine ?
- ecmascript 7y agoFor what exactly?
- janpot 7y agoCouldn't agree more, html should be just one implementation amongst others. It's good for documents, it's lousy for richer experiences. The rich experience shouldn't be built on top of HTML, it should live next to it.
- pistolpeteDK 7y agoThis. absolutely this! We didn't get the crossplatform UI framework we needed, we got the one we deserved. SwiftUI looks amazing - but again - apple only. React looked promising, but mainly for desktop, and it's not without its own issues. I think the W3C are a big part of why the web works so well cross-platform... even though the web was supposed to be "so much more". It's quite hard to imagine a similar kind of body for cross-platform UI frameworks.
- heavenlyblue 7y agoWhat makes React inherently un-mobile except the fact that all browsers have a touch timeout thus making UI seemingly slower?
- pistolpeteDK 7y agoDon’t know if it’s unmobile per se. But it’s heavy, JS wise, tends to promote SPAs, and can be quite tough to get to play well with a hybrid. The react team seems to put their effort in React Native. And that might the only framework I’d never ever ever “touch” again - pun intended:) We do use react for some mobile stuff, the issue seams to be that you still need a lot of other stuff and your app/UX still feels a bit like a 2nd class citizen
- rocky1138 7y agoHave you ever written anything in Qt?
- yiyus 7y agoI've recently been using it and I am very disappointed. Some tasks that should be totally trivial are incredibly hard to get right and require platform specific solutions. Nothing unsolvable, but I was expecting a much more straightforward experience from a product that has been promoted as the cross platform toolkit since the 90s.
- danieldk 7y ago
- nickjj 7y ago> My contrary opinion is that the actually important feature of the web is the URL, and the important feature of the browser is that it provides a sandboxed platform for running untrusted code without a builtin "walled garden moral police". Flash tried to do this 15-20 years ago. Flash was basically "here's a canvas, do whatever you want within reason". It had its use cases back then but the general web vastly preferred good old HTML and eventually CSS and JS. There's a lot of value in having constraints, especially when those constraints (HTML) are specifically designed for displaying documents.
- lmm 7y agoThe general web loved Flash for cases where you needed an application rather than a document. It wasn't appropriate for everything, and it was unfortunately very difficult to mix Flash with general HTML, but in many ways it was better than today's web for both creators and end users.
- ktpsns 7y agoSecond that. For the user, flash applets where super easy to block in general and to whitelist on pages where you wanted to use that particular flash application. Basically the same was true with Java. And for a certain extend JavaScript -- until the ugly DHTML menus arised and websites stopped to be usable without JavaScript. Nowadays there are only two options: Either you block JavaScript --- and percieve a 1995's web view, in general --- or you let it run on your browser, having tons of programs running which you probably don't want (ads, tracking, that particular application that replaces flash).
- kevin_thibedeau 7y agoThe 1995 view is superior. It loads fast, doesn't hog CPU, never does anything unexpected, and has limited tracking capacity. I cringe whenever I browse without NoScript. If your pages can't render in my sandbox I just go somewhere more sensible.
- 7y ago
- snlacks 7y agoNo one's delivered? There were and are plenty of platforms for full apps on the web. All of them require: loading each time or elevated privileges above the normal browser. This is not the reason they haven't taken off. Security isn't the reason either. It isn't used because it's just not how the suppliers of content nor consumers of the web want to use the web. If they want a full featured app, they use it. Even with super fast speeds, latency and minimal startup time still make the browser unattractive for this. Web users and content providers want linkable documents. I'd argue that the modern browser stack is so good that we see installed apps adopting html/css/js for the presentation layer.
- flohofwoe 7y agoIMHO the word "installed app" shouldn't even exist. What's the use of "installing" an application these days? Of course this goes hand in hand with an instant start (no dreaded splash screens please), and not having to download gigabytes upon gigabytes of data upfront. Modern web apps might be bad at this, and browser engines might be bloated, but native apps aren't any better (even heavy web pages still load many times faster than - for instance - starting Visual Studio or Photoshop).
- snlacks 7y agoWhat's the issue? There's two that are unavoidable. The maximum speed of moving data from one physical place to another, moving data from the hard drive to the motherboard and the ram to the cpu/cache is faster than from the internet to a computer. To he speed of light is still noticably slow when you're making round trips to get data. The other issue is configuration, even if automated, software needs to make decisions about how to deal with different hardware and system differences. This takes time to bootstrap after initial load increase time to usuability or it can be done on the fly slowing down the interactions.
- cesarb 7y ago> What's the use of "installing" an application these days? Once I "install" an application, for example libreoffice: - It works even if I do not have a working Internet connection (or back in the day, even if I had removed the original media from the drive); - It works even if the original is gone. That is, by "installing" an application, I gain a permanent, offline, working copy of it.
- amelius 7y agoIndeed, a browser should be just a sandbox, nothing more. All the HTML+CSS+JS stuff only makes browsers difficult to secure, and also causes bloat and performance issues when they are not needed. Furthermore, all these hairy web specifications cause compatibility issues, and are a barrier to entry for new browser makers. If people want HTML or CSS or JS, then they should implement these inside the sandbox. In practice, this would mean that developers would simply include one of the standard libs for rendering HTML, etc., and these standard libraries can be cached by the browser, so their use does not cause performance/bandwidth penalties.
- AnIdiotOnTheNet 7y agoI agree. If we want an application platform, let's have something designed first and foremost to be an application platform instead of the garbage fire we've bolted to the skeleton of HTML. Here's how you do it: create the new platform and its spec. Include an open 'document rendering engine' to replace that portion of the web. For backwards compatibility, go ahead and port a web browser to the new platform. For forwards compatibility, port the new platform to the current web.
- rocky1138 7y agoOk, but that isn't "the web." You are completely free to write and launch a new app that does this today. Just don't try and shoehorn it into my web browser.
- amelius 7y ago> Ok, but that isn't "the web." It's "the sandboxed, browser agnostic web".
- BlueTemplar 7y agoI'm not sure that it can be called "the Web" if it doesn't have directly accessible pages linked by hypertext, instead having a single page/app for instance (even if it runs on the top of the HyperText Protocol...) We're getting into non-Web Internet territory here...
- brightball 7y agoThat view of the browser is what I want to have. It blows my mind that we still have to tell people “don’t click links in your email” because it’s still possible for something terrible to happen if they do.
- u801e 7y agoThe real question is why should links in an email message be clickable? Restricting email messages to plain text would make it much more difficult for attacks like that to succeed.
- dgellow 7y ago... and make emails completely useless.
- dijksterhuis 7y agoEver head of copy & paste? Won’t make them “useless”, maybe inconvenient for non-security minded individuals.
- dgellow 7y agoif You make emails inconvenient for non-security minded people by removing something as important as links, you will push mainstream users to move away of the medium (because other way to communicate will definitely support links and not force people to copy paste), which doesn’t help or solve anything.
- BlueTemplar 7y agoURLs are plain text... Can also easily be clickable, depending on your e-mail software.
- u801e 7y agoThey are, but some email clients will display text that doesn't match the original URL. Hence the advice to hover the mouse pointer over the link and tread the original URL text that way.
- pjc50 7y agoI'm not quite sure how this relates to the original article, but: > the important feature of the browser is that it provides a sandboxed platform for running untrusted code without a builtin "walled garden moral police". > for some reason "commercial" OS vendors are not able or willing to provide a safe "native" sandbox completely uncoupled from curated app stores. The key word here is absolutely "unwilling". All the platform vendors want platform lock-in, they don't want a general purpose platform. Microsoft originally tried to do this to the web with ActiveX, before even Flash. At least Flash was slightly cross-platform in that Adobe provided Mac and Linux versions. These days no platform vendor is going to give up their 30% cut voluntarily. In a world of fully general app sandboxes, you can switch out your hardware and OS at any time without disrupting your life or business. Therefore those are commoditized, and their price drops to the marginal cost of production - which for software is zero. (Also I think CS theory took a while to catch up to practical security; everyone used to teach the model in which multi-user systems were trying to protect users from one another, not one where a single-user system is trying to protect the user from predatory apps, viruses and potentially unwanted programs.)
- fipar 7y ago> In a world of fully general app sandboxes, you can switch out your hardware and OS at any time without disrupting your life or business. Therefore those are commoditized, and their price drops to the marginal cost of production - which for software is zero. I think software's marginal cost of production is zero only if no updates/fixes are ever needed. I know it sounds like nitpicking but just think of all the vulnerabilities discovered, specially the closer software gets to the lower end of the stack. Even if an OS could suddenly stop adding features and still be viable in the market, the cost of patching it as holes are discovered is certainly not zero.
- thinkloop 7y agoThe zero mainly comes from the ability to scale for free. Sure it costs a few million bucks to maintain Linux (or whatever), but when divided by billions of copies the per unit cost becomes effectively zero.
- 7y ago
- bo1024 7y agoI'm inclined to disagree, but I guess the real problem is that webpages on the internet are being forced to serve both purposes. Paradigm 1 - interconnected, hyperlinked web of text-and-content-based documents: open, accessible, amenable to indexing and tooling and so forth. Paradigm 2 - delivery vehicle for cross-platform, full-featured, somewhat-security-sandboxed, applications. I agree with the article that it's sad if Paradigm 1 is trampled to make way for Paradigm 2, just because (as you point out) we haven't been able to develop a viable alternative. In theory these could coexist, but the point of the article is people are being trained in Paradigm 2 and try to use it for purposes that are much more suited for Paradigm 1. Just as sad, Paradigm 1 is more oriented around decentralization, giving power, options, and information to the user; Paradigm 2 is often exploited for lock-in, control over user's decisions, collecting information about the user, etc.
- rthomas6 7y agoDon't we kind of have Paradigm 2 on our smartphones and tablets? It's not perfect but it's something.
- EGreg 7y agoWe should replace DNS with DHT, then we can have content addressable (or otherwise verified) apps sideloaded or loaded in chunks from anywhere like in BitTorrent or Dat. To me, the Browser is the most widely distributed sandbox runtime ever! It’s just missing a few crucial things we plan to add soon :-)
- JBiserkov 7y agoHave you seen https://github.com/staltz/dat-installer https://github.com/staltz/dat-installer ? It can be used to update itself, too :-)
- bo1024 7y agoI agree it's better in some ways than the desktop programs ("apps") situation
- 7y ago
- whoisthemachine 7y agoI think you need to take into context the history of browsers vs. operating systems... operating systems were always a platform, while browsers started as consumers of an electronic document standard. That being said - I agree with your ideal, and I don't think it's far off. HTML as a view engine combined with WASM as a cross-platform runtime can enable truly cross-platform, industry-standard native applications. I think it's only a matter of time until Electron apps morph into cross-platform native apps running off of a thin WASM layer. Once those are available, then the OS vendors will have a huge competitive advantage if they develop fast native WASM runtimes.
- scarface74 7y agoIt would be nice if operating systems would be exactly that, but for some reason "commercial" OS vendors are not able or willing to provide a safe "native" sandbox completely uncoupled from curated app stores. Apple is going down this route with code signing and granular permissions with Macintosh applications that don’t have to be part of the Mac App Store and there is still whining from geeks that this is leading to a walled garden, even though there are approved ways to work around it. It's the same with Electron apps by the way, those wouldn't exist if operating systems would come with cross-platform UI frameworks that are actually better than the unholy mix of HTML+CSS+JS. But Microsoft, Apple etc... had decades to get their act together without delivering. One of the problems with Electron is that it’s the same interface everywhere. I don’t want the same interface on a Mac that I have on Windows.
- gear54rus 7y agoI'm sorry but you have to be special kind of delusional to think apple is doing something to move away from walled garden lol. They haven't done it because it doesn't bring any benefits to the greedy corps, and apple is the worst offender with their dumbed down, shackled os
- scarface74 7y agoDid you read the post or are you just responding to your own prejudices? The parent post said that OS vendors should have sandboxes without an App Store. Isn’t Apple doing exactly that with the Macintosh? The Mac App Store is optional and despite all of the conspiracies, it was introduced over 8 years ago and you can release an application on the Mac just as easily today as you could then. So how is MacOS - a real certified Unix OS “dumbed down”?
- BlueTemplar 7y agoWell, I remember people warning that having an official Android Market would make distributing via side loading not a viable option... Lo and behold, these days Fortnite gets criticized for being delivered via an .apk because it's "unsafe" !
- snek 7y agoThe reason browsers use the document as a building block is to provide a consistent and accessible UI to everyone using your site. This is the exact same thing that Windows, Apple, Android, etc do with their UI frameworks that they recommend you use. It also provides the ability for websites to safely degrade on older browsers because unknown elements can still be rendered in the correct hierarchy. Now in both cases, you can just make your app a fullscreen canvas or opengl/metal viewport or whatever and manually render everything to that while manually handling user input, but you lose interactivity, accessibility, extensibility, etc.
- flohofwoe 7y agoPlatforms should provide the necessary low-level APIs to hook into their accessibility- etc... features without having to use their high-level UI frameworks, and they should provide lower-level services like high-quality text rendering. Mostly this already works, I can open a standard file dialog, or copy data into or out of the system-wide clipboard. If there are any APIs for accessibility missing (e.g. for hooking into screen-readers), I would consider that a bug on that particular platform. There's no reason that applications which use the system UIs should behave any different from applications using custom UIs.
- snek 7y agoThere are ARIA attributes which let you customize the advertised meaning/intent of an element, but there is nothing to, say, mark that a particular location on the page should be considered a button. As far as I'm aware, this matches how Android, Windows, iOS, etc work. There are so many parts that go into the accessibility of an element, handling tab index, handling keyboard input, handling screenreaders, spoken voice prompting, etc, that a custom solution usually ends up being detrimental to the user's experience.
- saagarjha 7y agoThere's no way a platform can provide accessibility for arbitrary pixels you throw onto a screen. You could, by yourself, using the low-level accessibility APIs, but you likely won't since it's a lot of work. Hence the push for using platform UI components: they inform the framework of your intention, and in return this information helps it provide you with better accessibility.
- agumonkey 7y agoWell, beside formatting, html is <a href="...">
- mpweiher 7y ago> My contrary opinion is that the actually important feature of the web is the URL, As others have pointed out, that's hardly a contrary opinion. To quote Roy Fielding's Dissertation (p 109). "Uniform Resource Identifiers (URI) are both the simplest element of the Web architecture and the most important." https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding...
- reallydude 7y ago> As others have pointed out, that's hardly a contrary opinion. Opinions are almost universally contrary, despite the knowledge that the URL can be a tool. How often is it put forth that the URL is meant to be indempotent or the URL is supposed to be mapped to another routing system etc. The number of commercial sites where the URL is a field you are meant to manipulate (other than say search engines and even they don't point it out for you) is so small as to be significant.
- deleted 7y ago[deleted]
- z3t4 7y agoApple planned to use web apps for iOS but developers wanted bare metal performance, and users also want bare metal performance. So dont blame the platforms, blame users and developers. As a Linux user you can however restrict what the app can do using Apparmor.
- old-gregg 7y ago> the browser is that it provides a sandboxed platform for running untrusted code Unfortunately it's not true. Zero day exploits happen all the time, even the recent Intel CPU vulnerabilities were exploitable via JavaScript. Morevever, some harmful effects of arbitrary code execution cannot be mitigated (like the drained battery or user tracking), that's why I have recently adopted a view that code execution on web pages is just a Bad Idea and my non-work browsers are configured with JS turned completely off. This gives me nearly 2 full days of battery life on my phone and I'm less worried about privacy/security aspects of visiting random web sites. Unfortunately, even within the last year, I'm noticing that more and more web sites simply serve me a blank screen without JS enabled. This forces me to stop using such sites, which is gradually reducing the size of the usable web for me. My only hope is for a new trendy server-side rendering fad to come along and rescue the Internet :)
- jdofaz 7y agoI'm aware of at least one project to do that with Ember https://ember-fastboot.com/#how-does-it-work- https://ember-fastboot.com/#how-does-it-work-
- deleted 7y ago[deleted]
- wwweston 7y agoImagine that in the 90s, a "URLs only" web took off -- not too hard to envision, really, considering how many sites there were that were giant slabs of sliced images with hotspots for links between, or how Sun was pushing the vision of URLs essentially indexing Java client apps. If that had ended up as the dominant paradigm... Google (or a search engine like it) wouldn't exist. A URLs-only web, one that sees the browser as nothing more than The VM That Lived™, is actually the more limited vision.
- the8472 7y ago> It would be nice if operating systems would be exactly that, but for some reason "commercial" OS vendors are not able or willing to provide a safe "native" sandbox completely uncoupled from curated app stores. Windows 10 comes with a VM-based application sandbox. But it's meant for powerusers and has to be explicitly enabled https://www.windowscentral.com/how-use-windows-sandbox-windows-10-may-2019-update https://www.windowscentral.com/how-use-windows-sandbox-windo...
- skywhopper 7y agoThe web browser _is_ the "safe" sandbox. Your dream of competing OS vendors coming together to build a standard UI platform makes no sense whatsoever. The current state of web apps is mostly a factor of developers being willing to do any amount of work whatsoever to avoid having to learn how to do things differently than they already know (ie, writing good native apps for multiple platforms, which would require learning multiple frameworks, so instead they create their own abstracted framework within a sandbox.
- tracker1 7y agoChromeOS is pretty close to what you are talking about... yeah, it's still an App store, but IIRC, you can add an "app" from any URL. It would be nice to see a more open version of what Adobe AIR tried to do, but with node/electron at the core. Unfortunately $VERSIONS makes it difficult to support well with a common runtime, but would still be well worth seeing. I don't mind Electron too much, current (for 5+ years or so) desktops support running a handful of them without issue (provided at least 8gb ram). I think that once a few quirks are worked out, we may well see a "one runtime to rule them all" with WebAssembly. WASM + Sandboxed FS + Canvas/WebGL could go a VERY long way towards a lot of application use cases. There's been a lot of work underway for this type of thing and it could be very interesting to say the least. I do think we'll wind up with an XML based markup for UI over the top, maybe a ReactNative-like syntax for WebAssembly+Canvas or WebGL would be very cool.