WASM’s biggest holdback is that it cannot directly access the DOM. Until then, JS will still have a prominent place in building anything rendered in a browser.
jvisick
joined 1 year ago
No worries, the Democrats will do what the party does best with a majority - pretty much nothing.
Enough to say “see? We’re better than the other guys”, but not enough to even nudge the status quo.
Spotify pays artists based on how many listens their songs get, so if you can get a bunch of bots to stream your music over and over you can get a legitimate income stream.
In this case, they’re using their illegal income to pay people to use a botnet to stream their songs - which then means they have a nice legal income instead.
But what if it was an African Swallow?
But have you heard of Rust? Rust has zero-cost abstractions! Zero cost!
Honestly, “it’s better than JavaScript” is a pretty low bar.
I don’t like PHP because I think the syntax is ugly and I’ve only used it on systems that are old and a pain to maintain, but I’ll also very freely admit that I have absolutely not written enough PHP to have an informed opinion on it as a language.
At that point, just make a typescript engine so people don’t have to build their TS projects anymore
I agree! I don’t think 3?”stuff”:”empty” should work at all because I think it’s an insane way to type a ternary :) I’m also very open to admitting that it’s just my own strongly worded opinion.
I think that in most cases, syntactically significant whitespace is a horrible idea - the one exception being that you should have space between operators/identifiers/etc. I don’t care how much, and 4 spaces should have no more special meaning than 1, but I do think that using a space to indicate “this thing is a different thing than the thing before it” is important.
I can’t imagine anyone but a total novice disagreeing with this.
I can understand finding pointers hard at first, but I can absolutely not understand trying to argue that they aren’t useful.
Can you clarify what you meant about types, then? Because I’m not sure I really understand your point there.
It’s not a question of performance - it’s just the fact that you need to use JS to modify the DOM in WASM. Until there is access to the DOM from WASM, there simply will be a place for JS in nearly every web app and it’s not because it’s fast, it’s because there are still certain things just need to be done using JS.
My point is really nothing to do with performance and I agree with the video you’ve linked: WASM is fast enough today. Whenever you can truly stop using JavaScript, I’ll be the first in line. You can already use WASM and eliminate huge portions of JS - but for anything beyond a very simple UI, you always end up with something that needs to be called in JS.