metajack

39 ms·

61.
by metajack 9y ago
And don't forget all the people not in pools! It's like a support program for lawyers...
62.
by metajack 9y ago
I'm not sure why High Sierra is broken, but there are issues filed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1379811 for the meta bug tracking all the ones we know about. I'm guessing this will be fixed in
63.
by metajack 9y ago
Pretty sure we are coordinating with them to make sure it's available for the Firefox Quantum release in November. So this is hopefully only going to be an issue during Nightly and Beta cycles, and not in the main population.
64.
by metajack 9y ago
If the issue is as bad as it looks like in that screenshot, the performance profiler should be able to spot what's happening easily. Take a look at https://perf-html.io/
65.
by metajack 9y ago
Beta for 57 rolls out today I believe.
66.
by metajack 9y ago
For normal web pages, rasterization of fonts is not a big deal. This is obviously not the case when projected into VR. WR rasterizes glyphs into font atlases and uploads those to the GPU. Those atlases are cached for use later and can be se
67.
by metajack 9y ago
We use hyper and rolled our own async support I believe, since it didn't exist at the time, but it is quite neglected and the general plan has been to move to futures and tokio. Firefox's network stack is called necko, and has bee
68.
by metajack 9y ago
I think there were alternative designs but either no one cared or people were determined to push WebAudio despite faults. An example alternative that was proposed is http://robert.ocallahan.org/2012/01/mediastreams
69.
by metajack 9y ago
The sequential traversal code is separate and does not have parallel overhead. On a single core machine you will get the sequential traversal. Note that Stylo is still faster than the old Gecko system even in sequential mode.
70.
by metajack 9y ago
I suspect you will hear a lot of numbers around the time of the 57 launch, and until then people will keep quiet as they try to make the numbers that get revealed as good as possible. For old numbers, you can get some in some of my old pres
71.
by metajack 9y ago
There's more to putting it in the product than just the code, but the style system in Servo does already work on Android. Once 57 ships, I suspect there will be some resources to start doing the remaining product integration work for F
72.
by metajack 9y ago
It should go out in Firefox 57 which is scheduled for November 14.
73.
by metajack 9y ago
There's a lot of refactoring to do in Gecko's graphics stack to fit the new rendering model. While they do that, they can also accelerate one thing at a time with WebRender, testing incrementally. Things like SVG which WebRender d
74.
by metajack 9y ago
I know lots of settings get reset when you get new Insider builds. It annoyed me constantly. Perhaps OP is on those?
75.
by metajack 9y ago
It runs in a separate process. I don't think that process is sandboxed in Firefox. And you probably can't restrict it too much or most Flash apps wouldn't work.
76.
by metajack 9y ago
Thankfully you can't obscure the DOM, but people certainly obscure JS and CSS plenty already. Mostly in the name of shrinking its size, but not always just that. Try to learn how a Google web app works by inspecting the source code som
77.
by metajack 9y ago
CDMs are sandboxed, which is an improvement over the NPAPI plugins. I don't think we have to worry much about Sony rootkit attacks at least.
78.
by metajack 9y ago
Free browsers can't play Netflix anyway, because EME is just a standardized interface to a proprietary CDM, which one must license from a vendor (Microsoft of Google mostly). What giving in achieved is a reasonable security story aroun
79.
by metajack 9y ago
Nothing forces web browsers to run any code except perhaps market pressures. Keeping EME out of the standard would have sent a political message, but since everyone is already shipping it, kind of a useless one. I am sad too. Perhaps there
80.
by metajack 9y ago
For doing without to work, all browsers must agree to do without. As soon as one browser ships it and people prefer browsers that can stream Netflix, everyone else must follow suit or wallow in obscurity. Microsoft and Google make CDMs; no
81.
by metajack 9y ago
It's a bit tough to argue we should keep computers insecure and hope people get annoyed and change their minds. Keeping people's computers safe is a primary goal of browser vendors, and this improves that state of affairs. Sure, D
82.
by metajack 9y ago
I feel like that case was true back when this fight actually mattered. These days people use native-ish apps on iPads and smart TVs and not just laptops. So I think there is less market power on the web's side than there used to be. Go
83.
by metajack 9y ago
Before DRM plugins could access anything. Now they live in a sandbox which was not possible when they were NPAPI plugins. So the security story is actually much better as far as I know. It still sucks to infect the web with this nonsense, b
84.
by metajack 9y ago
Every major browser ships this already. In Firefox you can choose not to download it, but in the rest it is always there I believe. The reason it was implemented is that Microsoft and Google both also make and sell the DRM systems that EME
85.
by metajack 9y ago
Which happened in Servo already: https://github.com/servo/servo/issues/1226
86.
by metajack 9y ago
Quantum is the name of the new web engine for Firefox. It started landing in the current release, and will land piece by piece over the next several releases. Servo is related because several of the big parts of this new engine are taken di
87.
by metajack 9y ago
There are only unsafe coders.
88.
by metajack 10y ago
The way add-ons are currently done significantly hampers the engine architecture, and is a good chunk of the reason why multi-process took so long. All this synchronous access to engine internals is also why the first advice diagnosing perf
89.
by metajack 10y ago
You forgot Servo in your list, which runs only on specific nightlies, though we do try to make most of the dependencies buildable on stable.
90.
by metajack 10y ago
There's some discussion of allowing beta for nightly Firefox builds. Since the Rust release cycle is slightly shorter than the Firefox one, this means Firefox release will always ship on stable Rust. Meanwhile, nightly can get bug fixe

More ›