5 ms·

can it cause perfomance issue ? I know for example the devtool is written in react and it's a lot slower than chrome devtools (I don't know how chrome devtool

can it cause perfomance issue ? I know for example the devtool is written in react and it's a lot slower than chrome devtools (I don't know how chrome devtool is written) and the javascript debugger is sometime not even usable because it's so slow.

warpech 7y ago
Chrome DevTools use Web Components: https://github.com/ChromeDevTools/devtools-frontend https://github.com/ChromeDevTools/devtools-frontend
saagarjha 7y ago
I believe the developer consoles for all three major desktop browsers (Chrome, Firefox, and Safari) are written using web technologies.
- floatboth 7y ago
  Yes. In fact, "Safari devtools" are really a part of upstream WebKit. You get them in e.g. Epiphany (GNOME Web) too.
  - saagarjha 7y ago
    Yup, I'm aware and use the on GNOME Web too. It's fun to point the web inspector at itself :)
Touche 7y ago
Using web components or something else is only one small part of the performance question. They could be using both web components and React for all we know. They could be using any number of JavaScript libraries that could be harming performance. They could be using raw DOM manipulation which could be either very fast or somewhat slow depending on how well it was implemented. All we can say is that using JavaScript in general is slower than using C++ but they weren't using C++ before anyways.
thayne 7y ago
chrome devtools are also written in javascript (although I'm not sure which framework if any they use). You can even debug the chrome devtools with chrome devtools (I think the same applies to firefox, although I've never accidentally gotten into that state like I have in chrome).
- the8472 7y ago
  about:config -> devtools.chrome.enabled = true then you should have additional entries in the tools -> web developer menu.
jkaptur 7y ago
Chrome devtools is also a JS application: https://github.com/ChromeDevTools/devtools-frontend https://github.com/ChromeDevTools/devtools-frontend.
- ergo14 7y ago
  In fact it looks like it is also webcomponents. https://github.com/ChromeDevTools/devtools-frontend/blob/master/front_end/inspector_main/InspectorMain.js#L99 https://github.com/ChromeDevTools/devtools-frontend/blob/mas...
jasonlaster11 7y ago
Hi, Firefox DevTools Debugger engineer here. We've focused on performance and quality over the past six months and believe it should be much better. If you're still seeing issues, feel free to record a performance profile and send it to us: - https://profiler.firefox.com/ https://profiler.firefox.com/ - https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&component=Debugger https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&... I'd be happy to fix it!
- abacadaba 7y ago
  ty for the effort! this is pretty much what has kept me developing chrome first.
- the8472 7y ago
  I find it mildly amusing that there's a profiler in the devtools. And yet there is another profiler that is at times more powerful than it. I have used the gecko profiler from time to time to identify which feature the page was using that slowed down the entire browser. Multi-process means just debugging a single tab doesn't give you the whole picture.
  - skunkpocalypse 7y ago
    Profilers profiling profilers. Because why Do It Right The First Time when you can slap another layer onto the stack?
- alexkoeh 7y ago
  Is it possible for Cmd+P to work when you don't have the Debugger tab in focus? That one of the few things I miss from Chrome dev tools. Performance-wise it's been running great for me. The hard work you've put into this definitely shows.
- everybodyknows 7y ago
  To any other devs who like me who want to use Firefox Debugger, but were driven back to the devil Chromium by need for consistent, seamless copy-paste and select-middlemouse interaction: Give 70.0.1 a try. Much, much better. So much that I've dropped Chromium. (Ubuntu 18.04)
kart23 7y ago
Really? I prefer the firefox devtools over chrome. They're pretty similar though.

warpech 7y ago

Chrome DevTools use Web Components: https://github.com/ChromeDevTools/devtools-frontend https://github.com/ChromeDevTools/devtools-frontend

saagarjha 7y ago

I believe the developer consoles for all three major desktop browsers (Chrome, Firefox, and Safari) are written using web technologies.

floatboth 7y ago
Yes. In fact, "Safari devtools" are really a part of upstream WebKit. You get them in e.g. Epiphany (GNOME Web) too.
- saagarjha 7y ago
  Yup, I'm aware and use the on GNOME Web too. It's fun to point the web inspector at itself :)

Touche 7y ago

Using web components or something else is only one small part of the performance question. They could be using both web components and React for all we know. They could be using any number of JavaScript libraries that could be harming performance. They could be using raw DOM manipulation which could be either very fast or somewhat slow depending on how well it was implemented. All we can say is that using JavaScript in general is slower than using C++ but they weren't using C++ before anyways.

thayne 7y ago

chrome devtools are also written in javascript (although I'm not sure which framework if any they use). You can even debug the chrome devtools with chrome devtools (I think the same applies to firefox, although I've never accidentally gotten into that state like I have in chrome).

the8472 7y ago
about:config -> devtools.chrome.enabled = true then you should have additional entries in the tools -> web developer menu.

jkaptur 7y ago

Chrome devtools is also a JS application: https://github.com/ChromeDevTools/devtools-frontend https://github.com/ChromeDevTools/devtools-frontend.

ergo14 7y ago
In fact it looks like it is also webcomponents. https://github.com/ChromeDevTools/devtools-frontend/blob/master/front_end/inspector_main/InspectorMain.js#L99 https://github.com/ChromeDevTools/devtools-frontend/blob/mas...

jasonlaster11 7y ago

Hi, Firefox DevTools Debugger engineer here. We've focused on performance and quality over the past six months and believe it should be much better. If you're still seeing issues, feel free to record a performance profile and send it to us: - https://profiler.firefox.com/ https://profiler.firefox.com/ - https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&component=Debugger https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&... I'd be happy to fix it!

abacadaba 7y ago
ty for the effort! this is pretty much what has kept me developing chrome first.
the8472 7y ago
I find it mildly amusing that there's a profiler in the devtools. And yet there is another profiler that is at times more powerful than it. I have used the gecko profiler from time to time to identify which feature the page was using that slowed down the entire browser. Multi-process means just debugging a single tab doesn't give you the whole picture.
- skunkpocalypse 7y ago
  Profilers profiling profilers. Because why Do It Right The First Time when you can slap another layer onto the stack?
alexkoeh 7y ago
Is it possible for Cmd+P to work when you don't have the Debugger tab in focus? That one of the few things I miss from Chrome dev tools. Performance-wise it's been running great for me. The hard work you've put into this definitely shows.
everybodyknows 7y ago
To any other devs who like me who want to use Firefox Debugger, but were driven back to the devil Chromium by need for consistent, seamless copy-paste and select-middlemouse interaction: Give 70.0.1 a try. Much, much better. So much that I've dropped Chromium. (Ubuntu 18.04)

kart23 7y ago

Really? I prefer the firefox devtools over chrome. They're pretty similar though.