dblohm7

70 ms·

811.
by dblohm7 10y ago
I pledged on Kickstarter to receive a pair of these (still in manufacturing), but maybe they'd help? https://www.kickstarter.com/projects/branchusb/magneo-first-...
812.
by dblohm7 10y ago
XUL extensions may not include binary components anymore.
813.
by dblohm7 10y ago
You've got that backwards. The foundation owns the corporation.
814.
by dblohm7 10y ago
You must be running Windows. I'm the Mozilla developer who is responsible for that. You'll get e10s on touchscreen in version 52.
815.
by dblohm7 10y ago
https://wiki.mozilla.org/Platform/GFX/Quantum_Render
816.
by dblohm7 10y ago
> And instead of getting engineers, you're wasting your money on political stuff. Mozilla has never been just about shipping a browser. That "political stuff" that you are so dismissive of is a core part of Mozilla's
817.
by dblohm7 10y ago
> The Firefox project is literally years behind in security and performance, I think the Mozilla Foundation doesn't understand how critical the current situation is. https://blog.mozilla.org/blog/2016/08&#x
818.
by dblohm7 10y ago
Our "Stage 1" sandbox is out on Windows in version 50. If you want to dislike us, fine, but at least do so for valid reasons.
819.
by dblohm7 10y ago
Out of curiosity, why would you switch if it weren't for vimperator?
820.
by dblohm7 10y ago
It does: http://www.fark.com/farq/
821.
by dblohm7 10y ago
You seem to be confusing NPAPI plugins with browser extensions. Firefox doesn't allow addons that contain binary XPCOM components anymore. Everything has to be JS, whether the addon is XPCOM based, addon SDK (JetPack) based, or WebExte
822.
by dblohm7 10y ago
Or maybe this: https://www.kickstarter.com/projects/branchusb/magneo-first-...
823.
by dblohm7 10y ago
If you write software using a language with a compilation step, you certainly need the latest and greatest.
824.
by dblohm7 10y ago
Here are a couple of links that outline the design and contain some notes: https://wiki.mozilla.org/Electrolysis/Accessibility#Windows http://dblohm7.ca/blog/2016/04/06/new-team-new-
825.
by dblohm7 10y ago
Chrome was a greenfield product with no extension ecosystem to contend with. Trying to overhaul the entire architecture of a browser with a huge extension ecosystem (and over a decade's worth of baggage associated with that) is hard.
826.
by dblohm7 10y ago
I'm the dev who is responsible for the Windows implementation. It has been quite the... gnarly experience to say the least. We were shooting for 52 for enabling a11y+e10s, but it is increasingly looking like we're going to need to
827.
by dblohm7 10y ago
Both of those topics are discussed in the blog post, btw.
828.
by dblohm7 10y ago
See the Firefox Privacy Notice [1]. This kind of data is part of the "Firefox Health Report," which is opt-out. [1] https://www.mozilla.org/en-US/privacy/firefox/
829.
by dblohm7 10y ago
I prefer going through US Preclearance in Canada due to the fact that I am still subject to Canadian law when doing so. I don't understand why this wasn't even mentioned in the article.
830.
by dblohm7 10y ago
It's hard though. If we publicly call out specific AV vendors like that, they might be less motivated when we ask them to fix said shit.
831.
by dblohm7 10y ago
Firefox dev here. All browsers have a big bulls-eye on their foreheads with respect to AV, and it's not just security features that are held up. These AV products patch our binaries all over the place such that changing any browser int
832.
by dblohm7 10y ago
AV is also the biggest impediment to shipping a stable browser. I'll be spending some quality time next quarter adding mitigations to Firefox to prevent AV software injecting code into our process.
833.
by dblohm7 10y ago
You're assuming that your needs are representative of most users.
834.
by dblohm7 10y ago
Albertan here: Your redneck stereotyping is way off.
835.
by dblohm7 10y ago
Regarding high DPI, I beg to differ. A lot of Windows applications look like shit on high DPI.
836.
by dblohm7 10y ago
The limit is enforced unless an application ops out of it.
837.
by dblohm7 10y ago
> That's not true. Servo is designed to be production-grade. I never said that it wasn't. I said that it wasn't going to be shipped as a production Mozilla product.
838.
by dblohm7 10y ago
Servo has always been and still is a research project. It was never intended to go into production as a fully-fledged Mozilla product. Quantum is the initiative to bring a lot of those technologies into Gecko.
839.
A Quantum Leap for the Web(medium.com)
4 points by dblohm7 10y ago|0 comments
840.
by dblohm7 10y ago
No, it is because NPAPI is a stability and performance nightmare. No sane person in 2016 would want to port it to Servo or anything else.

More ›