HolyJit: A New Hope
81–90 of 219 posts
Re: HolyJit: A New Hope
#82Re: HolyJit: A New Hope
#83Re: HolyJit: A New Hope
#84I admire how mozilla is so passionate about what they develop but still, in 2017, firefox needs restart every couple of hours for performance reasons. I kinda of feel like they have the proof of concept working but its never good enough for the wider audience.
Re: HolyJit: A New Hope
#85I admire how mozilla is so passionate about what they develop but still, in 2017, firefox needs restart every couple of hours for performance reasons. I kinda of feel like they have the proof of concept working but its never good enough for the wider audience.
You might want to submit a bug with your specific hardware to see if anyone can identify the cause, because that's not normal.
Re: HolyJit: A New Hope
#86Can we just drop the JS VM and embed some nicer VM (JVM, DartVM) instead?
I agree this would be better, but backward compatibility constraint makes it impossible. WebAssembly is an attempt to add a nicer VM in addition to JS VM.
> With the advent of WebAssembly appearing in browsers, the virtual machine that we talked about earlier will now load and run two types of code — JavaScript AND WebAssembly.
Re: HolyJit: A New Hope
#87No offense, but the blog post is seriously missing a better (or any?) explanation of what's the new JIT all about. At first I even thought my browser loaded only half the page...
It does link to https://github.com/nbp/holyjit which explains pretty much everything there is to explain so far...
Re: HolyJit: A New Hope
#88Earlier quoted context omitted.
He/she is right though, just wait when WebAssembly gets more mature. I bet all those plugins will be back.
WebAssembly has no good story for the DOM.
And just because it isn't there today, it doesn't mean it won't be there tomorrow.