* Then you explained that there was a world of difference between a beta and a pre-release build, knowing that said build will become a beta in a few days or weeks and that developers only have a limited working ability (Not really… Betas are just fully packaged trunk builds for those who are afraid of unpacking a zip file including a trunk build) * Then, short of argument, you repeated yourself about speed, hoping that it makes it more true (No.) The merging still has to be worked on, there can be a performance gain there) It’s a very young merge of two older engines. * JaegerMonkey is older than two weeks old, why should it improve ? (Terminologically wrong. * Firefox on ARM is still not mature (Finally, you’re right. Curious, the extra registers should have had some effect…) By the way, noticed the performance difference in webkit between x86 and 圆4 in those tests ? Absolutely nothing. So 圆4 is an interesting platform to develop on, but by no mean, if you want to target users as a whole and not solely computer geeks, it should be top priority. Apple only got interest in 64-bit technology rather recently, and Linux/BSDs are a small minority.
A large majority of today’s computers run Windows XP x86, a smaller part runs Windows Vista x86, and only then you’ll find Windows 7 圆4 because Microsoft finally shakes its ass. The good wording is that x86 is still current gen and 圆4 is still next gen, as of today, because 64-bit mode requires OS support to be activated and otherwise hardware runs in x86 emulation mode, just like in Mozilla’s tests. * x86 is legacy, 圆4 is current gen (Absolutely and totally wrong. As far as I too know, Nokia were rather planning to use WebKit as their main browser) * Firefox+Qt is in active development because of Meego (Maybe right, maybe wrong. * Firefox 4’s hardware acceleration will only works on Windows ( ) What’s horribly slow in Firefox is its UI, and I hope they’ve finally done something about it in firefox 4 prereleases) Javascript speed is just a game for geeky developers where browsers are close to each other in ordinary conditions. The perceived difference in performance is small, as pointed out by ndrw. * Webkit browsers are much faster at rendering webpages than Firefox (Wrong. It’s then followed by Opera’s engine, which is already much better, then Gecko which is even better because of the Mozilla legacy of competition with IE as the dominant browser, and obviously Trident (IE) itself) Most websites are made for IE6 or IE7, and webkit has the worst IE compatibility around. * Webkit’s rendering of most websites is perfect (Wrong. OTOH, Mozilla may have used current releases of Safari and Chrome instead of nightlies, which would be a bit unfair, but as far as I know and as the Chrome 6 release shows it best, webkit’s current priority is not performance) * You assume that webkit stands still (it does, looking at the graphs. Mozilla are finally catching up in this competitive area, and that’s better for everyone in the end) * Firefox is slower than anything Webkit-based (right, but not for a long time. Let’s recall what you said in this thread.
What makes it most comic is that lemur2 probably has just as much of a social life as you and me, making you sound just even more silly. “I’m desperate to get the last word, but I realize how stupid what I said on this thread was and how short of arguments I am now, so I’ll just try to hit my opponent in the balls with something which hurts because I feel hurt myself, and then quickly flee to hide how shameful I feel”. I’m attending social life now than continuing to waste my time with some random pseudo expert. Wisdom for the people, viva la wisdom.The fact alone that you can’t differentiate between Beta 6 and a pre-beta nightly (“pre” is part of the version number for a reason) speaks more than 1000 words about your incompetence in IT. Hence, Mozilla’s decision to disable TLS 1.0 and 1.1 is welcomed as far as I’m concerned : wise browser needs no wise guy being pointed. Otherwise, considering 0.5%, I’d push the minimum to 3 (TLS 1.2) or at least to 2 (TLS 1.1).Īlways the same problematic : if you set as a wise guy you get more quickly spotted. * Firefox telemetry (April 2019) shows only 0.5% of TLS web traffic uses 1.0 or 1.1 ***/ * Leave these at default, otherwise you alter your TLS fingerprint. * 1202: control TLS versions with min and max If I leave it at default it’s only because our Ghacks-user.js recommendations ( ) state (Ghacks-user.js version 69-beta) : Likely even less for TLS 1.0 so one may wonder why TLS 1.0 (at least!) is still supported now on Firefox 69 : is 1 (1=TLS 1.0, 2=TLS 1.1, 3=TLS 1.2, 4=TLS 1.3). “Back then it was revealed that TLS 1.1 was used by 0.1% of all Internet connections the number has likely gone done in the meantime.”