I've been involved in the re-drafting of this charter as part of the
regular wasm WG meetings and I think we should support it.
Cheers,
Luke
On Tue, Jan 21, 2020 at 11:10 AM L. David Baron wrote:
> The W3C is proposing a revised charter for:
>
> WebAssembly Working Group
> https://www.w3.or
Since dynamic import is a core part of the JS language, with dedicated
syntax (`import` is not a plain function, but a fixed syntactic form), it
would seem to fall under the new, underlined JS exception in the first
section of
https://blog.mozilla.org/security/2018/01/15/secure-contexts-everywhere.
(Sorry, I polled #jsapi about this issue back when you first posted and
then forgot to reply with the response.)
It doesn't seem like any SM devs use --enable-shared-js for their own
development but we do know that various embedders (e.g. GNOME) use the JS
shared library and so we'd like to keep t
fbertsch helpfully wrote a query that breaks down physical cores into the %
with and without HT enabled:
https://sql.telemetry.mozilla.org/queries/47219/source
>From this we can see that, e.g., 6.7% of systems that report "2 logical
cores" (and ~2% of all systems) actually only have 1 physical co
For additional rationale, you might be interested to read:
https://blog.mozilla.org/javascript/2015/02/26/the-path-to-parallel-javascript/
On Thu, Jan 14, 2016 at 8:11 AM, Thomas Zimmermann
wrote:
> Thanks!
>
> Am 14.01.2016 um 15:08 schrieb Lars Hansen:
>> On Thu, Jan 14, 2016 at 2:49 PM, Tho
> It only helps some games. Most game development efforts will likely be
> unaffected, since it's generally easiest to use an existing engine,
> which will already have such things handled.
>
> Most games will either just use overlayed HTML, or have an in-engine
> solution for UI. The desire to emb
Since the original m.d.p thread on hardwareConcurrency last year:
https://groups.google.com/d/topic/mozilla.dev.platform/QnhfUVw9jCI/discussion
the landscape has shifted (as always) and I think we should reevaluate
and implement this feature.
What hasn't changed are the arguments, made in the or
If we do unify Gecko/SpiderMonkey styles (something it seems like we're
moving towards and I think would be great), it would be a real shame to
switch 'cx' (a parameter to basically every function in SpiderMonkey) to
'aCx'; that would really make some eyes bleed. One compromise could be to
drop th
In addition to judging noisiness by volume over a whole test run, can we
also include any warning that happens on normal browser startup, new tab,
and other vanilla browser operations? This has always annoyed me.
On Thu, Jun 4, 2015 at 3:33 PM, Bobby Holley wrote:
> On Thu, Jun 4, 2015 at 1:18
It definitely makes sense to start your performance investigation with
processCount=1 since that will likely highlight the low-hanging fruit which
should be fixed regardless of processCount.
My question is: after a decent period of time picking the low-hanging
fruit, if there is still non-trivial
>
> > I think we probably want to use a longer delay than 300ms before we show
> > the spinner. We'd also like to look into why it takes so long to
> re-create
> > the layer tree when we switch to a tab. Sometimes it's caused by a janky
> > content process, but there may be some layout/gfx improvem
> Do you know what they actually mean when they use the term "hardware
> pointer"?
>
I believe what he's referring to is the type of hardware-accelerated cursor
support discussed here:
http://technet.microsoft.com/en-us/magazine/2009.02.windowsconfidential.aspx?pr=blog
and here
http://blogs.uni
I have a short summary of why caching JIT code is not necessarily a clear win
for most JS in a blog post:
http://blog.mozilla.org/luke/2014/01/14/asm-js-aot-compilation-and-startup-performance/#caching
We do machine code for asm.js, though (as also described in the post).
More interesting than
To save typing, the JS engine has typedefs like
typedef Handle HandleObject;
typedef Rooted RootedValue;
and the official style is to prefer the HandleX/RootedX typedefs when there is
no need to use the Handle/Rooted template-ids directly.
This issue was discussed off and on in the JS engine
14 matches
Mail list logo
