Firefox continues to be my favorite software project. Part of this is idealism, of course (they serve a very important position in the browser market as a true non-profit). But unlike most other...
Firefox continues to be my favorite software project. Part of this is idealism, of course (they serve a very important position in the browser market as a true non-profit). But unlike most other FOSS project, it doesn't feel like a compromise: They not only do great under-the-hood work (performance is now on point) but also have a great UI team, it's an absolute pleasure to use. It feels like they're one step ahead of what features I could even come up with.
Agreed! I haven't used a chromium based browser in ages but was recently forced to install one for video calling. I was stupefied how hard the settings were to navigate. Feels like some of that is...
Agreed! I haven't used a chromium based browser in ages but was recently forced to install one for video calling. I was stupefied how hard the settings were to navigate. Feels like some of that is intentional to hide all the privacy settings..
Hopefully this will get better in upcoming versions of Firefox. We have identified this as an area of improvement for supporting users working through the pandemic.
I haven't used a chromium based browser in ages but was recently forced to install one for video calling.
Hopefully this will get better in upcoming versions of Firefox. We have identified this as an area of improvement for supporting users working through the pandemic.
Similar experience here. I've got Chrome installed because I periodically need it for applications that "only work on Chrome" (i.e. are crippled on Firefox), and every time I open it up I'm amazed...
Similar experience here. I've got Chrome installed because I periodically need it for applications that "only work on Chrome" (i.e. are crippled on Firefox), and every time I open it up I'm amazed by how slow it feels and how many browser nags I get to enable xyz privacy invading integration with Google service.
Excited about the rise of native lazy loading support. Nifty little feature, but never really wanted to depend on yet another JS library to implement it
Excited about the rise of native lazy loading support. Nifty little feature, but never really wanted to depend on yet another JS library to implement it
I took this as an opportunity to finally switch over from Chromium to Firefox. Getting all of my settings worked out now! Hopefully this begins my slow march away from Google.
I took this as an opportunity to finally switch over from Chromium to Firefox. Getting all of my settings worked out now! Hopefully this begins my slow march away from Google.
More of "now is as good a time as any" than firm reasons. I had been meaning to switch for a while but never got around to it, and reading through all of the features available made me finally...
More of "now is as good a time as any" than firm reasons. I had been meaning to switch for a while but never got around to it, and reading through all of the features available made me finally bite the bullet and switch over.
Hm... is loading="lazy" only a thing for img elements? I use picture elements quite a lot coupled with sources so that'd be a shame if it was only img elements. Since it mentions that Chrome wants...
Hm... is loading="lazy" only a thing for img elements? I use picture elements quite a lot coupled with sources so that'd be a shame if it was only img elements. Since it mentions that Chrome wants iframes, I assume it's not a thing to picture elements otherwise it would've been mentioned actually..
I haven't read through all of this, but it looks like this was discussed in the spec pull request: https://github.com/whatwg/html/pull/3752#issuecomment-462632789 Right now it seems to only apply...
I have always been a Firefox user up until about a year ago. For some reason, my tabs always crash (Pop_OS!) so I switched over to Brave which is based on the based on Chromium. About to install...
I have always been a Firefox user up until about a year ago. For some reason, my tabs always crash (Pop_OS!) so I switched over to Brave which is based on the based on Chromium.
About to install and see what happens as I love everything about it.
Firefox continues to be my favorite software project. Part of this is idealism, of course (they serve a very important position in the browser market as a true non-profit). But unlike most other FOSS project, it doesn't feel like a compromise: They not only do great under-the-hood work (performance is now on point) but also have a great UI team, it's an absolute pleasure to use. It feels like they're one step ahead of what features I could even come up with.
Agreed! I haven't used a chromium based browser in ages but was recently forced to install one for video calling. I was stupefied how hard the settings were to navigate. Feels like some of that is intentional to hide all the privacy settings..
Hopefully this will get better in upcoming versions of Firefox. We have identified this as an area of improvement for supporting users working through the pandemic.
Similar experience here. I've got Chrome installed because I periodically need it for applications that "only work on Chrome" (i.e. are crippled on Firefox), and every time I open it up I'm amazed by how slow it feels and how many browser nags I get to enable xyz privacy invading integration with Google service.
Excited about the rise of native lazy loading support. Nifty little feature, but never really wanted to depend on yet another JS library to implement it
I took this as an opportunity to finally switch over from Chromium to Firefox. Getting all of my settings worked out now! Hopefully this begins my slow march away from Google.
More of "now is as good a time as any" than firm reasons. I had been meaning to switch for a while but never got around to it, and reading through all of the features available made me finally bite the bullet and switch over.
It's going to take me some time to get used to the new address bar but it looks like an improvement over the previous one.
Hm... is
loading="lazy"only a thing for img elements? I use picture elements quite a lot coupled with sources so that'd be a shame if it was only img elements. Since it mentions that Chrome wants iframes, I assume it's not a thing to picture elements otherwise it would've been mentioned actually..I haven't read through all of this, but it looks like this was discussed in the spec pull request: https://github.com/whatwg/html/pull/3752#issuecomment-462632789
Right now it seems to only apply to
<img>and<iframe>as far as I can tell though.I have always been a Firefox user up until about a year ago. For some reason, my tabs always crash (Pop_OS!) so I switched over to Brave which is based on the based on Chromium.
About to install and see what happens as I love everything about it.