Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Switch from Chrome to Firefox

mozilla.org

Post reply on HN
Print view View original

491–500 of 1001 posts

Re: Switch from Chrome to Firefox

#491

Post by SilasX »

staticassertion wrote: post #446
SilasX wrote: post #353

Earlier quoted context omitted.

No, there wasn't. No malware was being spread en masse this way. It was an entirely fictitious threat, as it would have required convincing the user to enter a confusing part of the app (about:config) and correctly change a setting. I can accept that there might have been a malware problem when signatures weren't the default requirement, but that's not the change I'm talking about, where they ignore a user's explicit…

Hi I work on a security team that hunts for malware. Malicious extensions are a huge threat - totally happens for Chrome in particular, and I've even seen malware package old versions of browsers to get around the modern defenses.

Someone distributing a different product to get around you current products vulnerabilities is outside this threat model.

Re: Switch from Chrome to Firefox

#492

Post by folkrav »

mook wrote: post #265
fencepost wrote: post #104

Earlier quoted context omitted.

I really wish that if Microsoft was going to abandon having their own engine that they'd gone to Mozilla instead.

They really can't, though. There's a pile of corpses of people who tried to embed Gecko, because it turns out Netscape/Mozilla is really bad at keeping a stable ABI. I doubt anybody remembers K-meleon anymore, for example. As far as I know Servo was supposed to be the new, embeddable engine, but that's mostly cancelled now and the Rust bits are just being rolled into Gecko (via Project Quantum). I believe that's why…

> Servo was supposed to be the new, embeddable engine, but that's mostly cancelled now

You mean the plan to embed Servo, or Servo itself?

Re: Switch from Chrome to Firefox

#493

Post by Histrionic »

asenna wrote: post #233
intothev01d wrote: post #20

I switched a couple of months ago because Chrome is just a bloated piece of garbage. One of my favorite features in Firefox is containers, which I used to have different users for in Chrome. Maybe Chrome has something similar now but it's one of the things I liked when I switched over. Haven't had any issues so far, glad I did

> One of my favorite features in Firefox is containers I switched a couple months ago from Chrome to Firefox as well but to tell you the truth, I just heard about containers and what you could do with it. I guess I must've been living under a rock, this is amazing! I was already glad I made the switch for the less resources being used on my aging Macbook Pro and better privacy features, but containers just took this…

[dead]

Re: Switch from Chrome to Firefox

#494

Post by teh_klev »

BlueTemplar wrote: post #425
teh_klev wrote: post #378

Earlier quoted context omitted.

I'll bite, tell me (I already know they were acquired by Microsoft)....?

Do you think that Microsoft is just doing it out of the goodness of their hearts? And that Open Source, but especially Libre Software, is going to be compatible with whatever they have in mind ?

What have they done to GitHub that's been an act of Embrace, Extend, Extinguish? Pretty sure I'd hear it here on HN first if it was a thing. Honestly I need some evidence.

Re: Switch from Chrome to Firefox

#495

Post by chris_wot »

WorldMaker wrote: post #235
worble wrote: post #198

Earlier quoted context omitted.

How strange, this is the first I've heard of this. I've never had to touch source maps config in my webpack and it's always shown fine in Firefox. Is it just specific circumstances/specific code patterns that have source map problems in Firefox? Or is it when it's transpiling from TypeScript or JSX or something?

From what I've investigated so far, webpack likes to use the webpack:// pseudo-protocol for file references in most of its Source Map modes, including its defaults, and from what I've seen that seems to be the single biggest issue of cross-browser Source Map compatibility in the webpack ecosystem (other ecosystems have different problems). Chrome seems to be able to figure things out from the pseudo-protocol in just…

Do you know if there is a Mozilla bug for this?

Re: Switch from Chrome to Firefox

#496

Post by inyorgroove »

JoshMnem wrote: post #471
inyorgroove wrote: post #455

Earlier quoted context omitted.

Slightly better still not there. If I have 15 search providers I have to press TAB 15 times to get to the last one, that is tiresome. I can search amazon/ebay/npm/rubygems/mdn/etc without looking at the screen or keyboard with chrome. I have probably >10 search engines I use daily.

You can set custom keywords that are the same as on Chrome. You just won't need to press TAB. I don't use that feature, but it's described here: http://kb.mozillazine.org/Using_keyword_searches I didn't think about adding sites like rubygems and mdn, but that's a good idea. Edit: I just tried it and it works. Example: create a bookmark in Firefox and change the URL to the one below. Set the keyword to "r" in the book…

I guess I just need to choose better "keywords"

Re: Switch from Chrome to Firefox

#498

Post by asadotzler »

PascLeRasc wrote: post #442

I really want to switch to Firefox. I don't need it to be better-performing than Chrome on my work PC or Safari on my home machine - I want to support free software. But Firefox's text just looks bad, like really bad. On both a retina Mac screen and 24" 1080p monitors on Windows at work, the fonts look pixelated and blurry, like there's something around the edges of the characters. Contrast seems off too, much lower…

Can you share some screenshots? IMO, text looks somewhat better in Firefox than in other browsers.

Re: Switch from Chrome to Firefox

#499

Post by ebertucc »

ethanpil wrote: post #102

I wish MIcrosoft would have worked off Firefox for the new Edge instead of Chrome. Just doesn't make sense why they would feed into a direct competitor. Bagging Edge off Firefox would have made it a real option for me as well as creating an opportunity now with all the ad blocking stuff going down...

I'm just going to copy pattpass' response to a similar comment here, because the decision to use Chromium makes more sense with this context:

What benefit does Microsoft have by using Mozilla instead? Earnest question.

Electron, the software framework VSCode uses, runs on Chromium. Github maintained and developed the framework and they are currently owned by Microsoft. If Microsoft contributes to Chromium and improves performance they benefit in a lot of places: their new browser is improved(Edge Chromium), their own framework(Electron), and their own product (VSCode).

Re: Switch from Chrome to Firefox

#500

Post by SilasX »

MrRadar wrote: post #456
SilasX wrote: post #445

Earlier quoted context omitted.

>I'm referring to native malware abusing admin privileges to install extensions without the user's consent, not users deliberately installing malware extensions themselves. Ah, so a vector that required code signing doesn't protect against.

Signatures absolutely do protect the user in this scenario. With mandatory signatures you can't get (obvious) malware into the browser without having it first approved by Mozilla (who should reject it upon review).

Okay I misunderstood what you meant by native malware.

But if your threat model is that extensions can be added without the user's consent, then that is the vulnerability you should fix. And it still wouldn't justify blocking a user who is aware of the risk and chooses to disable that layer of default protection.

Post reply on HN