No marketing involved. The message we are sending is that Firebug 2 doesn't support multi-process (aka 10s) and will stop working as soon as e10s is on by default in Firefox. We do all we can to offer the same functionality in built-in developer tools. See also: https://blog.getfirebug.com/2016/02/08/merging-firebug-into-the-built-in-firefox-developer-tools/
Honza On Thursday, March 24, 2016 at 5:21:23 PM UTC+1, San wrote: > > Regarding the linked discussions... I still don't like the revised message: > "The next version of Firebug will be integrated directly into the Firefox > Developer Tools..." etc. > > As a whole, I find the new description vague and unclear. Do I have some > choice to make? Is Firebug just an optional skin (theme) on the FF dev > tools? If so, is there something I have to do to opt in/opt out? Or is > this just a marketing-ese way of saying that Firebug is, for all practical > purposes, disappearing entirely? > > The original message may have sounded negative/pessimistic (as a couple of > people complained), but I actually preferred it. I don't give a crap about > the marketing psychology of sounding upbeat about the change. I want > clarity -- what does the change really mean, when is it happening, what > choices (if any) do I have to make, that kind of thing. Specifics, not > happy-talk. > <http://Sanstudio.com> > > -- 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 https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/ff26dc13-3986-49e7-948d-ea0e241be41b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
