4 ms·
"putting in some necessary optimizations"? That sounds suspicious. If it's an optimization, it should be contributed upstream to benefit all the users of Gecko
by Yoric 8y ago
"putting in some necessary optimizations"?
That sounds suspicious. If it's an optimization, it should be contributed upstream to benefit all the users of Gecko/Firefox.
Or are these optimizations to XUL-only codepaths that are not present/executed in Firefox anymore?
- dictum 8y agoThe maintainer(s?) have some peculiar opinions: "We already have CSS table layouts... Why is this suddenly needed? why would sites switch to it? It makes no sense. It wasn't important enough to implement in any browser for the past 6 years so there's no real reason why websites would suddenly want to swap to it." (on the CSS Grid spec) https://forum.palemoon.org/viewtopic.php?t=15196 https://forum.palemoon.org/viewtopic.php?t=15196
- extra88 8y agoYikes. At least Basilisk is a fork of Firefox after it made CSS Grid support public (I don't know how how long it was behind a flag or how much the code changed in that time). It doesn't bode well for support for other, newer standards, like variable fonts.
- mrnhmath 8y agoMaintainers. It isn't a one-man show. Their approach to development is to implement things when there's enough user demand e.g CSS Masking, which someone from the community is working in.
- jcranmer 8y agoWhen one of these projects came out several years ago, what they touted as optimizations were a) releasing an x86-64 build instead of x86 build on Windows (at a time when the x86-64 JIT actually performed worse than x86, and this was known to the Mozilla team), and b) using manual compiler optimization flags a la Gentoo's -funroll-loops options.