3 ms·
What definitions of "application" and "document" are being used here? Banking websites are applications in terms of their functionality - they're certainly not
by krapp 8y ago
What definitions of "application" and "document" are being used here? Banking websites are applications in terms of their functionality - they're certainly not documents. At least not the parts where I can access and modify my account.
- Retric 8y agoClient side code including third party media players etc. IMO it's a simple question 'can you do the same thing with a sheet of printed paper.' I can fill out paper forms and hand them to someone just fine. Don't forget a Check is really just a piece of paper with a form on it.
- krapp 8y agoSo a spreadsheet running in the client with javascript or WASM would be an application, but a spreadsheet running on the backend wouldn't? I'm not trying to be overly pedantic or combative here but making a distinction between client-side and server-side code seems arbitrary. I understand it in terms of managing privilege - you can't control what someone does on a remote server, and that code isn't running on your machine, but it seems like the meaningful distinction here isn't between documents and applications but between local and remote applications.
- Retric 8y agoThe entire point is managing privileges. Just because I type in yourdomain.com does not mean I want you to be able to start playing death metal from my speakers. What about typing yourdomain.com means I want you to break my back button? Show a popup rather than close the browser? Churn CPU cycles crypto mining or do just about anything beyond hand me a document? Display a flashing GIF? The current model is basically handing complete control over my machine to a third party that may be compromised by anyone any time I click a random link. The single greatest web innovation in the last 30 years was readability mode.
- oblio 8y ago> The single greatest web innovation in the last 30 years was readability mode. For you. From what I see, everyone else seems to be enjoying the dancing and singing monkeys online.
- contras1970 8y agothe monkeys[1] are enjoying themselves, dancing and singing, at the expense of everybody else. [1] web application pushers edit: hn "syntax"
- oblio 8y agoBy monkeys I meant literal monkeys, animations and videos and games and generally “frivolous” features.
- workinthehead 8y agoThe problem is that the dancing and singing monkeys enabled advertising to be increasingly lucrative to the point where the monkeys are running the show.
- krapp 8y ago>Just because I type in yourdomain.com does not mean I want you to be able to start playing death metal from my speakers. Given the way HTTP works, I think it kind of does. It means you want the server at yourdomain.com to send you whatever content that URL points to, if anything. Which, granted, given the complexity of the web now, does seem fraught with danger, but what alternative would there be? Profiling each site for embedded content, size and complexity and whitelisting the elements before rendering? Browsers already let you block scripts, disable images and autoplay, overwrite or disable stylesheets and mute tabs, that would seem to be sufficient. >The current model is basically handing complete control over my machine to a third party that may be compromised by anyone any time I click a random link. That's a good point, but separating "applications" from "documents" wouldn't solve that problem, since that's presumably the model the applications would still be using. Sure, static pages that aren't running client side code would be safe, but those pages already are safe. Anything that could be done to make a separate application space run safely could be done to make them run safely on the existing web, couldn't it?