31–40 of 101 posts
I develop, test, and debug on browsers that my users are using, and that ain't Firefox.
Are you comfortable handing Google the power to dictate the future of the Internet?
Why isn't there an API for writing devtools, so that we can have some more competition in this space?
We need less API/standard, not more. To have more competition in web devtools, we need to simplify the web standard so more browser can appear instead of forcing some new fancy API on our almost monopoly.
There are also a bunch of things that keeps me with FF. multi container tabs is one of my most loved ones. But I simply don’t get why the Team does make that feature even better. Like making it much easier to distinguish which container tab I am in. And adding even more customisability pr container-type.
Regarding DevTools, I really do t think I have a strong preference at all. But the stronger/more consistent performance the DevTools in chromium comes out slightly ahead.
For me it’s the overall experience which makes it a close race
Earlier quoted context omitted.
We need less API/standard, not more. To have more competition in web devtools, we need to simplify the web standard so more browser can appear instead of forcing some new fancy API on our almost monopoly.
This isn't how anything works. If you want a better alternative compiler, you build a new compiler. You don't build an entirely new operating system that includes a new compiler. Want a better grep? Make a better grep, not a whole new shell. Forcing everybody to make their own entire browser in order to provide an alternative devtool is ... madness? What does making a devtool have to do with making a browser? Why sho…
Making the implementation of the web standard simpler means increasing the options available, meaning more chance of finding a devtools you appreciate and possibly modify.
APIs/Standards deprecate. It is not even a question of "if" but "when". Lowering the barrier of entry is much more sustainable than engineering a whole new spec every time we encounter a problem.
I develop, test, and debug on browsers that my users are using, and that ain't Firefox.
Of course, Firefox users may just skip your sites because they don't work in FF...
For some reason, new Firefox windows can only be launched from the same environment from which the first window has been started. Even the same user who started FF cannot launch a new window from a new shell. That constantly interferes with my workflow. Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal: su desktopuser firefox It does not wo…
Depending on your use case Docker may be a solution.
Earlier quoted context omitted.
Of course, Firefox users may just skip your sites because they don't work in FF...
Developing in Chrome doesn’t mean the end result doesn’t work in Firefox. Web standards are there for a reason. I develop in Chrome (by develop I mean the full interactive development cycle) but also check in Firefox and Safari once in a while. This post is explicitly about why people use Chrome’s devtools, so you’re just attacking a strawman.
Editing to not extend the thread: the comment says they do NOT test on anything than Chrome. You maybe do that, the top comment author doesn't.
Earlier quoted context omitted.
Browsers are so similar these days, web standards are so well defined, I see little reason to code Chrome-only sites. Having been through the IEs of the 90s/00s, I feel proud that we managed to scape what seemed an irreversible fate and a sense of responsibility to do whatever I can to help prevent it from happening again.
Try to use WebUSB or WebGPU on Firefox.
Why isn't there an API for writing devtools, so that we can have some more competition in this space?