HNHacker News
TopNewBestAskShowJobs

tschneidereit

131 karma · joined October 23, 2014

WebAssembly & Components & WASI @ Akamai. Started and help lead the Bytecode Alliance.
submissionscomments
tschneidereit··on Firefox Nightly now plays Amazon.com Flash videos using Shumway
Media codecs are a very common source of security holes, which is one of the main reasons for not indiscriminately using just any codec that might be installed on the system. I think most users value the decision to not unnecessarily expose them to these security holes.

Also, that wouldn't change anything about the current situation: we still can't rely on users having the right codecs installed. We're not saying that Linux and Windows XP won't be supported going forward. They most definitely will. As part of this first small step towards deployment, we opted for a conservative approach where we only enable Shumway in situations we have the maximum amount of control over. This will be broadened over time.

tschneidereit··on Firefox Nightly now plays Amazon.com Flash videos using Shumway
I think letting the browser do this kind of caching for you is best in most cases. Developers have used tricks to force browsers to layerize content for many years, and browsers have become better at that over time. Nowadays, it should be fairly simple to isolate complex but unchanging content into its own layer that's cached and composited with the rest of the page instead of being rerendered for each page update.

In Shumway, we do almost all rendering in a Canvas element, so we haven't experimented all that much with DOM-heavy constructs.

As for your last question: I used to work with AS3 on a daily basis in a previous work-life, so I have extensive experience with it. Yes, there are some parts of the language that're very nice. I think that optional static typing is the best of all worlds, for example. The details of AS3's type system leave much to be desired, but the IDE support gained through static typing and the large set of bugs that're far easier to avoid are easily worth it.

Also, declarative classes are, in my opinion much easier to deal with than, e.g., the unstructured alternatives in JS. That's part of why we moved to TypeScript, and I'd argue that it vastly improved the quality of our codebase. I'm very much looking forward to classes in ES6.

Of course there are things that I don't miss about AS3 and regret having to deal with in Shumway. Namespaces are one, E4X the other. Both are good concepts in theory but hugely problematic in practice because of issues in the details.

tschneidereit··on Firefox Nightly now plays Amazon.com Flash videos using Shumway
This is indeed a major consideration: Flash will undoubtedly go away as a player, and if we don't want to lose all the legacy content with it as if it were stored on floppy disks, Shumway or something like it is the only solution.

Note that for a lot of content, it's not even required to use Shumway in the form of a browser extension or built-in system: it's perfectly possible to run SWFs with Shumway as a website-deployed player. E.g., the header on http://areweflashyet.com is deployed that way and works just fine in all modern browsers.

tschneidereit··on Firefox Nightly now plays Amazon.com Flash videos using Shumway
(Shumway tech lead here)

Somewhat absurdly, you currently need Flash to use Flash without Flash in many cases. We don't yet have support for installing Shumway in navigator.plugins, so sites that detect Flash using that (i.e., most of them) currently only work in Shumway if Flash is installed, too.

This will be fixed once https://bugzilla.mozilla.org/show_bug.cgi?id=558184 lands.

tschneidereit··on Mozilla Research Projects
Structs are coming to JS proper in the form of Typed Objects. For a whole load of details, check the spec draft (https://github.com/dslomov-chromium/typed-objects-es7) or this very readable paper: http://smallcultfollowing.com/babysteps/pubs/2014.04.01-Type...

Implementation of Typed Objects is progressing very nicely in Firefox; if you want to play around with them, just download a Nightly build.

tschneidereit··on Mozilla Research Projects
We're moving away from the attach-patches-to-bugs model, but in another direction: bugzilla integration with reviewboard, with changesets pushed to a review server and review requests being triggered automatically.

See https://mozilla-version-control-tools.readthedocs.org/en/lat... for details

tschneidereit··on Mozilla Research Projects
Full support for contributing to Firefox via git is coming: http://glandium.org/blog/?p=3413
tschneidereit··on Mozilla Research Projects
Several things:

As of recently, that trend has finally stopped: Firefox has started gaining (very) small amounts of market share recently. The point where the speed of user attrition slowed down was actually slightly before the Australis launch, but after that, the development sped up considerably.

Thus, it looks like Australis helped substantially with winning back users.

Plus, a few years ago, the competition was essentially IE6/7. Not hard to gain market share against that. Now there are several great browsers to choose from. Which I'd say is a fantastic development, even though I work for Mozilla.

Finally, there are the billions of dollars that e.g. Google pours into advertising for Chrome, which might have something to do how market share developed.

tschneidereit··on Google Inbox
That makes a lot of sense, yes. We can profile cases like that and get info/help from people working on the relevant components. It happens fairly frequently that we move perf bugs from the JS component into GFX or DOM bindings or something else entirely. So really, just file a bug in one of these components, maybe CC a person you already interacted with or send an email, and we'll do the triage.
tschneidereit··on Google Inbox
(SpiderMonkey engineer here)

What VerGreeneyes says is true for our JS engine, too: you can always file bugs in our bugzilla (in the "Core/ JavaScript Engine" component). We react to such bugs very promptly (as you can see in bug 1087963[0] which was fixed six hours after being filed) and, in many cases, can uplift patches from Nightly to Aurora and maybe Beta, so they'll reach release builds more quickly.

If for some reason you're not comfortable with filing a publicly visible bug, you can also abuse the flag for filing security-sensitive bugs. That way, we may be better able to help with issues affecting unannounced products.

For asking questions or getting our attention even more quickly, you can either join us in the #jsapi channel on irc.mozilla.org, send mail to dev.tech.js-engine[1], or send mail to one of the SpiderMonkey engineers directly. A list of these engineers is available at [2], or you can just email me at [my nick]@mozilla.com.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1087963 [1] https://lists.mozilla.org/listinfo/dev-tech-js-engine [2] https://wiki.mozilla.org/index.php?title=Modules/Core#JavaSc...

← PreviousPage 2 of 2