Live data from Hacker News

It’s time to give Firefox another chance

techcrunch.com

31–40 of 733 posts

Re: It’s time to give Firefox another chance

#31

Am I the only one here who thinks that nothing can beat the Chrome debugger ? Nothing comes even close. It's a different story if you are just browsing, like the 95% or more of the internet consumers.

I agree, the Chrome dev tools feel much faster.

One essential feature for me is being able to pause the debugger and use the mouse selector on DOM elements, which doesn't work in Firefox right now. This is pretty much the only way I know how to inspect and debug popups.

Re: It’s time to give Firefox another chance

#32

Earlier quoted context omitted.

I know the chrome dev tools are also just a web app themselves (or at least for the most part are). I don't know the stack, but I do remember there is a way to open dev tools FOR the dev tools window.

> there is a way to open dev tools FOR the dev tools window I did not know that.

[deleted]

Re: It’s time to give Firefox another chance

#33

Am I the only one here who thinks that nothing can beat the Chrome debugger ? Nothing comes even close. It's a different story if you are just browsing, like the 95% or more of the internet consumers.

While it's true the firefox debugger is lacking in certain areas, it's also better than chrome in others. Debugging CSS animations is much easier in firefox, but firefox lacks a way to look at websocket packets. One thing I like about firefox is that its debugger is a just a React webapp : https://github.com/devtools-html/debugger.html . So it's fairly easy to add to it !

This is in the vein of firebug, the original "developer tools" extension, which was built in the same way: https://getfirebug.com/

Re: It’s time to give Firefox another chance

#35
Switched from Chrome to Nightly as my main browser 2 days ago when KeepassHttpConnector [0] got it's 1.0 release. Speed is absolutely on par with Chrome (which is something I never had in my earlier tries, usually gave FF a chance 2 times per year). Had 1 full browser crash which never happened with Chrome (in recent years), but then I was also running stable vs nightly now.

I'm still missing one extension (Join for Android), but I can live without it for now and might actually just help joaoapps in developing it.

One thing that annoyed me was the large min tab size as I didn't like scrolling tabs. Someone on Reddit pointed me to the right userChrome.css tweak though [1]

Overall I'm pretty happy being back on Firefox after many, many years.

[0]: https://github.com/smorks/keepasshttp-connector/releases

[1]: https://github.com/Timvde/UserChrome-Tweaks/blob/master/tabs...

Re: It’s time to give Firefox another chance

#37
post #17

I wanted to try Firefox, but 2 hours into using it I had a meeting in Google Hangouts. Firefox no longer supports Google Hangouts. Back to Chrome it is.

Yeah, that situation is a mess and should be embarrassing for those involved.

I can use Hangouts for simple messaging from Firefox, but as soon as we need to hop on a call I need to boot up Chrome. Often I forget and try to answer in Firefox just to get the error message. Then I have to start Chrome, login to gmail if it's logged out, wait for everything to load, and then answer the call. Ends up taking a fairly long time to answer an incoming call sometimes.

Re: It’s time to give Firefox another chance

#38
I've been a Chrome user since it was first available. I've tried to go back to Firefox multiple times. When the containers plugin hit the front page a week or two ago I decided to try it out.

I'm not using the beta or nightly builds because I'm lazy. However, Firefox with containers has sold me and I've switched to it for everything except development. I'm too used to Chrome Dev tools it's been hard to switch :|

I absolutely love Firefox+Containers though. I just wish I could make it auto-open-in-container with wildcards. For example, open all *.mywork.com pages in my Work profile.

Re: It’s time to give Firefox another chance

#39

Just switched to Firefox beta to test this out. Looking good so far! The other thing that I've been waiting for is better multi-profile support. You can get a (pre-release) version of that now by opting into the Containers experiment: https://testpilot.firefox.com/experiments/containers

I've been using multiple profiles for months on Firefox via `firefox -P profile1`, `firefox -P profile2`.

What's it changing to, moving forward?

Re: It’s time to give Firefox another chance

#40

The battery usage on MacOS has been atrocious in Firefox 57. Has anyone else had this problem? Am I doing something wrong?

I have plenty of battery issues on MacOS with both Firefox and Chrome. When it's a concern, I try to use Safari. I would probably use it all the time, but it's still awful when it comes to speeding up HTML5 videos (edit: including the latest Safari technology preview). It wasn't all that long ago that it didn't even do pitch correction. Now it does, but it's weirdly tinny and echoey. Firefox and Chrome both handle it fine.
Post reply on HN