4 ms·
Please switch to Firefox, it's better: https://www.mozilla.org/en-US/firefox/new/?redirect_source=firefox-com https://www.mozilla.org/en-US/firefox/new/?redire
by StavrosK 7y ago
Please switch to Firefox, it's better:
https://www.mozilla.org/en-US/firefox/new/?redirect_source=firefox-com https://www.mozilla.org/en-US/firefox/new/?redirect_source=f...
If your favorite feature works slightly worse in Firefox, consider that its interests align with yours, unlike Google's.
- pmlnr 7y agoMaybe it's time for a new firefox ad in the Times. https://blog.mozilla.org/press/2004/12/mozilla-foundation-places-two-page-advocacy-ad-in-the-new-york-times/ https://blog.mozilla.org/press/2004/12/mozilla-foundation-pl...
- garganzol 7y agoFrom the looks of it, Mozilla Inc. is Google's darling. The rarely disclosed amounts in ballpark of tens of millions are being paid by Google on (somewhat) yearly basis. They call it donations but a few people see something else here. For example, when it comes to web standards, those two (Google and Mozilla) act in a good/bad policemen role play. Need to push DRM under the table? No problem. HTTPS? No problem either. Mind you, it's all in the name of a greater security! Hardly anyone can see that it's all come down to Google's evil strain on The Free Web.
- StavrosK 7y ago> The rarely disclosed amounts in ballpark of tens of millions are being paid by Google on (somewhat) yearly basis. They call it donations but a few people see something else here. They don't call it "donations", they call it "payment for having Google as the default search engine". This isn't even news. > Need to push DRM under the table? No problem. HTTPS? No problem either Yeah, God forbid websites deploy TLS. What the hell is this comment?
- snazz 7y agoI’d personally rather have optional DRM and more Firefox users than no DRM and more Chrome users. Encryption decreases the spying power that ISPs have, which can’t be a bad thing.
- garganzol 7y agoPlease consider to take a wider look. Once TLS is everywhere, it's much harder to cut the ads from pages in a centralized fashion. Another point is that data trends and statistics remain exclusively at the hands of a Big Co. Win-win for Google.
- StavrosK 7y agoI'm not sure what you mean. TLS is everywhere now, and uBlock origin works fine. I don't know what you mean about "the hands of a big Co" either. I think you gravely misunderstand how TLS works.
- garganzol 7y agoDon't get me wrong, I'm all in for TLS. But consider this asymmetry: with encryption, all data remains at hands of a Big Co as nobody else can access it. An exclusive access to data at large is a powerful weapon fueling inequality, wars and monopolies.
- StavrosK 7y agoYeah, this doesn't make any sense, I'm sorry. You seem to not know how encryption works, or please go into some detail on why you think this is.
- garganzol 7y agoSimple. TLS ensures data integrity and protects it from eavesdropping. Here is a conversation between Alice and Bob: Alice <-TLS-> Bob In this scheme, only Alice and Bob can know the details of a conversation. Another conversation with Kevin reveals another scheme: Kevin <-TLS-> Bob See the pattern? Both Alice and Kevin shared their information with Bob. Now imagine that Bob is a Big Co. And it has hundreds of millions conversations every day. In this way, Bob is able to gather big data about all the persons he ever talked to. And because TLS only protects data in transit, Bob now has the privilege of an exclusive access to the gathered data en masse. No other person in the world would be able to access it as Bob claims a total ownership on it. What Bob would do with data? It's an open question. One scenario is to build a graph of relations between the persons and then target them with ads. Another scenario is to target all the persons who ever dared to show signs of non-conformity and disagreement and put them to jail. The possibilities are endless and nobody would be able to prove anything because TLS helped Bob to deter all the eavesdroppers. And now he has the ultimate power to rule the world.
- dang 7y agoPlease don't break the site guidelines regardless of how wrong some other comment is. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- radcon 7y agoI had already switched on PC because of Chrome's voracious appetite for RAM. On mobile I made the switch to avoid AMP pages. The list of reasons keeps growing...
- SquareWheel 7y agoIt's not better, but it's still very good. And it's getting better every day. Both Chrome and Firefox are extremely impressive browsers.
- aoeuidiue 7y agoWhile I want to, performance is always an issue and has been for a period of years, 5+ or more. I'm talking my entire system gets taken out for minutes by one pages' shitty javascript. Even then, I'm not even sure if it's the pages fault or a plugin, or firefox itself. Surely I'm not the exception to an application that everyone else seems to have no issue with?
- CJefferson 7y agoHonestly, something is up with your system if that is a regular occurrence in Firefox. Try doing a full reset, delete all your configs and extensions. Then run plain Firefox with no extensions for a while, and see if that behaves well. If not, something serious is up and you should try reporting it to the Firefox bugzilla if you can repeat it. If that works fine, something was up in your config, or extensions. Once I found someone had gone into the internal Firefox config settings and changes something years ago, forgotten it, and it was now causing serious performance problems.
- timw4mail 7y agoExtensions/Addons are also running Javascript, so they can definitely be a factor in how responsive the browser is. Chrome is slightly better at utilizing every computing resource available, but that also means that it is more resource-intensive. Now, every once in a while, I do experience Firefox being unresponsive. Restarting the browser always fixes that, even with the same browsing session. I haven't experienced Firefox locking up the entire system, except with really low resource computers (like Netbooks, or < 4GB of Ram).
- ubermonkey 7y agoThis. I'm on OSX. My primary browser is Safari, but I typically had Chrome running, too. Something pushed me over the edge last year, and I switched to Firefox for exactly this reason. There was a time when FF was lagging badly, but that all seems to be over now.
- ptero 7y agoI personally switched from Chrome to Firefox, but I think we need more well running browsers, not less. Even most well-meaning organizations get many have strange ideas and can use "my way or the highway" liberally when competition does not produce other palatable options. Thus while I did switch I hope Google steps back from this heavy handed approach (and more valid options get developed by other groups and companies). My 2c.
- StavrosK 7y agoWe do need more well-running browsers, which means browsers with roughly equal market share. I'm not comfortable with an 80/20 situation, but even then I'd prefer Firefox to be the 80 instead of Chrome.
- ptero 7y agoI would also prefer an 80/20 split to be in the Firefox favor. However, I do not see that "many well-running" means "roughly equal market share". Browsers are software and thus easy to replicate. And due to the huge market (> 1B users), even 1% market penetration is meaningful -- that is provides enough users to stay alive and develop. Linux, text editors, many email clients, etc. were originally hackers toys, not grandma's tools and as such had a small (but vocal and dedicated) user base that cared about functionality and not market penetration. But once certain functionality threshold has been reached a lot of people were willing to wrap the core in a grandma-style interface. It could work for new browsers, too -- the main threat is not low user base, but being eaten by a large corp once it is capable enough to be a potential threat. My 2c.
- behnamoh 7y agoPlease define "better". I've used both Chrome and FF, and traditionally FF was more aimed at developers and heavy users. However, they lost that advantage over Chrome when their add-ons started to have forward compatibility issues. Speaking of add-ons, I do miss FireBug. It was easy to find/define XPATHs by it (which is critical for web scraping). The new inspect element in FF just lacks that feature. Just how GNU/Linux and macOS are traditionally more appealing to professionals and developers, FF should come to grips with targeting their own niche market. It's interesting how so many great ideas from these "niche" markets (e.g. Unix and Linux in the case of OSs) have surfaced in the more dominant, closed, commercial ones (i.e. Windows). If Mozilla want to really make the web a better place, they should know that by keeping their users happy (who are mostly developers), the ideas they put forth will sooner or later get spread in other browsers as well. As another analogy, you might think about LISP and how the main ideas were later implemented in even the most imperative languages: although Lisp as we knew it is not dominant anymore, the ideas that made it different are still alive in Ruby, JS, etc.
- diegof79 7y agoFirefox is great, and since the Quantum release is getting better on each release. My 2 reasons to keep coming back to Chrome for Mac are the battery life and DevTools. Firefox is very power hungry in macOS, there are a few bugs reported about that (see [1] and related tickets). The best in terms of energy consumption is Safari, but the dev tools are terrible. So each time that I switch my default browser to Firefox or Safari, I end switching back to Chrome a week after for one of those two reasons :( [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 https://bugzilla.mozilla.org/show_bug.cgi?id=1404042
- dylan604 7y agoWhat differences are you seeing in the two dev tools? I use both browsers, and as far as what I’m using the dev tools for, they both give me the info I’m looking to find.
- diegof79 7y agoFeature-wise most of the dev tools are similar across browsers (in particular Firefox and Chome are similar), but the things that keep me coming back to Chrome DevTools are: - Console. Both Safari and Firefox put the input at the bottom so it's like a command line. Chrome puts it at the top, so it feels more like a code editor. It's a small difference, but that combined with auto-complete and the preview of results makes Chrome console better for me. - Editing of CSS properties. Chrome and Firefox are similar in this area, but Safari is terrible (it improved in Safari 12, but it has some interaction annoyances when you edit rules). Since I work doing UX, I do dev mostly for prototyping. Tweaking CSS in the dev tools is something that I do often. - Display of computed CSS properties, Chrome displays the "trail" of a property in the computed view. (Note: I just discovered that Safari added that as an experimental feature in the latest versions). - Source Maps: My experience with source maps was much better in Chrome DevTools. For example, Chrome shows the files mapped by a bundle in the source tree, while Safari shows the bundle and only displays the source map when you hit a breakpoint (if there is a setting for that I couldn't find it). - Accessibility tree is also a great feature of Chrome DevTools. - For small (simple) projects, the ability to link a file system workspace is also great (although useless for projects that use a lot of JS tooling).
- theandrewbailey 7y agoI might be the only person in the world who never stopped using Firefox as a primary browser (since ~2005).
- oftenwrong 7y agoI have used it as my main browser since it was called "Firebird". For me, its pros have always outweighed its cons, even during the long period in which its stability/performance/memory-usage was inferior to its competitors. Some nostalgia: https://upload.wikimedia.org/wikipedia/commons/a/a1/Mozilla_Phoenix_logo_vector.svg https://upload.wikimedia.org/wikipedia/commons/a/a1/Mozilla_...
- deleted 7y ago[deleted]
- cesarb 7y agoI can top that: not only I used it as my main browser while it was still called "Firebird", but I also used as my main browser its predecessor Mozilla back when its version numbers were single-digit "milestones". For those who didn't experience these early versions: they crashed a lot, and opening more than one window (there were no tabs back then) increased the chances of a crash so much that after 2-3 windows having it crash was almost certain. (Before that, I had used Netscape, starting with Netscape 2.)
- jackewiehose 7y agoYou are not. For some reason chrome always felt much more sluggish than firefox (on linux as well as on windows). Maybe it's the kind of websites I visit? I don't know...