Attached: 2 images
I have no idea why people use #Chrome. #Firefox looks so much better, and their theme actually works! Even their hidden compact theme looks perfect, the padding around elements is always the same... meanwhile Chromium uses tons of different shapes and they are all incoherent and the padding is off.
Apart from the fact that Firefox is #efficient has core components rewritten in #rust and supports #wayland for way longer.
#Librewolf is a perfect addition to Firefox, I highly recommend to use it!
A little admiration of how easy UI customization is on Firefox, and how shitty Chromium looks.
You say Angular. But what else can we expect for a framework for making WebKit/Chromium apps.
Angular working in Firefox is an afterthought because it has very much similar featureset.
I’ve to work with what I got :P Either way even if I was doing jQuery or Vue (like I did in the past) I wouldn’t ever use Firefox because even without the Angular extension, just plain JS/CSS debugging I like Chromium dev tools more.
Besides the fact that my target users are always Chrome users and by using Firefox for development in the past I run into issues because specific features would work in Firefox but not on Chrome and vice-versa… or some piece of CSS rendered differently Chromium offers a level of polishness on small details that Firefox wasn’t ever close to. Firefox’s dev tools are always playing catch-up time to Chromium’s, that’s what I see.
Maybe I’m biased like you seem to be, but in the opposite way :P
You say Angular. But what else can we expect for a framework for making WebKit/Chromium apps. Angular working in Firefox is an afterthought because it has very much similar featureset.
I’ve to work with what I got :P Either way even if I was doing jQuery or Vue (like I did in the past) I wouldn’t ever use Firefox because even without the Angular extension, just plain JS/CSS debugging I like Chromium dev tools more.
Besides the fact that my target users are always Chrome users and by using Firefox for development in the past I run into issues because specific features would work in Firefox but not on Chrome and vice-versa… or some piece of CSS rendered differently Chromium offers a level of polishness on small details that Firefox wasn’t ever close to. Firefox’s dev tools are always playing catch-up time to Chromium’s, that’s what I see.
Maybe I’m biased like you seem to be, but in the opposite way :P