bholley

8 ms·

1.
by bholley 23d ago
Thanks all. I'm really happy with how it all turned out.
2.
by bholley 6mo ago
The system is mediated by the browser, so the source code can be inspected by anyone and verified not to leak information.
3.
by bholley 6mo ago
The idea is to leverage information from site A (say, a bank) who knows a lot about the user to attest to site B (say, HN) that the user is a real person, without revealing any other information known by site A to site B.
4.
by bholley 5y ago
Sorry, I should have been more clear. I believe we use the masking on 32-bit platforms, which is faster than explicit bounds checks. On 64-bit platforms we use guard pages. We don't actually need a signal handler, because we don't
5.
by bholley 5y ago
I believe the implementation in Firefox masks off the high bits of pointers and adds the result to the base address before performing a load/store. This requires us to reserve a power-of-two-sized region of address space, but we can la
6.
by bholley 5y ago
Deukhoofd is correct — we compile the WASM code back into C in order to reuse and reduce friction with our existing compilation pipeline.
7.
by bholley 5y ago
It varies. Here's an example of some performance analysis I did on the expat port: https://bugzilla.mozilla.org/show_bug.cgi?id=1688452#c37
8.
by bholley 5y ago
Beyond the reasons others have mentioned, another key issue is that this isn't a transparent transformation. The sandboxed code can only access memory within a restricted subregion, which often requires some small code changes on both
9.
by bholley 5y ago
The purpose of RLBox is to add an extra layer of component-level isolation on top of Firefox's process-based site-level isolation. The reduced overhead is relative to the hypothetical scenario in which we performed the component-level
10.
by bholley 6y ago
We made the decision several years ago to integrate Servo components individually rather than trying to replace the entire engine (for the reasons outpost in the blog post linked above). We invest a lot in Gecko though, precisely because it
11.
by bholley 6y ago
Respectfully: The Firefox layout team did not have a plan to integrate Layout 2020 (we hadn't yet found a way to ship it incrementally), and doing so was never the basis of our strategy to compete with LayoutNG.
12.
by bholley 6y ago
I led the Stylo project to integrate Servo's CSS engine into Firefox as part of project Quantum [1]. I have the utmost respect for the engineers on the Servo team, and am sad to see them go (though I am certain they will have no shorta
13.
by bholley 8y ago
See https://bugzilla.mozilla.org/show_bug.cgi?id=1511726 Assuming you're on non-Windows, the message is expected and not indicative of a problem. I've pushed a patch to disable it going forward. Sorry for the nois
14.
by bholley 8y ago
Yeah, we do prioritize Mac disproportionately to its market share for that reason. It does sometimes happen that we have to make hard calls though, and that's what Jeff is referring to. On that note, one of the key motivators behind We
15.
by bholley 8y ago
Sounds like ghost windows. Try disabling all your add-ons to see if the problem persists? You can also record a profile via perfht.ml and send it to me, I'm happy to have a look.
16.
by bholley 9y ago
Using the rhetoric of the parent, in case that wasn't clear.
17.
by bholley 9y ago
Per my comment above, there's a misunderstanding here. The goal was to delight Mr Robot viewers and turn them into Firefox users. This was about marketing, not revenue, and I believe no money changed hands.
18.
by bholley 9y ago
Thank you (and pault) for the kind word and understanding!
19.
by bholley 9y ago
I'm not privy to the details, nor have I ever seen Mr Robot. That said, I believe there were hints in the show about using Firefox to solve some mystery. The idea was that users would then go open Firefox (which may have been sitting u
20.
by bholley 9y ago
My impression (without any internal knowledge on the subject) is that this was intended as a way to promote Firefox to Mr Robot viewers. A lot of people in this thread seem to have this backwards, IIUC - it's not an ad for Mr Robot, it
21.
by bholley 9y ago
Since I gave that talk, it's become more clear to me that servo's layout engine is a lot farther from feature-complete than the CSS engine was. So my hunch is that the granularity of incrementalism we used for stylo may not be wor
22.
by bholley 9y ago
In more detail: For the original FirefoxOS security model, sicking and jlebar rototilled all the security checks in the codebase to switch from comparing origins to comparing (origin, appId, isInMozBrowser) tuples. Later on, for the eventua
23.
by bholley 9y ago
Yeah, the key reason Rust is necessary here is that there is an insane amount of complexity in the heart of modern web engines. Injecting concurrency into the intersection of DOM and Layout is only realistic with some kind of static guarant
24.
by bholley 9y ago
This is an easy benchmark for rejecting a lot of selectors: http://bholley.net/testcases/style-perf-tests/perf-reftest/b... Firefox with STYLO_THREADS=1 gets about 160ms on my machine, which is basically pari
25.
by bholley 9y ago
It's even better now - we get down to about 14ms with various recent improvements in style sharing.
26.
by bholley 9y ago
Note that everything in components/layout is servo-specific and not used by Stylo / Firefox. The code in components/style is shared, and the code that hooks it up to Firefox is in ports/geckolib/glue.rs (specificall
27.
by bholley 10y ago
> So I think this is not really a leap for the web. Just FireFox catching up a bit. To be clear, Project Quantum is the next phase of architecture, post-Electrolysis. We're also simultaneously working on multiple content processes (
28.
by bholley 11y ago
I think you're both misinterpreting the title. The sign is near the ceiling. It's not a question of some people being taller than others. Nobody is that tall - not even dbaron (pictured in the photo), who is one of Mozilla's