4 ms·
Throwing web-interactivity (via Javascript) away today is like throwing your computer away. Computers help you be more productive, but it also helps the people
by netsharc 10y ago
Throwing web-interactivity (via Javascript) away today is like throwing your computer away. Computers help you be more productive, but it also helps the people who want to profile you. What's the alternative?
If it's not Javascript, any functionality that offers access to the hardware (via however many layers) to "apps" from the "cloud" can be exploited this way. Maybe we should disallow hardware access, how will YouTube play videos? Should we all install youtubeplayer.exe ?
- mikegerwitz 10y agoJS is different---your browser automatically downloads and executes untrusted, unsigned, arbitrary, ephemeral code that can do whatever it feels like. Almost worse: is does so silently without the user's knowledge, and has the illusion of remote execution, misleading the user into thinking no software is actually running on their own computer.
- Silhouette 10y agoJS is different---your browser automatically downloads and executes untrusted, unsigned, arbitrary, ephemeral code that can do whatever it feels like. It really doesn't. There are severe limits on what JS downloaded from some random site can do via a browser on your local device. A few tricks to detect some environment-based signals and invade privacy might be undesirable, but that intrusion is nothing compared to the kind of stunts native software has pulled over the years, and the major desktop and mobile operating systems are pathetically ineffective at sandboxing that software compared to what browsers do with JS, even taking into account the unwanted side effects of recently expanded capabilities that we're discussing here.
- omginternets 10y ago>It really doesn't. There are severe limits on what JS downloaded from some random site can do via a browser on your local device. That's missing the point. With respect to tracking a user, most of those restrictions don't matter. Your browser does download/execute untrusted, unsigned, arbitrary, ephemeral code that can do any kind of tracking it wants.
- Silhouette 10y agoAnd compared to the kinds of technologies used for copy protection and telemetry in native applications, what JS can do within a browser is still very limited. Yes, the browser executes JS code from untrusted sources, but only if you visit a page that loads scripts from those sources, and always (barring security bugs) within a sandbox that limits their capabilities. I fail to see how this can possibly be any worse than installing software in other ways such as running a native executable you downloaded from somewhere, or following a "curl | sh" installation process as advocated by plenty of popular OSS tools, or allowing native software that you already installed to install arbitrary automatic updates that it fetches from remote sources. The argument netsharc made was essentially that turning off JS would disable a lot of useful functionality for a lot of people, and that providing that functionality would still involve similar risks if it were done some other way. The reply from mikegerwitz argued that JS is different, but I still don't see how. The relevant comparison isn't against just turning JS off, it's against turning JS off and implementing the same functionality some other way, and compared to the sandboxed environment of JS, the most likely alternatives with today's technology would be even worse in terms of security and privacy.
- mikegerwitz 10y ago> compared to the kinds of technologies used for copy protection and telemetry in native applications Compared to the damage a logging truck can do to my car, a snow plow is very limited. I still don't want to be hit by a snow plow. The threats to privacy posed by JS are severe and constantly evolving. Being able to profile based on hardware is effectively breaking the sandbox. > (barring security bugs) Which are far from uncommon. But you can't predicate a security discussion with the phrase "barring security bugs". > I fail to see how this can possibly be any worse than installing software in other ways such as running a native executable you downloaded from somewhere, or following a "curl | sh" installation process as advocated by plenty of popular OSS tools, or allowing native software that you already installed to install arbitrary automatic updates that it fetches from remote sources. Each of these requires explicit user authorization at some point (barring malicious operating systems). In the case of automatic updates, the initial install required user consent. That isn't the case on the Web when you click on some random link I send you and automatically download and execute a program.
- na85 10y ago>Computers help you be more productive, but it also helps the people who want to profile you I disagree with the idea that computers == JavaScript, and furthermore with the idea that JavaScript helps me be more productive. Excel makes me productive. React.js as a service does not.
- wtbob 10y ago> What's the alternative? The alternative is cleanly separating web browsing (a passive activity requiring no code execution) and using distributed apps. I'm not at all against the idea of a common, cross-platform execution environment; I'm 100% against the idea of executing cross-platform code when all I want to do is read an article.
- pdkl95 10y ago> Throwing web-interactivity (via Javascript) away Javascript is not the only way to provide interactivity. CSS, for example, provides some form validation methods in a declarative style. Sometimes you can do it server-side. Many types of interactivity were possible before the current JS mess. If there is a type of common interactivity that is not supported without JS, we can always add it as a new browser features, just like we did with everything else in the browser. > any functionality that offers access to the hardware (via however many layers) to "apps" from the "cloud" can be exploited this way That's why you don't provide an runtime environment for "apps". Rendering data (a document, an image, video, etc.) does not need arbitrary software. It only needs a way to send a media file to the appropriate renderer. <img> and <video> tags should work fine. > how will YouTube play videos? Why is this even a question? They can serve an mp4 (or whatever) at some URL, and reference it in the <video> tag. Video playback doesn't require running arbitrary software, because we already have local video players.
- deleted 10y ago[deleted]