Manishearth

11 ms·

61.
by Manishearth 8y ago
Does setting gfx.compositor.glcontext.opaque to true in about:config fix the problem?
62.
by Manishearth 8y ago
"often" slowest of the bunch
63.
by Manishearth 8y ago
IIRC this isn't intentional, but it's not due to benevolence either: The whole custom elements fiasco (which is largely Google jumping the gun and shipping an unstandardized API that they eventually had to deprecate) means that so
64.
by Manishearth 8y ago
We haven't called it a day. The servo team still exists, we still work on Servo. Working on a production ready project is hard and takes forever, the integration work was a pit stop where we had an opportunity to get our work out to us
65.
by Manishearth 8y ago
IIRC this bug is known (something about compositing and rounded corners on Mac because of how Core Graphics works) and there's work going on to fix it. The Webrender stuff helps here too, I think. (I don't know the exact details,
66.
by Manishearth 8y ago
Slowest to implement things.
67.
by Manishearth 8y ago
Right, the point being made is that Webkit/Safari are often the slowest of the bunch which is fine when you have three others but now each browser effectively has veto power and the expectation is that Webkit will wield it often. It&#x
68.
by Manishearth 8y ago
You can have machines that receive and scan the ballot (instead of a simple box), without losing the paper trail, and keeping a count of the number of submitted ballots (the number of used ballots is also controlled and counted). Many place
69.
by Manishearth 8y ago
In Alameda County you deposit non-provisional paper ballots in a scanner which tallies it up. At the end of the day you get a printout of results (assuming there are enough voters to preserve privacy) which is posted outside and submitted t
70.
by Manishearth 8y ago
This isn't a changelog, this is a newsletter for folks wanting to keep up with development.
71.
by Manishearth 8y ago
You're literally talking to one of the main initial people behind the Mozilla project that uses the GPU for browser rendering more than any other browser, on the comments of a post about this stuff making its way to a release. Webrende
72.
by Manishearth 8y ago
I've discussed this a fair bit and we have a rough plan, but the idea is to wait for other things to localize first.
73.
by Manishearth 8y ago
> There's a very sound argument to be made for the opposite conclusion, that if we care about a problem we should make it necessary to solve the problem correctly or else stuff very obviously breaks, not have broken systems seem lik
74.
by Manishearth 8y ago
I think a more accurate characterization is that neither code points nor grapheme clusters are usually what you want, but when you're naively processing text it's usually better to go with grapheme clusters so you don't mess
75.
by Manishearth 8y ago
You probably have search suggestions in firefox turned off (they may be off by default?). Works for me when I flip it on https://i.stack.imgur.com/0ZfvX.png . I keep it off because I don't like having my every keystrok
76.
by Manishearth 8y ago
Yeah, this is true. We do the equivalent of telling the compiler that things don't alias at function boundaries (i.e. restrict) and not much more. Nobody writes C code with restrict all over the place, which means that not only is this
77.
by Manishearth 8y ago
I don't use an adblocker -- I just use Firefox with tracking protection on. I'm okay with ads, just not track-y heavy ads, and Tracking Protection does the trick. You may want to look into why Tracking Protection doesn't like
78.
by Manishearth 8y ago
It's implemented, it's preffed off. These things take time to roll out properly. Chrome jumped the gun on v0, Firefox/Edge aren't "dragging their feet".
79.
by Manishearth 8y ago
For the first one, this is pretty well known : Google "shadow dom v0" v0 is the old stuff chrome shipped before there was consensus, and it's pretty different from v1, which is what the spec settled on. To be clear, "is
80.
by Manishearth 8y ago
"impossible" is a highly contextual term here. Adding this to Rust isn't "impossible", of course it isn't. We can "just" slowly turn Rust into Haskell using the edition mechanism. Done. When folks say
81.
by Manishearth 8y ago
Given that Send is autoimplemented for things that should be Send, this is a strong indication towards your code attempting to send actually not-thread-safe things across threads (things containing borrowed references or Rc<T>) The er
82.
by Manishearth 8y ago
Support for multiple accounts in drive is pretty great (minor papercuts here and there) as long as all but one of your accounts is an Apps account. This feels like an issue that they've fixed but not rolled out. Except this has been a
83.
by Manishearth 8y ago
That's probably because your work account is a Google Apps account, which works much better especially for Drive (the problem is that you can't have more than one non-Apps account using drive at once in the same session. I have no
84.
by Manishearth 8y ago
Free: - The book: https://doc.rust-lang.org/book/second-edition/index.html - Rust By Example is also good but it may currently be out of date (folks are working to improve it) Paid: - The O'Reilly book by Jim
85.
by Manishearth 8y ago
Yeah, the plan is for async/await to be part of the 2018 edition, but it's going to take some time.
86.
by Manishearth 8y ago
Both. I'm saying they work together fine, and isolate works fine with Google logins. It's not that strict.
87.
by Manishearth 8y ago
Google logins still work, this is a different kind of container from the Firefox container tabs. I use this feature with container tabs and it's fine. There are so far one or two sites I've come across that this breaks, neither of
88.
by Manishearth 9y ago
> But isn't it an anti-pattern to wrap something in an `Arc` when some of your use cases for it are purely single-threaded, and as such you're wasting a certain (potentially very significant) amount of performance on upholding
89.
by Manishearth 9y ago
Arc::make_mut is really nice and is something we use a bunch in Stylo to safely mutate possibly-shared styles. Across threads.
90.
by Manishearth 9y ago
> Using refcounts to get around an overly aggressive borrow checker seems to be an ugly developing pattern in rust Every single large, "modern", C++ codebase I've worked with uses way more refcounts than is typical in Rust

More ›