Slashdot Mirror


Case Study of Bungie.Net

nmb3000 writes "MSDN recently put up a case study of Bungie.Net (much more detailed than a previous one), the homepage for the creators of the Halo series, and its transition from Perl to .NET and ASP. From the study: 'The Bungie.net site is the online companion to the wildly successful Halo 2 video game for Xbox, released in November 2004 by Microsoft. The site also acts as the community hub for all things related to Bungie games. Built with the Microsoft .NET Framework, Bungie.net serves up more than 4 million pages per day, accumulating 300 gigabytes of online game statistics per month from more than 1 million games played daily.' This is an interesting look into the creation and integration of the very large and interactive website which was voted 'Most Innovative Design' by IGN Entertainment in 2004."

3 of 75 comments (clear)

  1. Re:Works for me by delus10n0 · · Score: 4, Informative

    Blame FireFox-- it's the one rendering it slowly. These bugs have been known about for quite some time:

    Fixed background makes scrolling painfully slow
    https://bugzilla.mozilla.org/show_bug.cgi?id=90198

    slow scrolling in pages with position:fixed elements
    https://bugzilla.mozilla.org/show_bug.cgi?id=20130 7

    Yay!

    --
    Not All Who Wander Are Lost
  2. Poor site design by xeaxes · · Score: 2, Informative

    The site is designed very poorly. The website is no where near W3 compliant HTML/X-HTML/CSS. It runs extremely poorly in Firefox. They don't even serve up a proper DOCTYPE, and for that alone I would not hire their front-end developers for any website design.

    Honestly, for all the back-end work, they should have gotten a GOOD front-end developer who understood design and standards.

    --

    "BEHOLD, CORN!!" - Dr. Weird, ATHF

    1. Re:Poor site design by xeaxes · · Score: 4, Informative

      I'm disappointed that I was moderated as a Troll, when I was not trolling.

      Although I was too brief before, let me expand on other reasons on why the front-end design is poor:

      • The fixed navigation panels on the left side and right side do not function properly when a browser does not have a large amount of available vertical space. The menus become in-accessible.
      • Inconsistent menus. The menus change depending on the section of the site AND the individual story.
      • Does not work properly in all browsers. There are rendering errors all over the place, especially in Firefox.
      • Poorly performing DHTML.
      • Poor color selection. The site will be hard for visually impaired users. Especially the blue on slightly darker blue.
      • The improper use of table elements, and overall ignoring of web standards.
      • The lack of a DOCTYPE is a glaring omission.

      The design isn't god-awful, but it could use a lot of work. It was clearly designed initially with flash over function, and that hurts the it in the end.

      --

      "BEHOLD, CORN!!" - Dr. Weird, ATHF