Live data from Hacker News

Choose Firefox Now, or Later You Won't Get a Choice (2014)

robert.ocallahan.org

101–110 of 343 posts

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#101
post #44
post #27

Earlier quoted context omitted.

Yes. I like Pocket, but I can't see why it shouldn't be an extension that can be removed.

Intellectually, I agree, but - it actually doesn't hurt; - market research indicates that most people actually love it.

Neither does RSS. Forgive me if I'm wrong, but isn't Pocket developed outside of the main Mozilla tree?

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#103
post #94

Earlier quoted context omitted.

> As frustrating as that is, perhaps if more iOS users picked firefox as their "browser" then maybe Apple would take a hint and open up allowing other rendering engines. Although I'm not holding my breath. The problem with this is that allowing other rendering engines would open up a whole can of worms that Apple would rather not have to deal with, and there's no easy way, even if Apple wanted it, to allow JIT execut…

What design choices mean third party Android browsers can do JIT but third party iPhone ones can't?

Android doesn't do codesigning, at least in the way that iOS does: on iOS, all code that executes must be signed and approved by Apple before it is allowed to be loaded by the OS into memory (with some exceptions e.g. Safari). JIT gets around this because applications can now generate and execute arbitrary code, which is obviously something that Apple doesn't want. So this basically means that you are not allowed to put apps like this on the App Store.

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#104
I was very afraid about syncing my data with other devices on Firefox. But today I switched to Firefox and passed all my chrome data (even stored passwords) to Firefox. It can sync with all devices such as mobile. I hope I will not get trouble about web apps :P

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#105
post #9

Just so we can avoid rehashing the discussion whenever a post encouraging the use of Firefox is posted. - Yes, Mozilla is still the better browser when it comes to privacy. - Yes, Mozilla has made missteps with Pocket and Mr. Robot. - Yes, it is slow/resource heavy on certain Macs with non-default resolutions. Yes, Mozilla is working on a fix. - Yes, it has become really fast for most users after Quantum improvements…

Chrome has better security unless you want to keep yourself secure from prying by Google.

Ungoogled-chromium exists you know..

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#106

Earlier quoted context omitted.

A browser written in Rust (which is probably Firefox's long term goal) should blow Chrome out of the water in terms of security, despite the massive efforts invested in that regard by Google to prop up Chrome's C++ code base.

Would it really though? Sure, there are definitely things about Rust that make coding more secure, but surely that it only one part of security?

Definitely, it prevents the buffer overflow style of exploits but there’s also a lot of leaks in how all the DOM objects interact.

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#107
post #73

Earlier quoted context omitted.

Pocket is also easy to implement as an extension. In fact, it is an extension. But they bundled it with the browser.

It's their own service.

It wasn't when they first did it.

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#108
post #34

Back in 2014 I was using g Firefox, for precisely this reason. I am still using it today, for the same reason. Please stop creating web applications that only work with Chrome (or Chrome and Safari).

not only that but stop testing your frontend code only on chrome. i'm the only one on my team that uses a non-chrome browser and every once in a while i find a bug or a css issue that is non-chrome only because nobody tests outside chrome.

Re: Choose Firefox Now, or Later You Won't Get a Choice (2014)

#109

Earlier quoted context omitted.

A browser written in Rust (which is probably Firefox's long term goal) should blow Chrome out of the water in terms of security, despite the massive efforts invested in that regard by Google to prop up Chrome's C++ code base.

Would it really though? Sure, there are definitely things about Rust that make coding more secure, but surely that it only one part of security?

Indeed, that's only one part of security. But it's a pretty big one!
Post reply on HN