661–670 of 679 posts
Earlier quoted context omitted.
Looks like you don't know about chrome://flags/
The thing is, flags in Chrome exist only until Google decides it shouldn't be an option anymore. Then they take the choice away from you. I disabled the material "design" styled themes for as long as I could, until the flag disappeared.
Earlier quoted context omitted.
Or when they silently installed an extension in order to send telemetry from Firefox installations that had explicitly opted out of telemetry. https://www.ghacks.net/2018/09/21/mozilla-wants-to-estimate-...
The reason this is outrageous is because they weren't doing this kind of thing before. The reason this isn't outrageous when Chrome does it is that Chrome always does this. Using this as a reason to distrust Firefox and instead trust Chrome is insane. It's valid criticism but seeing this presented in arguments about why Firefox is bad (and you should be using Chrome instead) is absurd.
Earlier quoted context omitted.
I think Servo is going to be a massive Good Thing (tm) for Mozilla, but they have messed up a few times with UI anti-patterns and sneaking extensions into updates that users didn't opt for. They have seriously breached our trust like Google and it will take years to earn back that trust. I switched to Firefox away from Chrome recently. I am happy with this but I wish they had a friendly UI you could bring up to expos…
> I can't hide the tab bar at the top as far as I know. It could be easier, but still doable in 5 minutes (that's how long it took me) with some CSS, see https://github.com/piroor/treestyletab/wiki/Code-snippets-fo... on how to do it. There seem to be some security concern or it's not so easy UX wise, see https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 for all the discussions and progress.
Earlier quoted context omitted.
I've found VS Code to be approximately unusably slow in a virtual machine (Linux guest, Windows host) but VS Code runs fine on the host. Other editors run just fine in my Linux VMs- Sublime Text has no problem at all.
Probably a lack of hardware acceleration on the virtual machine.
That said, it's clearly possible to build a nice editor purely on the CPU, so it's a shame that VS Code can't run well in the same environment. Sublime Text handles dozens of tabs and windows under emulation.
Earlier quoted context omitted.
And the Mozilla Corporation is a 100% subsidiary of the non-profit Mozilla Foundation. That means their only stakeholder that they could pay out their profits to, is the Foundation, which can't take the money, because it's a non-profit. The Corporation can only really save up the money to reinvest it later. The Mozilla Foundation's legally-binding mission statement is therefore also effectively enforced for the Corpo…
That's an excellent explanation. A small correction: if I recall correctly, the Corporation is legally allowed to give some money to the Foundation, and it does so. But the allowed amount is quite small -- maybe a couple a million a year? I don't remember exactly -- and only a tiny fraction of the Corporation's profits.
Earlier quoted context omitted.
I know about ~100 Firefox developers with Macbooks and none of them experiences the issue, so that's probably harder to reproduce. Would you be interested in help to profile the issue and file a detailed bug? This would help fix it.
Off course. I would really like to ditch Chrome once and for all. What i don't get is that it's an unknown problem, many people have already filed bug reports on the tracker: https://news.ycombinator.com/item?id=18626325 (also see several blog posts like: https://www.kamshin.com/2018/07/firefox-on-macos-insane-batt... ) I think it has to do with running the Macbook Pro at scaled resolution which is pretty much standa…
Do I understand correctly that you're checking CPU usage immediately after having scrolled up/down, or while scrolling up/down, right?
Apparently, there are already people working on that bug. If I understand things correctly, Firefox uses transparent windows, but transparent windows use lots of CPU on some macOS configurations, and this somehow wasn't detected during testing (I imagine that the computers used for testing didn't have these configurations).
If this is the same bug, as is likely, the bug is identified and developers are working on it: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 . If you wish, you may leave a message on that bug mentioning that you are available for profiling and testing a fix.
It is my impression (but don't take my word on it) that the fix will ship in Firefox 65, which is currently in Nightly. Now, I'm not sure that the fix has already landed in the current Nightlies, but do you have the possibility of testing on Firefox Nightly if the problem is still present?
(usual caveat: Nightly has Telemetry activated by default – if you don't like Telemetry, don't forget to disable it)
Earlier quoted context omitted.
I know about ~100 Firefox developers with Macbooks and none of them experiences the issue, so that's probably harder to reproduce. Would you be interested in help to profile the issue and file a detailed bug? This would help fix it.
I’m seeing the same behavior on my Mac. Linux is fine. I’d be happy to help / run profiling / whatever. Contact should be in my profile.
Apparently, the bug is already identified, so this might not be necessary. More details in my answer here: https://news.ycombinator.com/item?id=18634165 .
If you wish, you may leave a message on https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 mentioning that you are available for profiling and testing a fix.
Earlier quoted context omitted.
Everyone seems to be missing that this is Microsoft’s tacit recognition that Electron is the future of apps. Electron has abysmal performance and doesn’t work on ARM. This is them fixing fundamental chromium issues, to improve Electron performance and give themselves a further wedge beyond TypeScript
Look at VS Code: Electron doesn't have abysmal performance. It's just what people do with it that causes problems.
Earlier quoted context omitted.
The best thing about Firefox is Mozilla's Multi-Account Container tabs[0]. Essentially it allows you to put different tabs into different light-weight profiles, with their own session, cookies, and state. That means if you want to log into Facebook but don't want Facebook following you online, just give Facebook its own container. Mozilla has anti-tracking already baked in, but Multi-Account Containers are a whole ot…
Containers are such a great idea. My one wish is if you could set a default container. I use FF to browser Facebook primarily and want that to be default, but instead I have to load Firefox then load a container then load Facebook. Wish it were just open FF -> Facebook is homepage.
Mozilla. What a great, open and free place, where you can't write your opinion under articles.