9 ms·
This is just a troll post getting way too much attention. Let's consider a few facts to put it in perspective. Firstly, neither IE 9 nor Firefox 4 has been rel
by Silhouette 16y ago
This is just a troll post getting way too much attention. Let's consider a few facts to put it in perspective.
Firstly, neither IE 9 nor Firefox 4 has been released, and neither HTML5 nor CSS3 is a standard, nor will either be for several years at a minimum. The entire argument in this post boils down to not liking one experimental piece of software over another because the author's personal preferences for experimental features are not supported.
Secondly, when it comes to performance, IE has been getting better with every version while Firefox has been getting worse. If you want to talk about modern browsers in a useful way, instead of about bleeding edge features that no-one will be using on mainstream web sites for a while anyway, consider that Firefox is the only one of the major browsers that does not handle each tab independently, leading to obvious performance and security problems.
Thirdly, the trend for Google and now apparently Mozilla to release updates every few weeks is not necessarily a good thing. The major advantage is supposedly that it allows browsers to develop faster, but as any Linux advocate can tell you, it's no good having a great platform if no-one is building great stuff on top of it. For developers, automated updates every few weeks are often unhelpful, because you're always trying to test against a moving target. When you have to deal with inconvenient realities like contracts and customer approvals on major projects, it's now almost impossible to include testing against Chrome and soon Firefox because you don't even have a stable version to use as a basis for tests. I have no problem with pushing security patches more regularly, but they shouldn't be changing functionality and obviously Microsoft does this for IE anyway.
Maybe I'm just weird, but I consider issues like performance, reliability, and having a stable foundation to build on to be far more important than supporting your own browser's take on some hypothetical future "standard", which is just IE vs. Netscape all over again. On that basis, IE is currently the only one of the big three that is actually going in the right direction. It's just a shame they're not providing it on XP.
- fabjan 16y ago> Secondly, when it comes to performance, IE has been getting better with every version Really? I use IE 8 at work and opening a new empty tab takes ten seconds. I'd hate to see what it was like in 7.
- Silhouette 16y agoYour system is broken. Opening a new tab in IE8 takes well under a second on every machine I use, regardless of Windows version or even, within reason, age.
- Groxx 16y ago>when it comes to performance, IE has been getting better with every version while Firefox has been getting worse Fast speed-up happens in developmental builds. There's more to improve than in a finely-tuned end-product that you can't change significantly. And apparently you haven't compared FF 4 to 3 on the same machine. Page-rendering and especially JavaScript are significantly faster on 4. Start-up seems to be slower though, yes; I gather that's partly because they don't intend to optimize it much until the release version. I'll take moving targets that net-improve with backwards compatibility over years and years of non-change, though I'll admit a) I'm not running a business on this opinion, and b) others may disagree. Web development is extremely highly paced right now, being stuck for years is complete and utter death. Out of curiosity: what's the "right direction" you think IE is taking? Stability over incremental updates? Or something else?
- Silhouette 16y ago> Out of curiosity: what's the "right direction" you think IE is taking? Stability over incremental updates? Or something else? Well, yes, I am in favour of a certain level of stability over lightning-fast development. No-one who is actually developing web sites can use all the bleeding edge stuff the day it's released anyway, and releasing functionality changes every few weeks just means yet another round of reading release notes and blog posts to make sure nothing is about to break. I would far rather have a new version released, say, every 1-2 years, with a clearly defined set of new major features, and with every major browser implementing those new features at roughly the same time and in the same way. This is, after all, the point of standards. (Security patches can be released ASAP of course, but shouldn't change any functionality anyway.) More than that stability, though, I feel that the IE team is focussing on better support for important technologies that are out there right now and experienced by real people and not just geeks and web designers who like the shiny new toys. For example, while Google, Adobe, Apple, and Mozilla are having a big pissing match and actively dropping support for various things, IE will be happily running Flash, H.264 in an HTML5 video tag, etc. Along similar lines, recent versions of IE have dramatically improved both JS performance and standards compliance, so most arguments about IE being slow or needing things like CSS hacks are out of date anyway. Moreover, Microsoft have much improved their handling of security issues in recent years, and as I mentioned before, IE has long since moved to running tabs independently. I've been shopping on-line for a lot of networking components recently, and while Firefox has been my default browser for a while, I've been getting awfully tired of waiting around because one of the 20+ tabs I opened to compare products/prices was loading slowly and locking up the whole browser. Apparently I've gone into super-verbose mode today so I'll stop there. Basically, I do think IE's approach to releases is more practically useful and sustainable, but I also think the IE team is focussing their efforts on technologies that are in widespread use today, while some of the other browser teams seem more preoccupied with bragging rights about trendy-but-currently-worthless new ideas and politics, neither of which ever did much to help real users trying to get real stuff done.
- ahi 16y agoThe disadvantage of IE's tab handling is that it frequently takes a second or two for a tab to come up. That makes IE unusable for me, as every few minutes I'm doing a search with 'ctrl-t tab <keywords>'
- pushtheenvelope 16y agoThe IE team has made many changes to improve the tab opening and closing speed. These operations are snappy on my machines. Could you confirm that you see this slow behavior in the IE9 RC?
- curtin 16y agoFirefox does the same thing though. The only browser that doesn't IMHO is chrome.
- beej71 16y agoIt's more than a shame Microsoft's not providing IE9 on XP. It's positively criminal. Do you know what it's like to target IE8 with a web app that was built for a modern browser? And XP has 60% of the market! It has been a good... forever since MS has been a proper team player when it came to working well with websites that run on all other browsers with minimal modification. This is closer than we've ever ever been in the past to having a remotely sane reality. So pretty please, with sugar on top, fix the fucking browser.
- Silhouette 16y ago> It's more than a shame Microsoft's not providing IE9 on XP. It's positively criminal. I understand the sentiment, but I don't think that kind of hyperbole advances the debate in any useful way. Obviously Microsoft are under no legal obligation to support an operating system first released many years ago and when two successors have been out for a while now. It may be commercially sensible for them to do so, but that depends on many other factors beyond the preferences of the web development community. > Do you know what it's like to target IE8 with a web app that was built for a modern browser? Yes, I do that for a living, on multiple projects, and so far I have encountered no serious difficulties in doing so. What problem(s) have you found with running "a web app that was built for a modern browser" on IE8? > It has been a good... forever since MS has been a proper team player when it came to working well with websites that run on all other browsers with minimal modification. So people often seem to say, yet I find very few portability/compatibility issues with running my web apps on any recent browser. I was surprised to find that in the last problem that did arise, it was actually IE that was compliant and Chrome and Firefox that were implementing non-standard behaviour. And as I noted before, IE is one of the only major browsers that hasn't been playing silly political games with blocking useful video-related technologies lately. > This is closer than we've ever ever been in the past to having a remotely sane reality. I guess we just have very different points of view, perhaps born of different real world experiences. In my world in 2011, we are closer than we have been for many years to the hell of IE vs. Netscape, everything working differently in every browser, and having no stable target for development. As I see it, the blame for this lies almost entirely with Mozilla, Google, and to some extent the standards bodies, not with IE.
- Fluxx 16y agoThis may be true, but there are a bunch of useful things IE9 doesn't support that even Firefox 3.6 does: 1. Text shadow 2. Offline applications 3. Multiple column layout 4. Border images 5. Web workers, File API, Geolocation A lot of these are in the working draft phase, so I can get the "we don't support any feature where the spec is in draft form" argument from IE. But if they want to play a part with the future of the web, IE needs to stop being boring and actually try to implement some draft features and help contribute to developing these standards.
- kenjackson 16y agoIE needs to stop being boring and actually try to implement some draft features and help contribute to developing these standards. But the second this happens, I guarantee that people will loudly complain. IE10 comes out with a slew of new features and MS puts them on the docket for standardization. People will say that MS is trying to hijack the web or standards process. For all the grief MS is getting by being behind, they'd get a lot more grief if they were active and out front w/ respect to features.
- wvenable 16y agoYet, we actually owe many modern web features to Microsoft with IE. There is the obvious stuff, like xmlHttpRequest (Ajax) but also simple stuff like allowing event handlers on every DOM element. All the stuff that Firefox/Chrome/Safari/Opera are doing now is exactly what IE did for it's entire history up to version 6. And really, IE very quickly became the superior browser of the day. But from then on, they appear to only be putting in minimal effort with no innovation.
- daleharvey 16y agoContinuous deployment is a mechanism to improve reliability not reduce it, ie is sticking to the same process that has been broken for how long? chrome has proved that continuous release cycle can produce the most stable and performant browser around. and your continuous dismissal of new web technology as "hypothetical / experimental" and talking about when html5 will become a w3c standard shows a complete lack of understanding as to how the web + browser development works to an extent that its really hard to not see irony in this comment calling the OP a troll
- Silhouette 16y ago> chrome has proved that continuous release cycle can produce the most stable and performant browser around. I respectfully disgaree. New Chrome releases have broken both cosmetics (rounded corners, just as the CSS3 version was starting to take off) and basic functionality (H.264 support for the HTML5 video element is disappearing in about five weeks, even though it's there and basically working today, as far as I can tell for purely political reasons). By the way, the word "performant" is real but does not mean what you think it does. Even if it did, I think you'd still be overstating the case. Chrome is probably faster than Firefox and IE in some respects today, particularly where JavaScript is concerned, but the gap has been closing for some time now. Once IE 9 and Firefox 4 are out, it looks unlikely that Chrome will still be significantly faster for typical real world browsing, which as I've noted previously, I consider to be more important than things like synthetic benchmarks or the speed of features no-one is using yet.
- daleharvey 16y agodom rendering speeds even up to ie8 lag far far behind what chrome and firefox have been capable off for years, everyone on the internet uses dom rendering and RIA's are not possible without being able to do fast dom modifications, most real world performance benchmarks have problems even running in ie because it is so slow. h264 was a conscious choice, nothing "broke", I dont know which rounded corner issue you are referring to, it certainly isnt "broken" and remember you are referring to features which do not yet exist in any release of ie
- ootachi 16y ago"Secondly, when it comes to performance, IE has been getting better with every version while Firefox has been getting worse." Your point about the lack of out-of-process tabs is legitimate, but I'm unsure as to how Firefox is getting worse. Could you elaborate? As far as I can tell, Firefox 4 is better than 3.6 in terms of performance on virtually every measure.
- burgerbrain 16y agoI haven't used other browsers besides Firefox in years, so I'm not qualified to provide a comparison. What I can say is that on the "profanity uttered"/"hour of usage" metric, Firefox has been getting much worse. Hell, I used to praise it.
- ootachi 16y agoHave you used Firefox 4, and if so, do you have things in particular that are slow?
- burgerbrain 16y agoNot slow, just breaky. Now, 3.6.13, which I use the majority of the time, is both.
- Joeri 16y agoHave you tried creating a new profile? In my experience, firefox needs a fresh profile every now and then or it becomes horribly slow.
- gst 16y ago"and neither HTML5 nor CSS3 is a standard, nor will either be for several years at a minimum" Actually, HTML5 will never be a standard (at least not one released by the WHATWG), see: http://www.h-online.com/open/news/item/HTML5-to-become-a-living-standard-called-HTML-1172982.html http://www.h-online.com/open/news/item/HTML5-to-become-a-liv... (Yes, I know that the W3C plans to release an HTML5 standard based on the WHATWG work in several years from now. But based on the current track record of the W3C I predict that this will either fail, or that the standard will be outdated by then.)
- Lennie 16y agoActually Firefox 4 Beta is not slower, it starts up faster than prevous versions of firefox. It has faster rendering and javascript engine. And it is especially more responsive. Just try it.
- eitland 16y agoTake a closer look at this: >> and neither HTML5 nor CSS3 is a standard, If Microsoft are referring to HTML5, Mozilla should be allowed too.
- alanh 16y agoI have to ask, because you seem like a committed defender of Microsoft: Are you affiliated with them at all, or perhaps a .Net/ASPX coder?
- Silhouette 16y agoNo, I have no connection to Microsoft. I'm familiar with technologies around .Net and have nothing against using them where a project calls for it, but as it happens none of my current commercial projects is built on it today. I certainly have no vested interest in promoting it over any other platform that might be more suitable for any given job. More generally, I have been rather critical of Microsoft/IE for a long time, for much the same reasons many here apparently still are. However, I do try to look at situations objectively and consider the facts, both quantitative and qualitative, and that in an industry that moves this fast, those facts can lead to different conclusions rather quickly. I honestly see Microsoft's current direction for their browser as healthier and more sustainable than that of say Google or Mozilla. I don't think more frequent releases of new toys or a factor of 5 difference in synthetic benchmarks can trump an emphasis on providing/speeding up core functionality that real users depend on today and tomorrow. Also, so far Microsoft are mostly rising above the silly political games that Apple/Adobe/Google have been playing lately in terms of knocking out functionality for non-technical reasons. Meanwhile, I have been less impressed with each successive version of Firefox, as performance of the UI slowed, things got moved around or more cluttered, and they didn't keep up with what I regard as essential features in a web app world like running tabs independently. I have nothing serious against Chrome, except that their release schedule and tendency to break stuff makes my life difficult as a developer. However, I also see little practical advantage in the areas they have been speeding up lately, since they were fast enough even for the web projects I work on that do fairly intensive DOM manipulation and such. As anyone reading my posts here can probably figure out, once functionality is fast enough to use in practice, I am more impressed with making it easy to use, robust, and/or easy to develop than I am with getting another notch up on some benchmark.
- pbhjpbhj 16y ago>Microsoft are mostly rising above the silly political games that Apple/Adobe/Google have been playing lately in terms of knocking out functionality for non-technical reasons. You mean like satisfying current internet standards and meeting the draft standards head on to allow browsers to exploit the latest advances in web design and development off the bat rather than having to wait years-and-years and drag back the whole development of the www as a medium. >Meanwhile, I have been less impressed with each successive version of Firefox, as performance of the UI slowed, things got moved around or more cluttered, and they didn't keep up with what I regard as essential features in a web app world like running tabs independently. What do you mean by "performance of the UI slowed". You've stated quite clearly that performance is only a factor for you up to the point it is fast enough. So, it seems something in the UI is so slow as to be unusable for you - the UI is pretty much non existent though isn't it. There's an address bar, couple of buttons, search bar - what is significantly slowing you down there? The actual user interfaces save a few niceties (like Chrome's tab closing, optional tabs on top in Chrome/FF/Op, etc.) are pretty similar in their standard forms. You mention running tabs independently (as independent processes presumably) I didn't know that IE8 did this?
- GrayFace 16y ago> consider that Firefox is the only one of the major browsers that does not handle each tab independently, leading to obvious performance and security problems. Well, here's the reality: having each tab in individual process greatly reduces performance and increases memory consumption. When you open many tabs in Chrome or IE they become as slow as FF with perhaps 5-10 times more tabs. While performance generally isn't a field where FF does a good job, I think reliability of FF is unmatched by other browsers despite the dirty tricks with tabs. Let's just wait 'till they stop losing the list of tabs that were open in the previous session from time to time, it's the thing that did happen to all of them, but never to FF with Session Manager addon.