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.'"

21 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 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.

    2. 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.

    3. 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.

    4. 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.
    5. 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.

    6. 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.

    7. 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.

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

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

    9. 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.

  2. 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
  3. 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... :)

  4. 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).

  5. 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.

  6. 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?

  7. 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.

  8. 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.

  9. 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.

  10. 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!

  11. "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.