Slashdot Mirror


Gates Expresses Surprise Over IE8 Secrecy

eldavojohn writes "Shortly following the frustrations of IE7, Gates claims that he is unaware that IE8 Secrecy has been alienating developers. Ten influential bloggers met with Bill on Tuesday and asked Gates questions about why they are no longer receiving information on IE. From Molly Holzschlag's blog: 'Something seems to have changed, where there is no messaging now for the last six months to a year going out on the IE team. They seem to have lost the transparency that they had. This conversation [between Web developers and the IE team] seems to have been pretty much shut down, and I'm very concerned as to why that is.' To which Bill replied: 'I'll have to ask [IE general manager] Dean [Hachamovitch] what the hell is going on, I mean, we're not, there's not like some deep secret about what we're doing with IE.'"

75 of 381 comments (clear)

  1. In a perfect world by Ckwop · · Score: 5, Insightful

    They'd be no secret about what I'd be doing if I was running the Internet Explorer 8 team. Here's a few things I'd do:

    1. Turn everything on this page that is red to green for the Trident engine.
    2. Fix everything on this page.
    3. Correctly support the mime-type for XHTML and display an error if *anything* on that page is incorrectly formed. The last part of this sentence is absolutely crucial. We need to start breaking pages that are not correct, XHTML is a good chance to push this.
    4. Get rid of the Trusted Site, Internet, Untrusted security model and just have Untrusted.
    5. Get rid of ActiveX. Support Internet Explorer 6 for ActiveX for another five years to allow people to transition to other platforms.

    For bonus points, do all this faster and with less memory than Internet Explorer 7 takes.

    This is a fairly modest list but if they fixed all of that, Internet Explorer would be a joy to develop against. Hell, I might even consider replacing Firefox as my default browser on Windows. However, as much as we can collectively dream, you know they'll rejig the interface slightly, crank up the version number by one and call it a day.

    Microsoft is a text-book example of a market failure. Nearly every other browser has Internet Explorer boxed off in terms of functionality, security and speed. The only reason it is the world's number one browser is because it comes pre-installed with WIndows.

    As a program Internet Explorer is simply trash. I simply hate it. Actually I fucking despise it. It is a big ball of shit. It's the ugly building in the middle of a city that everyone wants torn down but it just sits there damaging the community's spirit.

    I once joked with a colleague that Internet Explorer has probably wiped billions off pounds off the world economy. I laughed, paused for a moment, and realised it's probably completely true. What could the world have done with all those countless hours hacking their CSS to support the trash that is Internet Explorer?

    Doesn't it make you depressed?

    Simon

    1. Re:In a perfect world by coryking · · Score: 2, Funny
      • Dont forget SVG support too.
      • A good debugger would be nice.
      • Meet the standards and then innovate on top of them. Remember back in the day when every browser was adding extra tags to try to outdo the other guy? I really think we need that again. Semantic web is a pipe dream, HTML sucks, CSS is largely ivory tower bullshit and the W3C is ineffective at giving developers a good language. A classic Firefox vs IE battle of layout tags is exactly what we need to stir up the pot. Just make sure you follow the current standards first.
      I have no doubt that IE has cost our global economy billions of dollars in wasted time and effort. I also suspect there is a higher instance of stress related illness and depression in web developers. Developing on today's internet sucks monkey balls, and it is a large part due to IE. ... And this is all comming from me, proudly running on Vista developing in VS2008. I'm practically a Microsoft fanboy!
    2. Re:In a perfect world by Shados · · Score: 2, Interesting

      The problem is that Trident is also used as an all purpose rendering engine. Just about everything you can think of that renders "something", aside from big hot shots companies, will use Trident to render their content...so break Trident, you break everything. Thats part of why upgrades to it are so incremental and never revolutionary.

      Now, why don't they change the engine in IE while keeping both versions for backward compatibility? Thats the more interesting question.

    3. Re:In a perfect world by bunratty · · Score: 5, Informative

      First, the OP is referring to XHTML, where an error message on malformed XML is required. Second, if IE gave an error for a web page, web developers would surely fix it before the users had a chance to complain much. Fixing legitimate XML errors would be easier than the contortions web developers already go through just to make pages look good in the current version of IE.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    4. Re:In a perfect world by plague3106 · · Score: 2, Interesting

      Get rid of the Trusted Site, Internet, Untrusted security model and just have Untrusted.

      So even your company intranet should be untrusted (Restricted Sites), and not allowed to use ANY plugins or Javascript? Ya, great plan. Lets not forget how useless many other sites would be.

      I once joked with a colleague that Internet Explorer has probably wiped billions off pounds off the world economy. I laughed, paused for a moment, and realised it's probably completely true. What could the world have done with all those countless hours hacking their CSS to support the trash that is Internet Explorer?

      It's actually completely false. Your argument is similar to that used by those pushing "traffic safety" measures. Higher insurance rates / costs from accidents don't damage the economy, they actually contribute to it. You may not be happy paying $100 more to your insurance that you could put elsewhere, but its certainly not hurting the economy at all. If anything, the bugs in IE contribute to the economy, as more money is required to move through the system to account for them.

    5. Re:In a perfect world by ET_Fleshy · · Score: 2, Interesting

      He specifically said pages served in xhtml.

      Very, very few pages are served this way, it's usually text/html.

      Xhtml is suppose to break!

    6. Re:In a perfect world by 99BottlesOfBeerInMyF · · Score: 5, Insightful

      They'd be no secret about what I'd be doing if I was running the Internet Explorer 8 team. Here's a few things I'd do:

      6. Look for a new job because they fired me.

      MS doesn't want those fixed. Seriously, they make money by ensuring that other browsers can't compete because the Web is broken to conform to IE's modifications of the standards. In this way they lock people into their platform. If IE was standard compliant, then soon Web apps would be standard compliant, and then why the hell would big companies stick with IE and an expensive OS, when they can just run Linux for free?

      Microsoft is a text-book example of a market failure. Nearly every other browser has Internet Explorer boxed off in terms of functionality, security and speed. The only reason it is the world's number one browser is because it comes pre-installed with WIndows.

      IE will never have the same functionality, at least in terms of standards compliance, as other browsers as long as MS is allowed to bundle it without also bundling competitors. The Web will remain broken so long as MS is allowed to abuse their monopoly and numerous other markets will be broken as well, with innovation intentionally slowed for their profit. It is long past time the government enforced the fucking laws against MS, despite all the campaign contributions they made to both parties.

    7. Re:In a perfect world by CastrTroy · · Score: 2, Interesting

      I hope you were joking about "Meet the standards and innovate on top of them". The browser war was terrible for developers. You obviously don't remember trying to program Javascript during the Netscape 4 days. Anybody who knows anything about web development knows that you don't do layout with "tags" you do layout with CSS. It's different than doing layout with HTML Tables and Tags, but it makes your website much more flexible. CSS3 is coming, and it will provide us with even more features.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    8. Re:In a perfect world by coryking · · Score: 3, Insightful

      I know that you do layout in CSS. The problem is CSS is an inadequate way to express layout. Where is my "make a three column grid that extends the height of the page" in CSS?

      My point was really, there needs to be some innovation. HTML & CSS have grown stagnant and are not keeping up with what modern web applications are asking it to do. W3C is an ineffective standards body and is incapable of delivering something to meet these new demands. The only way I can see innovation now is if browser makers roll their own. Hell, even firefox has those -x-rounded-corner things. Gee. Maybe people want rounded corners huh? Why isn't this getting added to a formal standard?

      The important thing though is to make sure you meet all the baseline standards first before adding cool crap on top. IE doesn't meet the baseline yet, so they aren't in a place to do cool new stuff.

      At least, this is my opinion.

    9. Re:In a perfect world by coolGuyZak · · Score: 5, Interesting

      If anything, the bugs in IE contribute to the economy, as more money is required to move through the system to account for them.

      While superficially correct, this is a case of the broken window fallacy. The money spent working around IE bugs could be spent better elsewhere (for instance, QA, usability, etc.).

    10. Re:In a perfect world by devjj · · Score: 4, Insightful

      This is why web developers need to stop working around shitty rendering engines en masse. Every single time we - as developers - utilize hacks to make things work in IE where they're fine in WebKit, Gecko, et. al., we further allow IE to be as bad as it is. Do you honestly think IE would be the POS it is today if the world's web sites didn't work in it? Every single time we work around it we provide Microsoft reason not to change anything. Literally. Microsoft's biggest concern has always been backwards compatibility, and it is that reason that so many of the issues we have now we also had then. It would be one thing if IE7 had shown considerable improvement in this regard, but that simply isn't the case. IE7 kept some bugs, and swapped out some well-known ones for others, which we now have to hack around, again.

      If browsers actually required that we provide valid code each and every time, things would be a lot better. How many browser security holes can be traced to a parser that would not have been affected had it simply seen invalid input and rejected it? How much simpler and faster would browsers be if they didn't spend so much time trying to figure out what the person who wrote the code intended? How much more accessible would the content on those pages be to alternative browsers, like screenreaders?

      We've been running for way too long on the mindset that anybody can build web pages. Web browsers were built with this mentality. If I'm integrating with an enterprise XML API, and I feed it bad data, it gives me the proverbial finger. Why should web pages be any different? If you want to put stuff online, learn how to do it properly. The web is a cesspool for precisely this reason, and you can't blame the standards themselves. The XHTML and CSS specs are by no means perfect, but writing well-formed XHTML and CSS is not difficult. Requiring developers to ensure that every start tag has an end tag, proper nested order, alt tags, and the like, would go a long way toward keeping the architecture of the Internet sustainable. Granted, it might put sites like Myspace out of business, but I'll go out on a limb and say that's not a bad thing.

      Our PCs would be a lot safer, too. Call that a bonus.

    11. Re:In a perfect world by peragrin · · Score: 2, Interesting

      >>Now, why don't they change the engine in IE while keeping both versions for backward compatibility? Thats the more interesting question.

      The same reason why they didn't break all backward compatibility for Vista and use a sandboxed WinXP emulator for older applications.

      MSFT managers won't think out side the box.

      --
      i thought once I was found, but it was only a dream.
    12. Re:In a perfect world by CastrTroy · · Score: 3, Insightful

      I've never understood why people would want a 3 column layout on the web. The web isn't a newspaper. 3 Column layout doesn't work well. I seriously think someone went through the trouble of figuring out what CSS couldn't do (however useless or obscure) and started it as a meme or how weak CSS was. Firefox has x-rounded-corners because it's part of CSS3, and it's not officially supported yet, so they don't want everyone using the actual css rounded corners thinking that it's fully supported. For more information on rounded corners in CSS follow the link.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    13. Re:In a perfect world by coryking · · Score: 4, Interesting

      As long as the baseline standards are met, who cares? Nobody sane will use proprietary tags. All it does is make the other browser maker go "those bastards! they have curvy corner tags! lets steal the thing and enhance it by add drop shadows too!". Now we've got drop shadowed DIV's with curvy corners in CSS. Each browser maker will copy the other guy's syntax, improve it a bit, and kick it back out the market.

      Look at the IFRAME. You think that little fairly useful tag came from the W3C? Look at all the other tags you've got in HTML. How many of them were dreamed up by the eggheads at the W3C? I'm no historian, but I'd wager most of the useful bits of HTML and possibly CSS we have today is not because of the W3C, but a byproduct of the IE vs. Netscape wars of way back when. Shit, we even have the useful BLINK tag!!

      The W3C is horrible at cranking out useful standards - those guys seem more interested in hearing themselves talk. They want you to give up tables for a grid layout (which is a good move) but provide no direct replacement. Yes you can rid yourself of tables, but you do so with a hack. Hell, wasn't the TABLE tag something from Netscape?

      Bottom line? The only way we will evolve on the web is with another bloody tag war.

      At least, in my opinion. I could be wrong you know :-)

    14. Re:In a perfect world by devjj · · Score: 4, Insightful

      For a competent developer, writing valid code isn't difficult. A competent developer is already doing it. All this would do is out the bad developers, which I have absolutely no problem with. People think they can buy DreamWeaver and call themselves developers. That's how bad it is. That's what needs to stop. Good developers would get the money they deserve, and bad developers would no longer be able to parade themselves around as knowing WTH they're doing.

    15. Re:In a perfect world by Apiakun · · Score: 5, Insightful

      I call BS. It would take less time to develop dynamic websites that conform to standards than to have to code around existing browser inconsistencies.

    16. Re:In a perfect world by iron-kurton · · Score: 2, Insightful

      As a web developer myself, the solution is never so simple as to say "screw IE." The customer you are building the site for wants a page that works in all browsers. Since IE is widely used (*gag*), unfortunately, we have to obey our customers. And if I don't do it, my competition will, and I've lost a customer. Granted, I don't want those customers, but 99% of them are like that, so I don't really have a choice in the matter. There's no way we can all unite together in some kind of revolt -- some developers may not even want to unite because it's extra business for them!

      The damage has already been done. How would you propose we stop supporting IE's shitty rendering engine without angering our customers?? Don't get me wrong, I am also tired of working around IE's retardedness, but I think that simply stopping support for IE is not a feasible option at this point in time. Repairing the damage is going to take time -- lucky for us, other, better browsers are gaining a lot of traction, end-users are becoming (slightly) more educated, and with each day we get closer to being able to develop without headaches. But until that day, we just have our hopes, blood, sweat, and tears...

      --
      Change is inevitable, except from a vending machine -- Robert C. Gallagher
    17. Re:In a perfect world by devjj · · Score: 4, Insightful

      How quickly would people migrate to better browsers if sites actually started doing that? How much better would the web be in five years if people were forced to write valid code? That error message is fine, because there are plenty of browsers out there capable of doing an excellent job rendering HTML and CSS, and I guarantee it wouldn't stick around for long. If IE actually lost its majority Microsoft might actually have a reason to make it competitive.

    18. Re:In a perfect world by brunascle · · Score: 2, Insightful
      from the link:

      System Requirements
      Windows Server 2003; Windows Vista; Windows XP
      File Name:
      IE6_VPC.EXE
      IE7_VPC.EXE
      it's a good thing he bought XP and VMWare, so he can run those EXEs :)
    19. Re:In a perfect world by Slate99 · · Score: 2, Interesting

      This is a complete load of crap: "The only reason it is the world's number one browser is because it comes pre-installed with WIndows."

      Every version of Windows has Notepad and Wordpad. However, these are not the worlds number one text editors... There are better editors out and people spend a lot of money to get them (or download a free half-ass knockoff from the web). Either way, they go out of thier way to get something better. Why not do this for a browser? That's an easy one: IE7 works pretty well and there is nothing out that is significantly better.

      I have downloaded and used FireFox just to see if it is really that much better than IE. It is not. If IE is an ugly building I would have to say that it is surrounded by many more just like it except not as tall. I use IE7 every single day and have almost zero problems. Where do you get this crap?

    20. Re:In a perfect world by devjj · · Score: 4, Insightful

      You know what you get when demand far outstrips supply? Opportunity.

    21. Re:In a perfect world by Bert64 · · Score: 2

      Except that microsoft have a history of malice, and are far too successful (through many malicious acts) to be called incompetent.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    22. Re:In a perfect world by brusk · · Score: 2, Insightful

      How quickly? Not quickly enough that you could justify to your boss the n% drop in sales last month because you blocked IE and some customers bought from a competitor who didn't. Even if n=1. And not quickly enough to justify blacklisting users who happened to be using a computer in a public library that gave them no choice.

      --
      .sig withheld by request
    23. Re:In a perfect world by brusk · · Score: 5, Funny

      There is a fine line between courage and stupidity. You appear to be prepared to cross it.

      --
      .sig withheld by request
    24. Re:In a perfect world by version5 · · Score: 2, Insightful

      You seem to live in an imaginary world where a broken website is blamed on the web browser instead of the developer. Maybe after you graduate from high school and get your first job, you'll realize that people hack around IE not so that they can support IE, but so that they can support Firefox. 90% of clients want their websites to work in IE, and couldn't care less about Firefox or Safari. All your courage will get you is a tiny client base and the luxury of continuing to live with your parents.

      --

      "It's Dot Com!"

    25. Re:In a perfect world by devjj · · Score: 2, Insightful

      Someone once said to aim high so failure still puts you further ahead. If you honestly think that I honestly think this is feasible overnight, you're dreaming. There's nothing wrong with talking about how things would be ideally, so we can work backward from there to find reasonable solutions. That being said, I stand by the original (-1 Flamebait) comment. Sometimes you have to be willing to take risks if you believe in something. I believe in standards.

    26. Re:In a perfect world by brusk · · Score: 2, Insightful

      When it's a choice between trying to leap the 20 foot chasm and walking an extra mile to the bridge, I know what I'm doing.

      --
      .sig withheld by request
    27. Re:In a perfect world by Kelson · · Score: 2, Insightful

      In any case, the problem isn't with browsers being too permissive. The problem is that IE doesn't support the various web standards to the same level that other browsers do. If IE renders the CSS, SVG, XHTML, etc. specs properly but degrades gracefully when it gets a non-compliant page, that is fine with me.

      Actually, the difference between various browsers' error-recovery algorithms is a fairly big part of the problem... but only in the sense that the browsers are being used by the developers for debugging. If there were some sort of "developer mode" which would provide extremely useful debugging tools, but only on well-formed code (and making well-formedness the requirement instead of actual validation keeps it open to future versions of HTML/CSS), it might accomplish the same thing without causing problems for end users visiting existing websites.

    28. Re:In a perfect world by BenoitRen · · Score: 2, Insightful

      People know what text editors and text processors are. They have been there since the dawn of computing, and there never was something special about them.

      But they don't know what web browsers are. When they became popular with the layman, it was Internet Exploder who was leading the market. It also had a generic name.

      Moreover, it's just a viewer. They don't have to actually work with what it views, unlike text editors.

      It's obvious why bundling it with Windows made it the most popular web browser.

      Yeah, IE7 works pretty well until you have to actually make a website that displays correctly for all web browsers. I've banged my head for days on a simple problem that occurred only in IE7. When it comes to web standards, Firefox is much, MUCH better.

      Did you say the same when you were still using IE6? That's an even bigger pile of shit. More bugs, no PNG transparancy, no tabs, etc.

    29. Re:In a perfect world by absoluteflatness · · Score: 3, Insightful

      Basically, the attitude (which I agree with) is that you have to, at some point, apply some pressure if you want adherence with the standards. If browsers rejected non-compliant documents from the beginning, you can bet developers would be sure to have their syntax correct (especially since they wouldn't even be able to preview their pages). Even though I wouldn't classify HTML as a programming language, no other language just silently ignores your syntax errors and tries to "guess" what you meant to do. Unless the procedure for "guessing" is the same everywhere, it's a nightmare for portability, as we see with HTML today (along with other quirks like inconsistencies in every other aspect of the presentation).

      I can't really complain about this enough. You drop a semicolon or parenthesis in C or Java, your compiler lets you know about it, and doesn't proceed until you feed it something that makes sense. Same generally applies for scripting languages. Why browser writers in the early days of the web decided otherwise boggles the mind, and we're still paying for that decision today. You can't just cut out "quirks mode" et al. without breaking large swaths of the web.

      I see the W3C's specification of well-formedness on XHTML as the way forward, the light at the end of the tunnel. Since it only applies to the fairly recent XHTML, there's really no need to sweat about the effects on legacy documents. If someone's got noncompliant XHTML floating around and doesn't care to fix it, nuts to them. On the subject of uncooperative ad servers, if you as a developer can't get them to serve you compliant XHTML, just drop them. It's not as if there's really a shortage of advertising services out there. This won't have to go on very long before every company will fall into line.

      Of course this all only applies if well-formedness is actually enforced by all browsers, and only if XHTML actually catches on. Similar strictness on the part of HTML 5, if it ever arrives and becomes dominant, could perform the same function too.

    30. Re:In a perfect world by BenoitRen · · Score: 2, Informative

      HTML is presentational.

      Absolute bullshit. HTML stands for HyperText Markup Language. It describes its contents. It describes the semantics. Being semantic is its very nature.

    31. Re:In a perfect world by jln · · Score: 2, Interesting

      May be slightly OT but still.

      The way I remember it [and I have been coding HTML since, oh, '95], the IFRAME tag was m$' answer to Navigator 4 having a 'src' attribute for a DIV so you could load an external document in it. There was also a JavaScript method/property to change or retrieve the contents of a DIV. To me, this seemed like a sensible, logical and very useful extension of the DIV tag.

      Along then, with the advent of MSIE4[?] came the abhorrence called IFRAME since m$ had to have the same functionality [but in a different fashion, obviously]. A frame is a window object and where the hell is the logic in embedding a window in another window?

      And then there's the difficulties when scripting IFRAMEs. Try getting to the document.body of a page in an IFRAME. Or even worse, since in MSIE the event is a property of the window, have fun trying to intercept events in an IFRAME.

      And then, to make matters worse, the w3c, in its infinite wisdom, decided to standardize IFRAMEs over the DIV src attribute, probably trying to pick features in equal measure from MSIE and Navigator when they standardized the DOM.

      Blech, I detest IFRAMEs.

    32. Re:In a perfect world by cheater512 · · Score: 2, Interesting

      Ads are in iframes. The iframe wouldnt load but the main page would.
      That puts it in the ad company's best interests to make it work.

  2. Of course by darkhitman · · Score: 5, Funny

    To which Bill replied: 'I'll have to ask [IE general manager] Dean [Hachamovitch] what the hell is going on, I mean, we're not, there's not like some deep secret about what we're doing with IE.'"
    Of course there's no deep secret about it. "We're doing nothing" is hardly a secret, after all.
    --
    Tell me something...it's still "We, the people"... right?
  3. Truncated by nog_lorp · · Score: 3, Funny

    That quote was incomplete, it's really: "I'll have to ask [IE general manager] Dean [Hachamovitch] what the hell is going on, I mean, we're not, there's not like some deep secret about what we're doing with IE. *cackle*"

  4. Maybe by dedazo · · Score: 2, Insightful

    The IE team is tired of all the adolescent crap that gets posted in their blog. I know I would.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    1. Re:Maybe by coryking · · Score: 4, Insightful

      In this case, that "adolescent crap" is well deserved and hardly adolescent. It is the outpour of pent up rage from professional web developers everywhere.

      Until you've done serious web development, you have no idea how frustrating it is to target IE. Especially when you have to explain to your client why it took a day longer than you estimated because of IE.

    2. Re:Maybe by dedazo · · Score: 2, Insightful
      No, it's not well deserved. Clearly you didn't read through those comments. And the people working on IE7/8 are not the same as the ones that shipped IE5/6, and while the company might deserve the criticism, the individual developers and managers don't.

      I bet it's really hard to manage a project when you post an incidental blog entry about an icon change and you get 300 puerile comments about how you should be working on OMG CSS OMG STANDARDS when the roadmap for the product and what it would support based on time constraints and backwards compat requirments was laid out at the beginning of the project quite openly.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    3. Re:Maybe by coryking · · Score: 2, Insightful

      I could be wrong, so hear me out:

      I read almost all the comments from both blog entries. Aside from a few slashdotty tin-foil-hat EVIL M$ posts, I felt most were fairly well thought out. I don't think anybody was dissing the developers or managers, but more of "hey guys! we are all feeling neglected here" kind of deal.

      How about this. Are the comments you read on those two posts of the same nature as, say, those from the infamous "Digg Rebellion"?

    4. Re:Maybe by encoderer · · Score: 2, Insightful

      No, it's the rants of petulant children.

      If you've done *serious* web development then you consider yourself a *professional*. And as a professional, you no longer have the luxury afforded to the "my CSS is art" drama-queens.

      As a professional, you should be more concerned with the viability of your design to meet your clients goals: most often to sell something, support something already sold, or strengthen the brand they use to sell things. Which means you should be focusing on nothing more than making your design accessible to the widest swath of viewers.

      You should be TARGETING IE from the beginning. No, it's not sexy or trendy. And Yes, i'm writing this from Firefox, so I feel your pain. But when you develop for, FF/Opera/Safari and you realize it looks like crap in IE, you have to go to a client and say "The design doesn't work for 70%+ of the web population. I need time to fix it" Of course, they are not going to be happy. The obvious question is "You just NOW thought about that?" Now, if you do your job, you'd develop on IE first, and then go to the client and say "With another day, I can make this design work for the <30% of users on FF/Opera/Safari. Would you like me to do that?"

      This really isn't debatable. Is IE the best browser? Not in my opinion. Does that matter one bit when you're being paid $50-100/hr to do web development? Not for a second...

    5. Re:Maybe by Anonymous Coward · · Score: 2, Interesting

      And as a professional, you no longer have the luxury afforded to the "my CSS is art" drama-queens.

      As a professional, you should be more concerned with the viability of your design to meet your clients goals

      Precisely. As a professional, it takes longer to do something if I have to work around Internet Explorer's shortcomings, the end result isn't as good, and I have to say no to some features. As a professional, I resent the fact that Internet Explorer is a constant dead weight around my neck, limiting the quality of service I can provide my clients.

      Now, if you do your job, you'd develop on IE first, and then go to the client and say "With another day, I can make this design work for the

      Uh, no way. If you do it that way around, you spend a whole lot longer overall when the client inevitably says that they don't want to throw away that 30% of customers. The optimal approach is to develop on a conforming browser first, using only the subset of features that Internet Explorer supports, and then apply fixes for everything Internet Explorer screws up anyway. And any professional is going to look at the subset, and look at the required fixes, and recognise that Internet Explorer is a colossal waste of everybody's time and that it would be a gigantic leap forward if Microsoft were to simply fix their bugs, and they would also recognise that it's entirely possible for the world's largest software corporation to do it if they actually wanted to. Christ, there are lone developers that have produced more conformant CSS implementations than Microsoft. It's not petulant to resent Microsoft for deliberately holding back an entire industry.

  5. Microsoft is collapsing into itself by MSTCrow5429 · · Score: 4, Insightful

    Sounds like Microsoft has gotten far too enormous to be manageable by most people if Bill Gates has no clue what's going on any more. Vista barely got out the door, it's a lame duck OS, and now at least one of the major software development teams has gone into seclusion, and no one important noticed. Wouldn't be surprised if more problematic tripwires and land mines were hiding under rocks at Redmond. MS needs new management, it's silly that the founders of a tiny itsy-bitsy Microsoft are still in control of one of the largest, sprawling corporations in the world.

    --
    Slashdot: Playing Favorites Since 1997
    1. Re:Microsoft is collapsing into itself by MSTCrow5429 · · Score: 4, Insightful
      "Part of that is because those guys MADE IT into one of the largest, sprawling corporations in the world."

      Different managers are required for different stages of a corporation's existence. Sure, they made the corporation what it is today, but they also mismanaged it into a crippled, bloated, low-growth, living entirely off of prior achievements, slug. It's an axiom that after a certain point, the best thing the founders of a corporation can do for their creation is leave, and I don't think Microsoft has proven to be an exception. Microsoft should have re-invented itself at some point during the 95/NT4 era, and instead calcified into the Microsoft of today. Perhaps the DOJ inquisition had a lot to do with that, but a corporation is forced to live under the regime it finds itself subject to.

      --
      Slashdot: Playing Favorites Since 1997
    2. Re:Microsoft is collapsing into itself by miffo.swe · · Score: 4, Informative

      "It's an amazing world we live in where roughly a year after Vista was released it has 90 million users"

      No it has not in any way, shape or form 90 million users. Microsoft has sold 90 million Windows Vista/XP/NT/2000 licenses in total. The funny thing is, any windows license sold by Microsoft since Vista was released is counted as a Windows Vista license.

      If you have a fortune 500 company and buy a million licenses to deploy XP they will count as Windows Vista license no matter how you buy them. Then we have all the home users that come to me with their new computer with Vista installed wanting me to install XP and delete Vista from their computers.

      Vista is a lame duck considering it was 6 years since XP and there is a pent up want for a new OS. Six years of anticipation and vaporware turned into only minor improvement and in many cases regression.

      --
      HTTP/1.1 400
    3. Re:Microsoft is collapsing into itself by UnrefinedLayman · · Score: 2, Insightful

      The number of Vista users primarily is determined by the number of computers that come preinstalled with Vista. Windows 95's release, when people lined up and charged into the stores like it was Black Friday, is the appropriate contrast.

      Windows Vista's sales numbers to people with computers that can run it but already run XP are low, and that's what's being discussed.

    4. Re:Microsoft is collapsing into itself by happyemoticon · · Score: 2

      Having had some dealings with Microsoft recently, I think it's only fair to point out that their various divisions are already run more like distinct businesses. They're encouraged to think like small businesses, to the point that they actively discourage people from having any relations whatsoever with people of different divisions.

      The problem is that even though their day-to-day operations are independent of one another, they still collude to force shitty technology out the door, and their leadership is too ineffectual to maintain good quality control. I guess that makes them more akin to a loose-knit, highly corrupt cartel. So, they could also go the route of becoming a traditional, bureaucratic company.

  6. Actually this runs across products by Anonymous Coward · · Score: 2, Interesting

    For a year or more now Microsoft has been getting tighter and tighter about what information about their plans and dates can get out. It has been really bad getting info even when you are on one of their TAP programs. Date for the RTM? Hell - you won't even get a date for the next Beta version most of the time. What's in? What's out? Not a chance - you'll get it when you get it. It is so bad now that they need a Minster of Truth to determine what to tell people - http://www.istartedsomething.com/20071207/director-windows-disclosure/.

  7. How can they be working on IE8... by SpartacusJones · · Score: 4, Funny

    before Opera 9.5/FF3 are released and they have new ideas to copy?

  8. don't tell the boss by Plunky · · Score: 2

    Yeah, well he didn't think there was anything secret going on - but maybe they just didn't tell him either!

  9. They don't care? by bushboy · · Score: 2, Insightful

    ... when you have 90% browser market share, I guess thier feeling is "who cares?"

    It certainly seems that way.

    You only need to look at the mess they made of the GUI in ie7 to understand just how far off course the internet explorer team have sailed.

    It's a damn pain to develop for.
    Then again, so was ie6 - hmm, and ie5 and yeah, even ie4 ...

    The problem is, you can't ignore 90% market share - catch 22.

    --
    A slashdotting - you get the stick first and then the carrot !
  10. Too mundane, not flashy and pointless enough by foreverdisillusioned · · Score: 4, Interesting

    If Vista has taught us anything, it's that Microsoft is laser-focused on superficial and eye-candy improvements, while caring very little about improving (or even fixing) the underlying technologies. From my (thankfully VERY brief) experience with Vista, it looks like the only thing they even remotely attempted to fix or improve was security, and that... well, heh, it reminded me of a maxim I once heard: "Those who do not understand Unix are doomed to reinvent it--badly."

    My prediction is that IE 8 will have exactly the same rendering capabilities, but it will have some sort of annoying new UI, plus maybe a few extremely annoying security features that everyone will turn off immediately.

    1. Re:Too mundane, not flashy and pointless enough by baadger · · Score: 2, Informative

      My prediction is that IE 8 will have exactly the same rendering capabilities, but it will have some sort of annoying new UI, plus maybe a few extremely annoying security features that everyone will turn off immediately. This is a perfect description of IE 7. There were only *bug fixes* to the rendering capabilities of IE6.
    2. Re:Too mundane, not flashy and pointless enough by foreverdisillusioned · · Score: 5, Insightful

      Actually I thought the perfect description of IE 7 was "response to Firefox." Seriously, I don't think IE 7 existed as a serious, active project until Firefox started claiming significant percentages of the browser market, and most of the UI additions are ripped straight from Firefox. But, in the case of IE 8, this time there isn't really anything obvious to rip from Firefox--maybe integrated spellchecker? If they try to offer an easy-to-install plugin system (I'm assuming IE 7 doesn't have one already. If it does, forgive me--I've used IE 7 a grand total of maybe 15 minutes), the results will be a security disaster.

    3. Re:Too mundane, not flashy and pointless enough by gallwapa · · Score: 5, Funny

      IE uses easy-to-install plugins...haven't you ever worked on someones machine with 15 search bars?

    4. Re:Too mundane, not flashy and pointless enough by sh33333p · · Score: 2, Informative

      Just for clarification, Opera was the first browser that featured tabs. I was using that back when it was still supported with an ad pane built-in, and blocking those ads with Outpost Pro or Zonealarm. I use Firefox now because of NoScript. There are many other great extensions, but nothing as important IMHO.

    5. Re:Too mundane, not flashy and pointless enough by bunratty · · Score: 3, Informative

      Just to clarify your clarification, there was at least one browser that had tabs before Opera.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  11. And so it begins... by the_skywise · · Score: 4, Insightful

    "To which Bill replied: 'I'll have to ask [IE general manager] Dean [Hachamovitch] what the hell is going on, I mean, we're not, there's not like some deep secret about what we're doing with IE"

    As Bill begins to leave the company, the heralded Microsoft development teams start to act like your normal "joe IT" shop... First Vista... now IE...

    Your powers are weak, old man... :)

  12. Hmm... by Derek+Loev · · Score: 3, Funny

    'I'll have to ask [IE general manager] Dean [Hachamovitch] what the hell is going on, I mean, we're not, there's not like some deep secret about what we're doing with IE.'
    He, like, totally sounds like a Silicon Valley girl.
  13. Standard compliancy is most important for next IE by Anonymous Coward · · Score: 5, Insightful

    At my company we've had to just drop IE for now, and push out Firefox on all clients.
    This is OK for our internal users, but impossible for any external site because of the installed base of legacy CRAP.
    Microsoft need to fix:
    - CSS support
    - DOM support in their javascript implementation
    - XHTML support
    - SVG rendering
    Only then will we ever look at IE again.
    We also need to be clear on the patent situation surrounding technologies such as Silverlight on platforms other than Windows, before we invest any time and effort in such technologies. We don't want to end up supporting a technology that Microsoft plan on attacking on non-windows platforms.
    Microsoft are making a fool of themselves with IE, and severely damaging their reputation with developers. I hope they will offer an upgrade of internet explorer for Windows 2000, XP, and Vista when they have finally sorted out their shoddy rendering library. Internet Explorer 7 was a poor attempt at improving what remains the worst web browser that is still considered current (at least by some).

  14. 90%?? Maybe in the 90's... by Foofoobar · · Score: 3, Informative

    um... hate to tell you this but they haven't been 90% for a LONG time. In fact alot of studies are showing Firefox with 20-35% marketshare, Opera with 5-8%, Safari with 3-5%. Even if you take those lowest figures, the combination of all versions of IE would only have approx. 72% market share... 52% at worse.

    --
    This is my sig. There are many like it but this one is mine.
  15. Expectations, Transparency, Openness by Kelson · · Score: 4, Insightful

    In many ways, IE7 disappointed people. Many users don't like the changed interface. It has compatibility problems with IE6-only sites & apps. (Why this surprised anyone, I don't know.) And web developers wanted it to go much further beyond IE6's capabilities than it ultimately did. So I can buy the idea that they don't want to get people's expectations up too far.

    But there are many possible degrees of transparency. You don't have to take the Mozilla approach where every little change is visible to the public. Over the past year or two, Opera has managed to do a good job of keeping people aware that new stuff is coming down the pike without actually giving away the goods before their announcements.

    Sure, sometimes it means that reaction is a bit underwhelmed when people build up some huge expectation over a hinted-at feature, and it turns out to be something much more mundane (Opera Link, for example -- incredibly useful, but in its current form not revolutionary). But anyone following Opera developers' blogs can tell that yes, they're working on the next version, and could pick up some vague clues as to some of the planned features and capabilities.

    With IE8, no one without an NDA knew whether Microsoft had spent a year on design, a year on coding, or just took a year off. The IE8 blog asked us not to take silence for inaction, but what else should we have assumed?

  16. Re: More like 80% by bunratty · · Score: 3, Informative

    IE usage is closer to 80%, but it is still dropping. Give it a few more years, and it'll be down to 70%.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  17. There has been conversation? by sootman · · Score: 3, Funny

    This conversation [between Web developers and the IE team] seems to have been pretty much shut down...

    It may not have been face-to-face, but for almost a decade, it seems that the conversation between IE devs and web devs has pretty much been...
    Web devs: Fuck you!
    IE devs: Fuck you!

    Why does the IE team hate standards so much? It's not like they don't know how to make things work. IE5 for Mac came out in 2000 and was pretty awesome--it even supported transparent PNGs with nothing more than an <img> tag!

    Dear IE team: thanks for inventing AJAX. Now please go make everything else work. kthxbye.

    (Note: I know for a fact that the IE team has many talented and nice people. They (and we) are just victims of horrible decisions being made further up the chain. So this vitriol is really directed at management.)

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    1. Re:There has been conversation? by 99BottlesOfBeerInMyF · · Score: 5, Insightful

      Why does the IE team hate standards so much?

      Microsoft is a business. Keeping IE non-compliant with standards makes them money. If they complied with standards then all the Web pages and applications would soon do the same, which means there would be nothing stopping companies with Web apps from migrating to something cheaper than Windows and Office. MS's strategy is called "tying" and is illegal for companies with monopoly influence in a market, but MS still makes more money breaking the law and paying off politicians than it does complying with the law, so we're screwed. IE will never be compliant with the specs unless MS loses their monopoly influence.

  18. Developer overload by DigitAl56K · · Score: 3, Insightful

    Usually I find that any company wants an active dialog with its user base. It undeniably helps you make a better product.

    When that dialog does not occur usually it is because the product team are overloaded in terms of the features they have to implement in the time frame that they've been allocated. Sometimes you just don't have time to engage with external entities to the degree that you'd like, or at all. On a product as significant as IE has proven to be in influencing defacto standards, that is quite dangerous.

  19. Definition of "transparency" by Jay+L · · Score: 5, Funny

    When questioned further, Gates claimed that "When I said we'd be more transparent, I just meant we'd use more alpha-blending. You know, like Vista."

  20. Re:Windows hosted on SourceForge by MrDERP · · Score: 2, Interesting

    OT: He did donate billions to charity that Gates made off of the technically illegal monoply. Do you think this has done more harm or good, stifled innovation in computing, helped the world in other ways, Think if it was Larry Ellison running MSFT, that greedy prick would not give a dime away and would be using same anti-competitive stategies. Perhaps the "secret" in ie 8 is that it ties into Sharepoint, OCS etc, the whole .net 3.0 bs & live services, they want you to think your running windows on your [symbian, linux, java, etc] mobile device. Web Servies need to be open and inter operable, hope Android makes MSFT's plan for live services harder.

  21. Re:Why can't I find anything on IE from Google? by The+boojum · · Score: 2, Informative

    It is offtopic, but I'll answer anyway.

    Normally, Google's form uses q as the field for the search term, not searchQ. And btnI is the name of the "I'm Feeling Lucky" button. The link actually has nothing to do with IE 8. It's really just equivalent to an "I'm Feeling Lucky" search for contactlognet, for which Google immediately shoots back a redirect to that site. That site in turn sends you yet another redirect.

  22. Isn't This Part Of A Strategy? by jeff_schiller · · Score: 3, Insightful

    Does anyone else find it odd that Bill Gates didn't know this? I'd like to hear (off the record) from Molly on whether she believes him. Putting my tinfoil hat aside for a minute, it just seems obvious that the silence, which has engendered so much hatred and negativity from the development community, must surely be a part of some type of strategy. And shouldn't Bill be aware of that strategy?

    Even if they haven't committed on certain features or levels of compliancy, this surely does not mean complete silence. Disappointment about delivery of features can be expected, but usually it's tempered with some amount of understanding in the face of transparency and intentions.

    So to me, the silence is a strategy. The choices are:

    - they're not planning on implementing the standards that people expect (CSS, DOM, SVG, XHTML) so they want to avoid fact-based criticism for as long as possible. The longer they wait, the more people may fall in love with Silverlight?
    - they're planning on implementing standards and they want to surprise the hell out of the developers (to have them come rushing and gushing back to the fold).

    Ok, so I'm foolishly hoping it's the latter strategy (I've heard they do have a new layout engine they're working on). But the longer they wait, the more people will expect.

    It must be fairly obvious to them by now that most developers realize just how far behind standards compliancy IE is. Seriously, they are the _ONLY_ major browser out there with: its own DOM, its own event handling, its own vector graphics (VML/Silverlight) and woefully behind CSS implementation. EVERY other browser gives a shot at supporting SVG - where are they with that? They haven't even TOUCHED the spec yet!

    1. Re:Isn't This Part Of A Strategy? by geekoid · · Score: 2, Insightful

      No, I don't find it odd at all.

      IE is one of many, many projects that go one there and I doubt he keeps a detailed day to day list of what's going on.
      This is no different then any other company. Hell, I would be surprised if it was even interesting to him any more.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  23. "I've never understood" by Nicolas+MONNET · · Score: 5, Insightful

    I've never understood why people would want a 3 column layout on the web.


    Not only is this completely missing the point (people want 3 column layout, and they HAVE to implement them anyway with tedious gesticulations), but you're posting on a site with a 3 column layout, for fuck's sake!

    Navigation on the right, content and comments in the middle, links and tools on the right. No, that's not a newspaper layout (which have more than 3 columns, in case you've never opened one!), and it makes at least some fucking sense.
    1. Re:"I've never understood" by Sleepy · · Score: 2, Interesting

      >Navigation on the right, content and comments in the middle, links and tools on the right. No, that's not a newspaper layout (which have more than 3 columns, in case you've never opened one!), and it makes at least some fucking sense.

      You are assuming that the GP and everyone else doesn't take advantage of Preferences to get rid of that useless right column, which I did years ago and don't remember what the settings were. Perhaps the GP also surfs /. as '2 columns'.

      (Personally, I think 3 columns for a SINGLE piece of content is stupid, but using it to frame smaller scraps/elements is perfectly OK. I mean, what are people supposed to do.. be forced into making everything one ROW the width of the screen??)

      Back to the point, I agree that CSS has poor vertical support, which is the big complaint. The counter to that (and it is quite valid) is that you're designing for your monitor at something else's expense, or assumptions other's can' meet. So what, I say PROVIDED that the content remains ACCESSIBLE and MACHINE READABLE.

      People DO want web apps, and they want them to operate like desktop apps. If CSS and DOM can't manage to grow like that, I already know what's going to happen... we're going to see Microsoft push something like 'Avalon' or desktop-app-XML onto the web. And you know what? People will LOVE it.. especially if IE does that and eliminates bugs that USERS care about (note I didn't say developers... MS has called them "pawns")

      It's also interesting that Microsoft has been bickering with the Javascript folks, because Microsoft wants Javascript to receive no more improvements. What's Microsoft working on, and how far outside W3.org recommendations is it? Microsoft has realized that IE7 is pretty close to FF, so they can go pack to what they were working on before the emergency decision to even make an IE7.

      Sorry for the rambling thoughts.. it's late and I'm distracted. Hope this makes sense.

  24. What happened to Developers, developers...? by drew · · Score: 4, Interesting

    Whether Microsoft realizes it or not, they've pretty much lost this round of the browser wars. I don't know what their statistics are these days but even if they were still at 90% it wouldn't matter, because they've lost almost 100% of the mind share that actually matters - the developers. And oddly enough, it has very little to do with their awful support of standards. There was a time not long ago when it made financial sense to develop only for IE. IE was 90% of the market, and an average dev team could cut enough time off of their launch schedule that it more than made up for the number of users that you might lose by not fully supporting other browsers. Their buggy and nonstandard rendering wasn't a big deal, because you could still do reasonably well as a developer coding to the bugs and ignoring the standards.

    Where Microsoft completely missed the boat was on the developer tools. First the Web Developer Toolbar for Firefox and now Firebug. The IE web developer toolbar is an utter joke. The script debugger is awful. Debugging through Visual Studio is pretty nice (if you have it) but it's not nearly as convenient as Firebug's integrated debugger, or even Venkman. It's been two years since I knew a web developer that used IE as their primary development platform. Even when working on sites that only have to target IE (the site that I am writing now will only be used on IE6 - ouch) we still develop on Firefox first and then fix it in IE once it works in Firefox.

    Even if IE8 regains 95% of the market, they still won't have the same control over the web that they had with IE6 unless they drastically improve the developer experience. With IE6 one could argue that it made financial sense to ignore other browsers. As long as it's either to develop in other browsers than it is in IE, Microsoft will never achieve that kind of dominance again.

    (I also have to agree with the poster quoted on the front page the other day. As long as Microsoft shows this level of neglect for IE developers, why in the world would we consider using any of their other technologies. Even as a .NET developer, I have zero motivation to even install Silverlight, much less develop against it.)

    --
    If I don't put anything here, will anyone recognize me anymore?
  25. I hope that someone developes a browser that... by modmans2ndcoming · · Score: 2, Interesting

    I hope someone develops a browser that has a modular CSS enguine and leave the hooks open for anyone to use so you can plug in the CSS engine that you like. Then, CSS support can develop asynchronous from teh HTML engine and movement can accelerate on supporting the standards.

  26. Just when they had it working... by Okonomiyaki · · Score: 4, Funny

    "They seem to have lost the transparency that they had."

    It took them 10 years to finally get PNGs working properly and now they're going to be broken again?