zlacker

[parent] [thread] 8 comments
1. system+(OP)[view] [source] 2023-07-18 13:01:52
I used to keep Chrome installed just for the dev tools, but the Firefox dev tools became good enough in probably 2013 or so.
replies(3): >>quickt+V3 >>netule+Ws >>david2+vQ
◧
2. quickt+V3[view] [source] 2023-07-18 13:21:19
>>system+(OP)
Firefox gave birth to the first good dev tools as an extension IIRC
replies(4): >>ttfkam+w4 >>HeckFe+rj >>i_am_j+2T >>LunaSe+cD1
◧◩
3. ttfkam+w4[view] [source] [discussion] 2023-07-18 13:23:44
>>quickt+V3
Yep, Firebug
◧◩
4. HeckFe+rj[view] [source] [discussion] 2023-07-18 14:16:55
>>quickt+V3
A testament to how open its old extension API was.
replies(1): >>asadot+CP1
◧
5. netule+Ws[view] [source] 2023-07-18 14:47:53
>>system+(OP)
I still keep Chrome installed for some sites that are just excruciatingly slow on FF like FoundryVTT and some video sites.
◧
6. david2+vQ[view] [source] 2023-07-18 16:07:37
>>system+(OP)
Chrome’s wasm debugging is much better than firefox’s.
◧◩
7. i_am_j+2T[view] [source] [discussion] 2023-07-18 16:15:33
>>quickt+V3
You're definitely right.

I'll go even further; As I remember it Chrome Dev Tools pretty much copied Firebug's homework in terms of UI and feature set.

◧◩
8. LunaSe+cD1[view] [source] [discussion] 2023-07-18 19:11:24
>>quickt+V3
And then completely lost the plot and has been behind Chrome for the last ten years.
◧◩◪
9. asadot+CP1[view] [source] [discussion] 2023-07-18 20:17:15
>>HeckFe+rj
The Firefox extension API (which wasn't an API really at all when it was first used) was created to support cases like the DOM Inspector and others which abused Mozilla's XPInstall and XUL overlays (both created for other purposes) to invent extensions. The same people that created the APIs were the same people building those extensions (see Joe Hewitt for Firefox and DOMI and later Firebug.)
[go to top]