Google is stringing bad news after bad news.
Google is stringing bad news after bad news.
I use and love the send to device feature and password syncing (I use FF as my main drive for desktop and mobile), but they are quite slow compared to Chrome. I get it that Chrome is syncing aggressively, which would have been nice in Firefox too, even if it eats up my mobile data.
Chrome web view is also the default web view in Android.
1. The integration with Google Translate, which I understand would be difficult for Firefox to replicate
2. The ability to right-click on an image to search by image, which is probably similarly difficult to add to Firefox. [Edit: Thanks, vatueil, I will give that a try.]
3. How Chrome is less picky about what text it identifies as a url. E.g. If you highlight wpc.ncep.noaa.gov/qpf/day1-2.shtml in Chrome and right-click, you can navigate to that address, but Firefox doesn't realize that it is a url.
However, I only miss these conveniences a couple times a month, so I can live without them.
- Firefox: https://addons.mozilla.org/firefox/addon/image-search-option...
- Chrome: https://chrome.google.com/webstore/detail/image-search-optio...
- Website: https://saucenao.com/tools/
https://addons.mozilla.org/en-US/firefox/addon/imtranslator/
Especially the inline translation feature is very handy if you are learning a foreign language and want to see the texts side by side.
4. no Picture-In-Picture support, and 5. no native trackpad zoom support
The breaking point for me to go back to Chrome a few months back was Mapbox was chewing up SO MUCH MORE resources in FF. As someone who does a lot of GIS dev in Mapbox that was a no-go =/
I have to run a dedicated Win10 box because native Office automation is a huge part of what I do. I've had to go to lengths to get the LTSB (and am working on the LTSC) license because it's the only version of Win10 that's controllable + secure. I also have a 2015 MBP for my Adobe Creative Suite workflow. All of my dev infra is Debian 10. Best tool for the job yo.
I'm not going to bury my head in the sand and use tools that are only 20% performant because "ideals". I'll do my best to switch over (which I did for over a month) and if it's not working out I'm gonna ditch. I have to use Chrome until FF gets on the same level. I'm a startup engineer - I can't afford to neuter my productivity, I have to use the best tool for the job.
Time is money. Period.
Video viewing (as opposed to previewing) really belongs outside the browser anyway.
Using mps-youtube to search, curate, manage, and play lists of videos, without relying on YouTube's server-side management is a real bonus.
Hooking mpv into the stream more smoothly would be useful, and I don't have a good method yet. But given my primary use-case (listening, audio-only), the fact that in the case of video and audio you really can only watch/listen to a single performance at a time, and the fact that in general what's most useful for me is to have a queue of content that I'm going to watch/listen to, in sequence, non-browser tools turn out to be far more useful than browser-based ones.
Most especially when you throw auto-play and advertising into the mix, and find yourself with multiple auto-playing tabs amongst ... well, I'm embarassed to say just how many browser tabs I typically have open, but it's a lot.
WFM. YMMV.
If my split was different I'd feel quite different about it... I just need Hangouts, Mapbox, YouTube, etc to work 100% of the time without headache. Also running two browsers was difficult because it's like "where's that darn tab!!!" half the time ha.
My solution to this crap is to eventually do something like a pihole setup upstream from the browser and call it a day.
But to answer your question: If they are based on the same code, yes. I don't see why you wouldn't.