Marco Alka yes I will answer in more detail but first I have to finish a feature so I hope I'm able to answer in the evening :)

Marco Alka

• chrome timeline -> click on timeline and tada you got all the profiling information you need from memory to execution and so on. you can do something similar in firefox but the UX in chrome is much better and feels more natural

• firefox 3d representation of the dom -> ff uses webgl to render you a topographic map of your components so it's easy to see how they elements are actually placed on the z-index developer.mozilla.org/en/docs/Tools/3D/_View

• ff memory snapshot the options of how to display the memory are decoupled from the performance which means a clearer picture about the overall memory and exectution model, still the chrome timeline is just awesome but it takes time as the factor while ff does not care when it's executed -> different access but good for overall optimizations. you can have something similar in the chrome profiles but I think FF does a better job here.

i personally prefer the FF http inspection this is pure taste because I know the toolset.

and tbh I think that's it on my part. the react / redux tools are basically the same.

I have to say I did not test everything but from a pure programming frontend developer perspective chrome seems to be the more natural choice. it has an awesome easy access toolset.

gg I think to compare them I would have to create a list with all features and compare them side by side in detail with all options.