6 ms·

I vowed to switch to the first browser that implemented arrow-function syntax. Sooo, been using Firefox as my primary browser for the last 6 months, and am lovi

I vowed to switch to the first browser that implemented arrow-function syntax. Sooo, been using Firefox as my primary browser for the last 6 months, and am loving using ES6 features in my personal projects (without needing stinky transpilers messin' up my workflow)! Next up, hanging out for Module support. C'mon modules!

apaprocki 13y ago
FYI we (Bloomberg) also want arrow syntax and are sponsoring Adrian Perez at Igalia to work on adding it to v8. Work is coming along... https://codereview.chromium.org/160073006/ https://codereview.chromium.org/160073006/ (If any other companies are wondering how to help out, I can't recommend Igalia highly enough!)
- cpeterso 13y ago
  Bloomberg also sponsored Andy Wingo's work on ES6 generators and array comprehensions for Chrome [1] and Firefox [2]. What is Bloomberg's motivation for sponsoring browser feature development? How does Bloomberg prioritize what they would like to fund? It's exciting to see companies, not just contributing changes back to open-source projects they use, but actually funding new development. Thank you! :) [1] http://wingolog.org/archives/2013/05/08/generators-in-v8 http://wingolog.org/archives/2013/05/08/generators-in-v8 [2] http://wingolog.org/archives/2013/10/07/es6-generators-and-iteration-in-spidermonkey http://wingolog.org/archives/2013/10/07/es6-generators-and-i...
  - apaprocki 13y ago
    > What is Bloomberg's motivation for sponsoring browser feature development? Our motivation is that we have a massive custom server-side JS deployment that powers the platform for the Bloomberg Professional Service (a.k.a. "Terminal"). We use both spidermonkey and v8 in custom environments, so getting ES6 (and beyond) language features in the engines as fast as possible helps the 2,000+ developers building the platform every day. So what benefits us, benefits the web since we use engines that cut across multiple browsers. We also have a bunch of web properties, so obviously those teams are thrilled that we help move the needle a bit as well. > How does Bloomberg prioritize what they would like to fund? Prioritizing the features that Igalia works on falls out of discussions between my team and Igalia to see where their development effort can be most effective to get what helps our developers the most. We really, really wanted generators across the board so that we could use generators and promises to help how we address async control flow. We have internal JS frameworks that use certain features that are not too common in the web and sometimes are not as optimized/JITed as earlier APIs. It's a two-way conversation with Igalia to find out how we can make the most impact. We do some of our own contributions to these projects as well, but the model we have with Igalia works amazingly well because they aren't distracted by the other development that my team is currently involved in.
    - deleted 13y ago
      [deleted]
    - cpeterso 13y ago
      Thanks for sharing. That's very interesting! > We use both spidermonkey and v8 in custom environments Are you using SpiderMonkey on the server-side, too? I work for Mozilla and some community members are interested in rebooting "SpiderNode", Mozilla's 2011 proof-of-concept to plug SpiderMonkey VM into the Node server. SpiderMonkey supports more ES6 features than V8 (or node --harmony), so SpiderNode developers could use more ES6 features on the server-side without worrying about browser compatibility.
      - apaprocki 13y ago
        Yes, most of the production JS is running on spidermonkey. The original binding is hand built using JSAPI, but the newer code we have abstracts the JS engine away behind an interface, making a single way to easily bind C++ classes to JS, allowing us to swap in spidermonkey or v8 without the bound code being aware. This is kind of what you want to do, only you want to emulate the v8 API to avoid having to retool the Node guts. Two different approaches but they achieve the same result. IBM guys working on the POWER node port asked if we can open-source the abstraction and adapters -- it's on my todo list to look into, but can't promise anything yet.
        cpeterso 13y ago
        Mozilla has a prototype of what you suggested: "v8monkey", an API facade that emulates the v8 API on top of SpiderMonkey's JSAPI. A contributor named Sarat recently unbitrotted v8monkey and ported it to SpiderMonkey's current JSAPI (which was rewritten to support Generational GC). He posted his patches just three hours ago. :) https://bugzilla.mozilla.org/show_bug.cgi?id=1005411 https://bugzilla.mozilla.org/show_bug.cgi?id=1005411

apaprocki 13y ago

FYI we (Bloomberg) also want arrow syntax and are sponsoring Adrian Perez at Igalia to work on adding it to v8. Work is coming along... https://codereview.chromium.org/160073006/ https://codereview.chromium.org/160073006/ (If any other companies are wondering how to help out, I can't recommend Igalia highly enough!)

cpeterso 13y ago
Bloomberg also sponsored Andy Wingo's work on ES6 generators and array comprehensions for Chrome [1] and Firefox [2]. What is Bloomberg's motivation for sponsoring browser feature development? How does Bloomberg prioritize what they would like to fund? It's exciting to see companies, not just contributing changes back to open-source projects they use, but actually funding new development. Thank you! :) [1] http://wingolog.org/archives/2013/05/08/generators-in-v8 http://wingolog.org/archives/2013/05/08/generators-in-v8 [2] http://wingolog.org/archives/2013/10/07/es6-generators-and-iteration-in-spidermonkey http://wingolog.org/archives/2013/10/07/es6-generators-and-i...
- apaprocki 13y ago
  > What is Bloomberg's motivation for sponsoring browser feature development? Our motivation is that we have a massive custom server-side JS deployment that powers the platform for the Bloomberg Professional Service (a.k.a. "Terminal"). We use both spidermonkey and v8 in custom environments, so getting ES6 (and beyond) language features in the engines as fast as possible helps the 2,000+ developers building the platform every day. So what benefits us, benefits the web since we use engines that cut across multiple browsers. We also have a bunch of web properties, so obviously those teams are thrilled that we help move the needle a bit as well. > How does Bloomberg prioritize what they would like to fund? Prioritizing the features that Igalia works on falls out of discussions between my team and Igalia to see where their development effort can be most effective to get what helps our developers the most. We really, really wanted generators across the board so that we could use generators and promises to help how we address async control flow. We have internal JS frameworks that use certain features that are not too common in the web and sometimes are not as optimized/JITed as earlier APIs. It's a two-way conversation with Igalia to find out how we can make the most impact. We do some of our own contributions to these projects as well, but the model we have with Igalia works amazingly well because they aren't distracted by the other development that my team is currently involved in.
  - deleted 13y ago
    [deleted]
  - cpeterso 13y ago
    Thanks for sharing. That's very interesting! > We use both spidermonkey and v8 in custom environments Are you using SpiderMonkey on the server-side, too? I work for Mozilla and some community members are interested in rebooting "SpiderNode", Mozilla's 2011 proof-of-concept to plug SpiderMonkey VM into the Node server. SpiderMonkey supports more ES6 features than V8 (or node --harmony), so SpiderNode developers could use more ES6 features on the server-side without worrying about browser compatibility.
    - apaprocki 13y ago
      Yes, most of the production JS is running on spidermonkey. The original binding is hand built using JSAPI, but the newer code we have abstracts the JS engine away behind an interface, making a single way to easily bind C++ classes to JS, allowing us to swap in spidermonkey or v8 without the bound code being aware. This is kind of what you want to do, only you want to emulate the v8 API to avoid having to retool the Node guts. Two different approaches but they achieve the same result. IBM guys working on the POWER node port asked if we can open-source the abstraction and adapters -- it's on my todo list to look into, but can't promise anything yet.
      - cpeterso 13y ago
        Mozilla has a prototype of what you suggested: "v8monkey", an API facade that emulates the v8 API on top of SpiderMonkey's JSAPI. A contributor named Sarat recently unbitrotted v8monkey and ported it to SpiderMonkey's current JSAPI (which was rewritten to support Generational GC). He posted his patches just three hours ago. :) https://bugzilla.mozilla.org/show_bug.cgi?id=1005411 https://bugzilla.mozilla.org/show_bug.cgi?id=1005411