This is making me really curious because while Chrome is buttery smooth on my Macbook Pro, Firefox 57 is really sluggish, especially when creating/closing tabs. You can literally see the animation stuttering. Other times when a page loads it won't paint for some seconds even if it appears that it has completed loading. Is anyone else having these issues?
I have some similar issues. Sometimes Firefox lags after loading the page (around 1 sec), but eventually works fluently afterwards. It feels like it needs to warm up the engine.
I noticed that disabling "smooth scrolling" in the settings helps with initial scrolling issues.
However, in general I have the feeling that FF57 is faster than before. Could also be that I now focus on the loading times more than usual. A restart of Firefox helped yesterday after the upgrade to 57.
I have a MacBook Pro 2015 and am Firefox user since 1.0 ;-)
The idea of freeing your phone is cute, however, there are some considerable dangers.
* The software that you give access to your phone (be it drivers or the recovery images themselves) isn't signed by anyone. Some of the software isn't even available via HTTPS. I think it's a bad idea to trust some HTTP and unsigned executable more than Google, who are making all they can to ensure the integrity of anything that runs on your phone.
* Unlocking your bootloader is a bad idea. Google erases all your data whenever you unlock your phone[1]. They don't hate you, they've just realized the security issues that come from having an unlocked phone. Take this for example: You're at the airport and ready to leave. However, TSA stops you for a "random" check. They have your phone for about 5 minutes and there's nothing you can do about it. Now, they could ask you for your passcode but then you'd know something's wrong. Now, your bootloader is unlocked, which means they can see your device at firmware level and alter it to their liking it. Nothing can stop them from plating a backdoor in there or just making a copy of all your files and you wouldn't know. That's why Google does [1].
To be more certain that the code I'm about to run was written by the people I trust (by repute) to write non-malicious code.
These guys have built up quite a good reputation, and many people trust them to write useful, non-malicious code. If they did start shipping something iffy, they'd (ideally) quickly lose all of that good reputation, but not before doing quite a lot of harm as people updated. GPG doesn't protect against the authors going rogue, but against someone else maliciously trying to take advantage of this software's good reputation. SSL protects me against a straightforward MITM, but doesn't assert that the server is still under full control of the author and doesn't protect mirrors.
