4 ms·
I think this is a really braindead argument. Of course users are going to use javascript more, the more the internet demands it, the more people will be willing
by dijit 8y ago
I think this is a really braindead argument. Of course users are going to use javascript more, the more the internet demands it, the more people will be willing to allow it.
When I first started using noscript there were few exceptional sites which didn’t work and I didn’t bother with them after, if that was the majority of sites, I would probably just disable noscript.
The idea that I _have_ to let your site run code on my machine is only laughable when it’s an exception, the problem is the industry. And google is telling the industry that it’s ok.
edit: yes, I understand; I'm over the hill and you all absolutely love shoving javascript down peoples throats, I get it. But please take a moment to consider... not? maybe you have a financial incentive to avoid thinking about the ramifications you inflict on others, maybe you're paid to be a JS dev. But really, if you're making the web worse, I will not cry for being downvoted, just know that I hate you. :)
- arcticfox 8y ago> Of course users are going to use javascript more, the more the internet demands it, the more people will be willing to allow it. I think you have this backwards; the vast majority of users like the benefits of js-enabled sites, so they get built. That ship has sailed long ago.
- dijit 8y agoEven so, making the assertion that: "javascript adoption in the browser will increase in future, therefore we will enforce javascript" is like saying: "more people will have passports in future, therefore we require passports to get a bus pass". By doing that; you make it true.
- horsawlarway 8y agoIt's already true. You can quibble over who's fault it was, but it really doesn't matter at this point. The web serves code that users run. That's because the web is the best distribution medium for code we've ever seen. I bet you've also installed client side applications that came from the web, on a vendor installed OS that came from the web, and drivers for your machine that came from the web.
- dijit 8y agoYou're equating my signed/sealed/delivered package management to javascript?? ?? ?????? Really? You honestly don't see a difference? I have a chain of trust with my OS manufacturer (apple) and a defecto trust with a centralised entity for most of my applications (IE; my company for things that we build, or the home-brew project for most other packages) I should not have that trust with any idiot who manages to get a signed SSL certificate; IE: the whole internet.
- horsawlarway 8y agoYou mean like the signed/sealed/delivered csp policies that browsers have supported for years? https://developers.google.com/web/fundamentals/security/csp/ https://developers.google.com/web/fundamentals/security/csp/ To quote the signature section: '<hash-algorithm>-<base64-value>' A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the <script> or <style> tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See unsafe inline script for an example. In CSP 2.0 this applied only to inline scripts. CSP 3.0 allows it in the case of script-src for external scripts.
- horsawlarway 8y agoSorry, but you're out of touch. Almost everyone wants the features that JS enables. Literally: Almost everyone. I understand you don't, and I absolutely respect that decision, but it means that you're not worth developing for. Full stop. It's not a matter of mal-intent, it's a matter of financial logistics. You bought that machine to run code. If you don't want to run code that sites serve you on the internet, don't visit them. That said, I'd be willing to wager a fair bit that literally every line of code you've run on your machine (probably ever if it's been bought in the last few years) outside of the vendor installed OS and drivers came from the internet.
- dijit 8y agoYou're making an assumption about me, I actually don't use noscript these days (I haven't for at least 6 years at this point) however I will fight for the right of my brethren who do not have machines with six CPU cores and 64G of ram, or those who have had their scrollbars hijacked, or their text to speech software go insane, or their web experience which used to be controlled by them insidiously invaded by people who want to use their webbrowser as a software distribution platform and virtual machine. Javascript being enforced allows for a sub-par slew of web development which does not cater for performance(minor) or accessibility(major). I dislike the trend of _forcing_ people to do something that doesn't benefit them. Even if I'm not personally affected.
- horsawlarway 8y agoI'm sorry, but who is _forcing_ you to do anything?
- dijit 8y agoWow, I'm sorry... are you trolling? This thread is about google forcing everyone to use javascript to use their services. That's literally the topic of conversation. EDIT: I'm not allowed to post because of downvotes, to reply to the child: I am not forced to use google, no, but I don't think I'd get very far on todays internet without javascript. Google are enabling that: Now people will say "Oh, well google are able to force javascript so why would we support more than google does? we don't have their resources!" And thus, the next generation of websites have absolutely no hope of ever having a plaintext version.
- sctb 8y agoWe detached this subthread from https://news.ycombinator.com/item?id=18353373 https://news.ycombinator.com/item?id=18353373.