431–440 of 713 posts
Long live Rust! :)
Earlier quoted context omitted.
and this is where Chrome has a good hook on me. In order to switch, both FF desktop and mobile need to be better than Chrome. Does FF support a version of Chrome tabs too ? Damn, they have built themselves a good moat just with features I will miss.
I prefer FF over Chrome on mobile. FF mobile allows extensions such as uBlock Origin and Google Link Fixer which I find essential. FF supports sending tabs to other devices, if that's what you mean by Chrome tabs.
Earlier quoted context omitted.
Performance is usually death by a thousand cuts, and (imo) the best way of mitigating this is by standardizing some measurements and making that automated. Block changes that move performance past this bar, make sure the organization buys off on this approach. Any changes to a critical area that impact performance need to be zero-sum - if you add something, you need to take something away.
The cost of doing this in a large organization seem high though. Are there good ways to solve problems like this: - A newbie developer adds small feature, triggering some performance test that was already close to failing. Now newbie has to learn all about the performance of this large project before they can land their first change. - The performance test has a reasonable amount of noise. At first, 10% of test runs…
This is a tricky thing to deal with - (imo, again) how you deal with this is twofold:
1.) The automated test that measures performance needs to be rock solid - whatever you measure needs to be deterministic. Wall-clock time isn't always the way to go (although it's the easiest), maybe you profile and measure cpu cycles consumed by your application.
2.) If you capture performance over time then hopefully you can capture a trend-line that shows performance degrading from other changes that push the app past the performance bar. If your dev loop is fast enough you can isolate performance degradations to a small set of changes. Ideally if you handle #1 above this won't be much of an issue. In my experience changes that tank performance usually do so beyond the threshold of noise.
Regarding "newbie developer needs to learn all about performance" and "asking developers to delete code", that's why you need organizational buy-off. If your changes are regressing performance in a core area that is complex with a lot of legacy, maybe you shouldn't be making changes there, or the org needs to be aware of and sign off on letting your change go through. It doesn't always need to be a hard and fast "reject all changes", but there needs to be a discussion.
I can still remember: * that moment I was overjoyed to use Lynx over dialup in South India back in the mid-90s allowing me to browse the World Wide Web! * ...And then that moment being surpassed when I wet myself running the Netscape "GUI browser" on Windows 95 using a brilliant hack by a pair of brothers I knew that wrote a winsock.dll shim on top of Lynx over dialup (called Blue Laser; those guys went on to become…
Earlier quoted context omitted.
I prefer FF over Chrome on mobile. FF mobile allows extensions such as uBlock Origin and Google Link Fixer which I find essential. FF supports sending tabs to other devices, if that's what you mean by Chrome tabs.
Firefox on Android has awful scrolling physics. I will never be able to use it while the scrolling is different to every other app on my phone.
Firefox lost its biggest use case.. The extensions. Besides, the new version is similar to Chrome in memory usage for multiple tabs which is HUGE disappointment.
The extension ecosystem is great right now. A few high profile extensions aren't being ported but there are a lot of cool new extensions popping up and it's never been easier to port between browsers.
On html5test.com, FF56 scores 478 (on my windows 7 machine). Does FF57 increase compliance at all, or is this purely a performance boost?
FF57 gives me 483
I switched back to Firefox 54 from Chrome when multiprocess browsing ("Electrolysis") came out of beta. It's been absolutely great. It's fast and I trust and like the nonprofit behind it. And all the extensions I care about are available. My main issue with Chrome was the endless nags to sign in to a Google account, and just generally wanting less dependence on Google. I also like that Firefox has a built in tracking…
I found Electrolysis still quite slow. but the new engine ("Quantum"), is ridiculous fast. The last ~5 versions were such big improvements, that I even switched from Chrome. It's so good know that there is no need to keep Chrome. Firefox isn't good enough again, Firefox is the browser again.