Of course, this all sucks huge balls for those of us who used Firebug in
SeaMonkey. But whatever, you don't care about us. Thanks a lot.
--
Best regards,
Jeremy Morton (Jez)
On 04/02/2015 18:06, Jan Honza Odvarko wrote:
Some more comments to this thread.
I believe I understand most of the complaints and comments in this
thread and I can assure you that we are (FWG and yes even Mozilla)
listening to your feedback. I am personally involved in the Firebug
project since 2007 and I am quite familiar with the whole thing. Not
only with the code base, but also with various planning and strategies
we have been through over the years.
Firebug in its current incarnation (i.e. Firebug 2) doesn't have any
bright future (and believe me I belong among those who'd love to see
it!). The architecture isn't ready for multi-process browser (aka e10s)
and FWG is definitely not strong enough to refactor it. It would be
enormous pile of work (estimated as several years of work by one of the
FWG member). It's not something we want to spent time on - that would
mean ignore built-in tools in Firefox and duplicate the existing
platform. If you don't agree, do it yourselves. It's an open source
after all.
Yes, Mozilla could base built-in tools on Firebug, but it didn't happen
(I wasn't there personally when the decision has been made). Perhaps,
sometimes it's just better to start over (it isn't an exception in the
software world). But, this isn't even that important, the important
thing is to make sure that Firefox has great developer tools - yes, even
better than Firebug is now.
I agree that it still isn't the current situation - the more is
important to work on one tool (and not spread energy on two independent
tools). That's why we decided to move on and (re) build the next
generation of Firebug on top of the built-in tools. There is good
platform and bad UX and UX is exactly the thing where Firebug (team) can
jump in and bring experience. Some features can be part of Firebug 3 and
some can be implemented as built-in features for everyone's benefit.
Some features can be developed as Firebug 3 features and if accepted
well by the community of web-developers, we can make them built-in.
We are at a spot where we need to take this path. That's the best we can do.
If you want to be productive - point out concrete ideas. What specific
features are you missing and what new features you'd like to have. File
bugs [1]
One of the most commented missing features in Firebug 3 has been XHR
debugging/logging.
And yes again, we are listening, it's now in Firebug 3
(check out alpha 8)
https://github.com/firebug/firebug.next/releases/tag/firebug-3.0.0-alpha.8
(if sucessfull, it can become native feature)
What should be the next?
Honza
(Firebug team leader)
[1] https://github.com/firebug/firebug.next/issues
--
You received this message because you are subscribed to a topic in the
Google Groups "Firebug" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/firebug/9nWmTvZv6lw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[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/c5b43ea5-50ea-4647-9160-28803264223e%40googlegroups.com
<https://groups.google.com/d/msgid/firebug/c5b43ea5-50ea-4647-9160-28803264223e%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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/54D2643B.9010405%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
