5 ms·

Warp: Improved JavaScript performance in Firefox 83

brundolf 6y ago
I wonder if there's room to have a fork of Node that uses SpiderMonkey as a "back-end" in place of V8? It would be cool to introduce competition in that space. I don't know how tightly-coupled Node currently is to V8 (compared to other adherents of the JS standard).
- zingplex 6y ago
  Mozilla worked on this a while ago with SpiderNode but it is no longer maintained. It was actually based on Microsoft's work to do the same thing with ChakraCore.
- foolmeonce 6y ago
  It seemed interesting to me that deno combines V8 and rust. It might be interesting (and not yet as complicated as with node) to make a spidermonkey version of deno.
- ldng 6y ago
  Wouldn't forking GJS [https://gitlab.gnome.org/GNOME/gjs https://gitlab.gnome.org/GNOME/gjs] and adding Node compatibility API faster/simpler ?
ksec 6y ago
"With Warp we have replaced the frontend (the MIR building phase) of the IonMonkey JIT. The next step is removing the old code and architecture. This will likely happen in Firefox 85. We expect additional performance and memory usage improvements from that." Interesting I wonder how does it compared to Safari on Speedometer. Edit: Firefox 83 - 71 Safari 14 - 77
aitchnyu 6y ago
What does the innovation pipeline at Mozilla look like nowadays? Will it dry up drastically soon?
- dblohm7 6y ago
  I don’t think so. Sure, the Emerging Technologies division was shut down, but most of the Gecko team was left intact. (I am a Mozilla employee.)
justforyou 6y ago
Would be great if stabilizing firefox on mobile happened before this nonsense.
- jdlshore 6y ago
  Not only are you being unacceptably rude, you’re making the unfounded assumption that these developers have anything to do with the mobile apps.
  - justforyou 6y ago
    I'm not making any assumptions about developers. I'm making a comment about Mozilla as an organization, and Firefox as a product. Rudeness is in the eye if the beholder, but seems like you're taking this personally, and with a thin skin.

I wonder if there's room to have a fork of Node that uses SpiderMonkey as a "back-end" in place of V8? It would be cool to introduce competition in that space. I don't know how tightly-coupled Node currently is to V8 (compared to other adherents of the JS standard).

zingplex 6y ago
Mozilla worked on this a while ago with SpiderNode but it is no longer maintained. It was actually based on Microsoft's work to do the same thing with ChakraCore.
foolmeonce 6y ago
It seemed interesting to me that deno combines V8 and rust. It might be interesting (and not yet as complicated as with node) to make a spidermonkey version of deno.
ldng 6y ago
Wouldn't forking GJS [https://gitlab.gnome.org/GNOME/gjs https://gitlab.gnome.org/GNOME/gjs] and adding Node compatibility API faster/simpler ?

ksec 6y ago

"With Warp we have replaced the frontend (the MIR building phase) of the IonMonkey JIT. The next step is removing the old code and architecture. This will likely happen in Firefox 85. We expect additional performance and memory usage improvements from that." Interesting I wonder how does it compared to Safari on Speedometer. Edit: Firefox 83 - 71 Safari 14 - 77

aitchnyu 6y ago

What does the innovation pipeline at Mozilla look like nowadays? Will it dry up drastically soon?

dblohm7 6y ago
I don’t think so. Sure, the Emerging Technologies division was shut down, but most of the Gecko team was left intact. (I am a Mozilla employee.)

justforyou 6y ago

Would be great if stabilizing firefox on mobile happened before this nonsense.

jdlshore 6y ago
Not only are you being unacceptably rude, you’re making the unfounded assumption that these developers have anything to do with the mobile apps.
- justforyou 6y ago
  I'm not making any assumptions about developers. I'm making a comment about Mozilla as an organization, and Firefox as a product. Rudeness is in the eye if the beholder, but seems like you're taking this personally, and with a thin skin.