"Unless proven otherwise, ability to generate and run machine code, especially in same execution/privilege context as generator, is blatant memory unsafety comparable to the memory unsafety of C."
-
-
Being fast is an arms race and in arms races nobody but the arms dealers win. It's like adding more highway lanes. You don't need faster JS you need to nuke the ads and awful js frameworks that are layer upon layer of useless (& often Shlemiel) bloat.
-
You don’t have to convince me of that. :) I’m generally of the opinion that JS will remain fast enough even if we have to regress performance a bit for security.
- 5 more replies
New conversation -
-
-
Unfortunately, compilation speed is by far the most important thing when it comes to JS performance in the wild. Once you get past the interpreter stage, this starts to conflict with correctness.
-
My fear is that this is going to come down to a “JS benchmarks vs. security” tradeoff. Since the former is easier to measure and therefore makes for better press/etc, it has the advantage. :(
- 3 more replies
New conversation -
-
-
i’m particularly interested in wasm for this IR, idk if that’s silly
-
It’s not silly, but the GC story is the hard part.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.