Honestly given the direction and choices that Mozilla's team has been 
making in the past that very well could more intentional than it is 
accidental


The new "Firebug 3.0" is NOT Firebug. It is The failed web tools that 
Mozilla has been working on for 2-4 years that still are failing being 
given Firebug's name. 

Firebug 2.0.7 is the Last version of "Firebug" 

I see it sort of as Windows XP/7 versus Windows 8/9 or Office 2010 versus 
2013. Every interface dumbed down. All important/power user features 
removed or requires a ton of clicks (and then eventually removed because 
metrics says nobody was using that feature). Every interface made as 
inaccessible as possible (copy paste must go in all these UX). Interface 
and icons have as much colors/definition removed as possible. In the case 
of Firebug 3.0 I thought the Dark Grey Text against Black background was 
rather amusing (and unusable). 


On Wednesday, January 28, 2015 at 8:22:46 AM UTC-6, Richard Muse wrote:
>
> I appreciate your response. I would like to note a few things to make sure 
> they do not slip through the cracks.
>
> Someone at Mozilla is messing up your time table as the beta version of 
> FireFox will not run FireBug 2.0.7. Or if it can, but a setting needs 
> flipped, it would be appreciated if someone could point this out. (I got 
> the latest beta release this morning, beta 4, to test.)
>
>
>
> As before, holding optimism that all will work out, but the time tables 
> are dimming that hope.
>
>
> On Wednesday, January 28, 2015 at 2:13:15 AM UTC-5, Jan Honza Odvarko 
> wrote:
>>
>> A few notes from this thread to mention:
>>
>> > I much prefer Firebug and its interface to the built-in Firefox dev 
>> tools.
>>
>> > The new Firebug 3 is very clumsy and is missing pretty much all of the 
>> features that have made
>> > Firebug an invaluable web development tool.
>>
>> > The Nifty and better thought out UX/UI/Tools of Firebug of lore is THE 
>> THING that set Firebug
>> > apart from all other developer tools. 
>>
>> > If anyone wants to get ideas about how to improve the Firefox dev 
>> tools, they just have to open
>> > Firebug, look at each tab, check the options, look at the context menu, 
>> etc...
>>
>> etc.
>>
>> Here is my response:
>>
>> 1. I understand all the complaints in this thread and our project goals 
>> are set precisely to answer them.
>> 2. Yes, Firebug 3 is not ready yet (it's in alpha phase) and we (FWG) are 
>> working hard to move closer to what Firebug 2 is. And yes we need more time.
>> 3. We all (FWG + Mozilla) know about Firebug 2 UI/UX advantages and the 
>> goal is to integrate them either directly to devtools or to Firebug 3.
>> 4. To be fair, native devtools have also some advantages (e.g. stability, 
>> small memory footprint, security, e10s support, remotability, etc.), so 
>> taking the best from both tools and build one that is the best is the right 
>> goal.
>> 5. It's important to understand that FWG is pretty small, 1 full time dev 
>> (me, the team leader) and a few contributors, so work is not going forward 
>> as fast as you would perhaps expect.
>> 6. I have to mention that Firebug is an open source and even if I 
>> understand that everyone in this thread is probably already overloaded by 
>> work, we appreciate contributions.
>> 7. It isn't feasible to continue with Firebug as separate full feature 
>> in-browser development tool. An effective strategy is cooperation with the 
>> devtools team and bring back Firebug 2 UI/UX.
>> 8. No Firebug 3 isn't offshored to an Indian company (please be friendly, 
>> this kind of comments could be offending).
>>
>> Honza
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/8fa4eead-0085-4cb3-81fa-ba33ec8a7565%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to