Once again, there have been discussions on the feasibility of adding
static analysis to our JS code, possibly as part of MozReview. As usual,
one of the main problems is that we are not using standard JS, so we
pretty much cannot use standard tools.
One of the main differences between mozilla-cent
If the conversion is tractable and we end up with module ergonomics that
frontend developers are happy with, I'm certainly in favor of this from the
platform side. It would get us the 15-20MB of memory savings that bug
1186409 was pursuing without the smoke and mirrors.
bholley
On Sat, Sep 24, 20
If we're going to do a mass conversion, shouldn't we try to move to ES
modules? There's some support for them in SpiderMonkey for chrome code, and
it would be great to move towards a future standard.
-Bill
On Sat, Sep 24, 2016 at 4:16 PM, Bobby Holley wrote:
> If the conversion is tractable an
What's the current status of the implementation of ES6 modules? Also, to
use them in chrome code, can we support synchronous loading? Or would we
need to make the rewrite more complicated to support asynchronous loading?
On 25/09/16 02:35, Bill McCloskey wrote:
> If we're going to do a mass conver
4 matches
Mail list logo
