Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox? • Hacker News Board

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#31

Post by gverri » Tue, Mar 05, 2013, 5:03 PM UTC

What about some "livereload" capabilities?

http://livereload.com/

I know a lot of people who use it. And I think it would be great to have it native on firefox.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#32

Post by timme » Tue, Mar 05, 2013, 5:03 PM UTC

Make the native 'Inspector' tool go away. Accidentally opening that thing (because they're next to each other in the context menu and the labels are similar) instead of Firebug is infuriating.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#33

Post by drivingmenuts » Tue, Mar 05, 2013, 5:04 PM UTC

I would say make Firefox as light and fast as possible by keeping ALL developer tools as addons. Most users aren't going to need them at all, so it's just eating up space for no reason.

I personally prefer Firebug over Inspector, so I would rather see you throw more resources into integrating it fully with FF.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#34

Post by pwnna » Tue, Mar 05, 2013, 5:05 PM UTC

I find that firebug slows down the browser after a while of debugging. Memory leak? Make it faster :)

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#35

Post by goldfeld » Tue, Mar 05, 2013, 5:07 PM UTC

I'd love vi keybindings to navigate the console and web inspector.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#36

Post by paulrouget » Tue, Mar 05, 2013, 5:08 PM UTC

yesimahuman wrote: post #29

I think I'm just used to the WebKit dev tools, but I find it requires more work to get to the Script tools, etc in Firefox than Chrome. For example, in FF I have to go to Tools -> Web Developer -> Debugger to get to the debugger. I can't just get there by doing "Inspect Element". I'd like to see all the tools combined into one mode and allow me to pop it out into a new window. If I can do that right now, it's just no…

All you said has been implemented in Firefox Aurora.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#37

Post by vinhboy » Tue, Mar 05, 2013, 5:08 PM UTC

drivingmenuts wrote: post #33

I would say make Firefox as light and fast as possible by keeping ALL developer tools as addons. Most users aren't going to need them at all, so it's just eating up space for no reason. I personally prefer Firebug over Inspector, so I would rather see you throw more resources into integrating it fully with FF.

That new Inspector thing is really annoying. I always accidentally open it instead of Firebug. From a developer stand point, Firebug stills beat all other browser dev-tools by a mile and is the main reason I still have Firefox on my dashboard.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#38

Post by nkron » Tue, Mar 05, 2013, 5:09 PM UTC

I would love to an allocation profiler that reports garbage. .Net has the CLRProfiler which tracks allocations over time and can show where you are creating a lot of temporary allocations. CLRProfiler is a great tool and I haven't found anything like it in the web world yet.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#39

Post by mehrzad » Tue, Mar 05, 2013, 5:09 PM UTC

JoeCortopassi wrote: post #3

Honestly, the absolute best thing you could do for any dev, is lighten the footprint FF currently has on my ram, and continue to improve the api for add-ons/plugins. The more stable, extensible and fast FireFox is, the more useful I will find it for development. But if more kludge is added to it, and it continues to get slower/bigger, the less likely I am to continue to use it, regardless of what amazing plugins are…

I thought that the latest browser tests showed that FF used less ram than Chrome. http://lifehacker.com/5976082/browser-speed-tests-chrome-24-...

Unfortunately, reputations stick.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#40

Post by rebelde » Tue, Mar 05, 2013, 5:09 PM UTC

Maybe this is provided and I haven't found it yet: - Rendering speed - show what slows it and what we can do to improve it. (Too many DOM objects, external files, redrawing?).

Thanks!