Lackluster comped to chrome Dev tools. A11y has been a staple feature in cdt for years and keeps getting better. Chrome is by far the best browser in every sense that really matters.
Only point I agree with is the fact that we are going to be in a mono browser world (albiet, being open source is good), and they no longer "don't be evil", quite the opposite. Whatever is good for them comes first, unfortunately. FF is just so damn slow, Dev tools especially. And setting up a Charles proxy?... Ugh
I think Chrome and Firefox each have their own strengths, but Firefox is really great for any kind of layout/styling work. Grid inspector is fantastic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What makes them better than Chrome devtools?
To do unit tests, native integration with different debug tools is better, better integration with the dom
Lackluster comped to chrome Dev tools. A11y has been a staple feature in cdt for years and keeps getting better. Chrome is by far the best browser in every sense that really matters.
Only point I agree with is the fact that we are going to be in a mono browser world (albiet, being open source is good), and they no longer "don't be evil", quite the opposite. Whatever is good for them comes first, unfortunately. FF is just so damn slow, Dev tools especially. And setting up a Charles proxy?... Ugh
FF has dedicated tab for accessibility which shows accessibility tool and how each node is behaving.
FF also has dedicated tab with sliders to play with font size, line height, weight etc. With drop down of switching between different css units.
It also gives very dev friendly view of flex and grids. This helps a lot in debugging.
I think Chrome and Firefox each have their own strengths, but Firefox is really great for any kind of layout/styling work. Grid inspector is fantastic.