6 ms·
Let's take something very simple, like a guitar tuner. https://guitar-tuner.appspot.com/ https://guitar-tuner.appspot.com/ How are you going to implement that i
by sp332 9y ago
Let's take something very simple, like a guitar tuner. https://guitar-tuner.appspot.com/ https://guitar-tuner.appspot.com/ How are you going to implement that in plain HTML?
- deleted 9y ago[deleted]
- pmoriarty 9y agoDon't use web technologies to implement it. Make a native app. Javascript is a cancer that has lead to a slow, bloatware-, spyware-, and malware-infested web. Getting rid of it should be a priority.
- tenaciousDaniel 9y agoSerious question: in replace of what? A web that's just static content?
- pmoriarty 9y agoWhy not? What exactly is the big deal with having just static content? I don't have JS enabled when I read HN. I just hit reload to load and read new comments. What exactly is the problem with doing that? When I read some article on some news site or web forum, I don't need JS to just read a bunch of text or look at an image. All of that can be and often is static. JS is totally superflouous here. The only legitimate uses of JS I can think of are for things like games, or data that you really need to be updated in real-time like stock market tickers. But those are a relatively minor subset of the web and can be made in to standalone apps anyway. I'd much rather have a standalone app than expose myself to all the malware, spyware, and tracking that comes with a JS web ecosystem.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- krapp 9y ago>Why not? >What exactly is the big deal with having just static content? I don't read romance novels, so publishers shouldn't be allowed to print them. The problem is that your personal opinion on the legitimate utility of javascript doesn't have any value beyond your own browser, and the entire rest of the world has decided that a purely static web is not what it wants.
- tannhaeuser 9y ago> ... entire rest of the world ... Speak for yourself! I certainly agree with the parent that the Web is for content. And I believe many here around do as well. You do realize you're commenting here on a site which is as non-PWA/SPA as it gets, don't you?
- krapp 9y agoContent is still content when javascript is involved. Twitter serves content, so does facebook, so do wordpress blogs and medium and likely whatever other sites you think of when you think about how terrible javascript is, because "content" and "javascript" are not mutually opposed. I like Hacker News (obviously, since I spend far too much time here,) but I also like that I can run software in my browser and stream video and audio and play games. FFS, I'm running DOOM in a DosBox emulator in another browser tab as I type this. How is that not qualitatively better in terms of the breadth of content that the web allows than having it be limited to basic text styling and embedded images?
- tannhaeuser 9y agoAudio/video yes, but what's the point of running DOS emulators in a browser? What a browser can and cannot do should be very carefully balanced, or you end up with a tangled mess of Chrome-only content and security/privacy catastrophes.
- krapp 9y ago>Audio/video yes, but what's the point of running DOS emulators in a browser? The point is that if I want to play DOS games I only need a URL and a modern browser, just the same as with text, images and other media. That "software" becomes just another content type the web can provide, in a way that's transparent and easy for the end user. If nothing else, the browser can act as a sandbox for software that operating systems otherwise don't seem to provide. A developer can't sneak "rm -rf /*" into their javascript and have it work the way they could natively. > What a browser can and cannot do should be very carefully balanced, or you end up with a tangled mess of Chrome-only content and security/privacy catastrophes. I would argue things have gotten more stable, not less, over time. Flash is more or less dead, as are web applets, and a lot of security issues in javascript WRT overriding object primitives, high frequency timing, cross origin requests, etc, have been dealt with. It's not entirely the wild west anymore.
- tenaciousDaniel 9y agoI maintain a client dashboard for large ad vendors who need to visualize their data across multiple time spans. It's too much to sift through on mobile. Are you saying that in this brave new world you're envisioning, I'd have to build them a desktop app?
- gaius 9y agoNo, in the brave new world there would be no “large ad vendors” so your problem would not even exist
- tenaciousDaniel 9y agoThe only way for that to be an effective response is to argue that the only people who need large-scale data visualization on the fly are ad vendors.
- sp332 9y agoSo what's the advantage? It looks like all downside to me. From an app developer standpoint, I'd have to deal with multiple platforms and distributors. From a user standpoint, I'd have to hope the developer made the app available for my platform, and go through some install process before I got to use it. This way, it loads (with a cold cache) in half a second.
- pmoriarty 9y agoThe advantage for the user is that they don't have to open up their browser, computer, or mobile device to being exploited, spied upon, or advertised-to by an ocean of javascript garbage on the web. Their web browsing experience will be tremendously improved and streamlined. If they want a particular app, they can click to download and run it explicitly. It's not a big deal. From the developer and business standpoint, it might be a disadvantage not to have something like javascript available to use. It's more inconvenient, and now they can't spy on, advertise to, or track the user as easily. But I'm for a user-centric web, not a business-centric or developer-centric web.
- sp332 9y agoIf you click the link I posted above, you will get a permissions dialog that asks to access your microphone. You can say no upfront, or revoke permission at any time. It's not open to spying. Edit: to be specific, it's a lot easier to allow access temporarily in a browser than it is using the Android permissions system. Not sure about Apple but I'd bet it's about the same as Android.
- pmoriarty 9y agoJust because you've given permission to an app to access, say, your microphone, doesn't mean that it's not spying on you. That guitar-tuning app that was mentioned earlier might well be spying on you using the microphone it got access to. The guitar-tuning app is a special case that actually has a legitimate need to use a microphone, but I've seen countless apps that need all sorts of permissions that they don't legitimately need. Like calculator apps that need permission to access my microphone or contacts. The sad thing is that most users will just click through a popup asking for permissions, just like they do the "Run as administrator" popups on Windows. Such things are just not very effective safeguards. Even with limited permissions, allowing JS apps to run on my system opens me up to all sorts of JS exploits, tracking, and advertising that just aren't possible or much more difficult with static HTML (which has a much smaller attack surface than JS anyway).
- f2n 9y agoNative apps have led to slow, bloatware-, spyware-, and malware-infested mobile devices. The browser is a much better sandbox, giving much less permissions to the untrusted code.
- deleted 9y ago[deleted]
- eh78ssxv2f 9y ago> Don't use web technologies to implement it. Make a native app. > Javascript is a cancer that has lead to a slow, bloatware-, spyware-, and malware-infested web. Getting rid of it should be a priority. That may or may not be correct from developer's point of view. I am not sure and I am not going to argue that. However, how about user's point of view. A lot of users (including me!) prefer not to install native apps but use Web apps especially when achieving one-time tasks. Do you have any thoughts/data on what users prefer?
- tenaciousDaniel 9y agoThis is what I don't understand about the whole "create a website that can survive without JS" argument.
- mimsee 9y agoExactly. HTML was designed for sharing static documents. Now we want/need to do extensive client-side apps that can completely replace a desktop app.
- krapp 9y agoHTML at one point didn't even allow for image embedding, or tables, or external CSS. HTML evolves over time, and the <script> tag is no less a part of that evolution than any other tag.