211–220 of 256 posts
Recently switched back to Firefox. Their search engine selection option is so easy and excellent. On Chrome, non-technical people won't be able to change default search engine. Thanks Mozilla.
Earlier quoted context omitted.
Chrome SignIn is basically the same thing as Firefox Sync. It keeps your bookmarks, extensions, and stored passwords (all controllable) in sync between the different devices you use the browser on.
The key difference being that Firefox's implementation gives you all this without having to let Google rifle through the data you want to sync.
Recently switched back to Firefox. Their search engine selection option is so easy and excellent. On Chrome, non-technical people won't be able to change default search engine. Thanks Mozilla.
See the bottom of this screen shot:
I just updated and it broke my selenium scripts.
Not quite related to this particular release, but I kind of wish sync for extension data wasn't Opt-In. Having to hunt down the option to turn on Sync for each extension explicitly and not even having that option for some extensions makes for a rather poor user experience. Also, as someone who customizes the browser layout rather extensively, I'd like to see layout settings included in Sync as well (which toolbars ar…
It's totally unreasonable that I should have to start up applications in a sandbox after each upgrade and/or hire a team of lawyers to go over the EULA/TOS to find what new & interesting ways have been found to sell my personal info.
(Responding to your general point btw rather than specifically against Mozilla, who compared to the alternatives do seem to care about their users privacy, nor Sync which which you have to opt in for)
Earlier quoted context omitted.
Sprites are way more demanding memory wise than smaller images.
Performance on the Web isn't RAM-bound at this time, unless you're running on a Raspberry Pi or somethin. Network performance is a much stronger limiting factor, which is why protocols like HTTP/2 are being made in the first place. I'm also skeptical that sprites must necessarily be significantly more demanding memory-wise than smaller images. Implementations may vary, but at least in current browsers, when you make…
Earlier quoted context omitted.
I did try arch wiki advices, I got some results but I didn't really understand what I was doing and had lots of undesired side-effects (emacs buffer redraw failed, screenshot aliasing failed,...) so I dropped everything and used stock config. The xml config files seems overly complex (I admit, I suffer from acute xml ad-formatem) for my tastes. I tried to diff manjaro linux /etc/fontconfig actually, just to see what…
On Debian defaults are all under /etc/fonts About general idea of what all those settings are, here is a brief overview: https://en.wikipedia.org/wiki/Font_rasterization FontConfig rules can even be applied to Web fonts, which at times can be messed up by default. Example of such rule for fixing some mess on DuckDuckGo: @font-face:DDG_ProximaNova true lcddefault The difference it made for me (note the word Wikipedia…
Earlier quoted context omitted.
Fonts configuration is always rather subjective. I often don't like defaults. This applies to any system. Good ones allow greater flexibility. Bad ones assume they know best and force "best defaults" without any way to improve them.
Is not about font taste, is about brokenness, you can clearly see in the screenshot that the fonts are rendered poorly, some letters are lighter than others, half of a letter is lighter than the other half, some don't look smooth, etc...
Others have also mentioned that the subpixel order differs from monitor to monitor, so if the screenshot was taken on a monitor with BGR subpixels and your monitor has RGB subpixels, the text will look much, much, worse than if there had been no subpixel rendering at all. Or perhaps you, like me, have a CRT and subpixel rendering always looks wrong. It's hardly Firefox's fault.
Earlier quoted context omitted.
I did try arch wiki advices, I got some results but I didn't really understand what I was doing and had lots of undesired side-effects (emacs buffer redraw failed, screenshot aliasing failed,...) so I dropped everything and used stock config. The xml config files seems overly complex (I admit, I suffer from acute xml ad-formatem) for my tastes. I tried to diff manjaro linux /etc/fontconfig actually, just to see what…
On Debian defaults are all under /etc/fonts About general idea of what all those settings are, here is a brief overview: https://en.wikipedia.org/wiki/Font_rasterization FontConfig rules can even be applied to Web fonts, which at times can be messed up by default. Example of such rule for fixing some mess on DuckDuckGo: @font-face:DDG_ProximaNova true lcddefault The difference it made for me (note the word Wikipedia…
Earlier quoted context omitted.
Sprites are way more demanding memory wise than smaller images.
Performance on the Web isn't RAM-bound at this time, unless you're running on a Raspberry Pi or somethin. Network performance is a much stronger limiting factor, which is why protocols like HTTP/2 are being made in the first place. I'm also skeptical that sprites must necessarily be significantly more demanding memory-wise than smaller images. Implementations may vary, but at least in current browsers, when you make…
The memory usage of CSS sprites (which are implemented as css background images rather than Image objects) was definitely an issue a couple of years back. Inlining the images as base64 data uris seems much better.
