@mangeurdenuage Executing code in a web browser *without explicit permission from the user* is a mistake. As we've seen with mobile, normalizing downloading native apps for everything is also a mistake. In practice, it helps the biggest platforms starve the web of users by keeping them away from the web browser.
@strypey @email@example.com The (weak) line I like encouraging people to draw is that The Web is for publishing information, native apps are for supporting interactions.
Sigh, it was recently suggested to me to install an app for recipes. I didn't say that I dissaprove of distributing this information as an app.
@mangeurdenuage I understand that perspective, but I disagree. As I pointed out, users will only ever use a handful of native apps. Deploying apps on the web allows devs to try new things without having to convince users to install a new app just to try it out. Would the fediverse be as big as it is if users had to install a native app just to try it?
@strypey It is optional...
@seven in the sense that you can avoid it by not using the web, or by turning it off and having the vast majority of the web not work. Click the hashtag for all the examples I've collected. For it to be truly optional, web devs need to use it only for things that plain HTML/CSS can't do, and browsers need to make tools like NoScript standard, so users can opt-in to JS when it serves them.
I mean yeah, JS syntax and function is shit, but...
It is up to the interpreter to execute it (fing node not withstanding here, though still just a glorified translator for a language no one serious cares about, tell me I'm wrong I dare you, which is an ABOMINATION, yes I said it, it's literally what jesus died to prevent. O_o)
You still should blame the thing letting it run, even though we all know, it shouldn't run...
> JS syntax and function is shit, but...
I can't code JS so I'm not really in a position to judge those things. My issue is with client-side scripting in general, being a) run without permission by default, with no tools for selective op-in (browser makers' fault), and b) lazy over-use, eg pages that won't even load text and images without JS turned,on (web designers' fault). Like @dokuja says, it takes two to tango.
@seven not sure what point you're making here. Care to elaborate?