Live data from Hacker News

Future of Firefox DevTools

paulrouget.com

61–70 of 170 posts

Re: Future of Firefox DevTools

#61
post #35

I find the responses here really strange, has anyone here actually used the devtools in pratice? The firefox devtools seem to me just a awful waste of time from the beginning, they are years behind the competition and the development progress is so slow that I've given up on them. I'm using firefox as my main browser but for web development (dom/css inspection, javascript debugging) there is currently nothing that be…

totally agree with you. FF is really good at making people WOW but I'd really like to see usage numbers.

Re: Future of Firefox DevTools

#63
Making Firebug into an extension that works inside the Firefox dev tools (the same way Firebug plugins can add tabs) sounds like the best way to move forward both Firefox and Firebug.

Re: Future of Firefox DevTools

#64

While the number 1 suggestion sounds great on paper, isn't anyone else concerned about the security implications? The ability for the browser to modify files directly on my workstation outside of caching folders sounds like a recipe for disaster.

He had to click accept connection before it allowed him to edit the CSS.

Re: Future of Firefox DevTools

#66
How about opening up a browser-based API for existing in-browser IDE-like environments to leverage the debugging tools that are already present?

What I am talking about is instead of recreating jsFiddle in the dev tools, how about letting jsFiddle (with appropriate user confirmation) control the dev tools?

As the creator of Plunker (http://beta.plnkr.co/edit/e5iLyQ?p=preview), I would love to be able to leverage the environment that has already been created to allow adding breakpoints and inspecting of running code. Since Plunker already has live-previewing and a working multi-file editing interface, it would be really amazing to be able to take it to the next level.

Shameless plug: If you've never heard of Plunker, check it out. For free you get live-reload of previews, transparent compilation (and sourcemapping) of stuff like Coffee-Script, Typescript, Stylus, etc.., real-time collaboration on the same code, live js/css linting and much more! Also, it is open-source (http://github.com/filearts/).

Re: Future of Firefox DevTools

#67

Earlier quoted context omitted.

Haha, I just switched from Chrome to Firefox because I hate how Chrome prioritizes Google Search over my previous history. It's idiotic. Here, let me show you a clear example. http://i.imgur.com/uNsh7Yv.png Firefox clearly has the superior bar.

I've personally internalized the downdown for going to things I've gone to before. However, I do brand new searches constantly . Often 20+ a day, that often look similar to older searches, but aren't quite. Now, whether I've developed that behavior because of Chrome, or because it works well for me, is a question for itself. Also, since I'm here- anyone get frequent fuckups lately in the Chrome omnibar, not searching…

All the time. I'm not sure how to not activate auto-completion sometimes.

Re: Future of Firefox DevTools

#68
post #63

Making Firebug into an extension that works inside the Firefox dev tools (the same way Firebug plugins can add tabs) sounds like the best way to move forward both Firefox and Firebug.

Why? I say leave Firebug alone, or just kill it already? We don't need two inspectors.

Re: Future of Firefox DevTools

#69
Very excited to see the network panel, as that is what makes me go back to Chrome or Firebug most often.

In the network panel, being able to sorting/filter requests by content-type, request verb, and response code makes it much more usable for me. I didn't see that in the video-- do you plan to include it?

Post reply on HN