I can understand your frustration, though complaining here in the Firebug discussion group doesn't help to improve the situation. If you want to help, you should file bugs for the things that don't work as expected (if they are not already filed).
Sebastian On Thursday, December 8, 2016 at 12:51:09 PM UTC+1, pd wrote: > > I completely relate to your surprise, even though I haven't been 'away'. > What is happening to Firebug is a travesty. Someone else in this thread > suggesting "most devs have moved to Chrome" is a massive generalization > that isn't backed up by any evidence. However who could blame them? Mozilla > unfortunately makes a lot of very bizarre decisions. Choosing to build a > whole new set of developer tools has been one of their worst. The logic > must have seemed sound: Firebug is limited architecturally, isn't native, > and wouldn't be able to support e10s etc. Or at least, that was the claim. > But really, what has happened is we now have two different options for devs > in Firefox, *and neither of them is adequate*. That's right, NEITHER! The > development of the new/native tools have been piecemeal and far too slow. > The freeze on Firebug development has meant it has not grown either. So now > we've both tools that are inadequate yet Firefox is supposed to be the > biggest champion of the open web ... the only browser developer that > doesn't have a huge other agenda. > > Right now, it would seem that Firebug no longer even detects JS in web > pages! I could be wrong but the main aspect of my setup that has changed > lately is Firefox has been updated, but it appears Firebug has not, since > October? > > The sensible approach would have been to have some devs replicating the UI > and functionality of Firebug, another to expand upon it's functionality, > when Mozilla was developing the new/native version. Instead .. years down > the track ... we have a mismatch of new and are missing simple, but very > helpful, old Firebug features. This is hugely disappointing. Firebug was/is > that good, there was no need to write an alternative add-on to give users > choice. Then along comes Mozilla, kills Firebug and now we have no choice > but to adopt the inferior new/native tools. > > In what other industry is there no real competition for providing > professionals with the tools they depend on? Do mechanics not have a choice > between Sidchrome and other toolmakers? Do medical professionals not have a > plethora of choice for equipment providers? The list would be long. Only in > IT must we be forced to use substandard tools if we want to support / use > Firefox. Chrome devtools is not an option either. They give new meaning to > 'clunky' ... how could they not being based in/on webshit? > > On Tuesday, December 6, 2016 at 9:41:37 PM UTC+11, Glen Hong wrote: >> >> It feels like I've just found out my Mother is dead but in actual fact >> she died month's ago?? >> >> All of a sudden my Firebug is different. I can just make out that >> somewhere down the line there has been an integration to the Firefox native >> development tools. I've started scouring the internet but to my surprise >> there is barely nothing to be said?! I can see on the Firebug home page >> that they have stated that is the case but I cant find anywhere what >> happened and why? >> >> In my view and I'm sure for a lot of developers out there Firefox is/was >> the number one debugging environment by far. With all the support I just >> can't believe that there have been no blog posts nothing explaining what is >> going on. Did the guy just get jack of it and decided to call it quits? >> Why was there no kickstarter page started if money was an issue Im sure the >> guy could've raised enough to keep going? >> >> Pardon the ignorance but like I said there is just nothing on the >> internet that I can find. If someone can take the time to explain or post >> me some links as to what is going on. Im still living in hope that this is >> a joke and things will kick off again? >> >> Thanks for any insight someone may give me!! >> > -- 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 firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/d291fc1b-558e-46cf-b0fa-ad5a1f620d1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
