Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

I guess this site should be sent to anybody saying javascript should be blocked in web browsers... In the end whether a technology is used to track and exploit or educate and delight is entirely up to us.


JavaScript being enabled should be the exception, not the rule.


I try to visit only quality websites, like the article's. Enabling JS on every website I visit seems backward.


Aren't most things neatly placed in <canvas> tags? Not to mention that it's basically all some form of web GL, which could avoid JS pretty easily is it wanted to these days.

What we want blocked isn't all of javascript, it's some of the browser APIs.


You definitely can’t use canvas (or any DOM API) without JS. The idea of using WebAssembly for WebGL (or canvas via whatever JS bridge) almost certainly won’t satisfy a large portion of the no-JS crowd, whose opposition to JS is opposition to the browser as an application platform generally.


How would WebGL work without JavaScript? Also have a hard time seeing how the input could be handled without JS.


https://webassembly.org/

Again, it's all about the interface the browser provides. They could decide to remove this API for example: https://developer.mozilla.org/en-US/docs/Web/API/History


> https://webassembly.org/

How is that any better than 'javascript'?


The "no js" crowd isn't about language wars rather client side programmability. As such WASM is only a superset for this conversation, not an alternative.


No, you're talking about something completely different, so saying "what we want" and "it's all about" is simply incorrect.


Haven't even started exploring everything (hope to find the time to do so), but in random dive I see lots of handcrafted js

https://ciechanow.ski/js/gears.js




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: