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."
I guess it's innovative to not render properly in Firefox.
For once something has come out of msdn that doesn't read like a blatant advertisement. This study is open about the amount of time that it took to create this site, although the forum development and security testing was not included as it was outsourced to other companies. As a non-MS developer I'm naturally wary of studies like this but seems like a competent piece of work although I thought it was spoilt with the simpering hero-grams at the end... "Without the ease of .NET we wouldn't have even started"...ick!
Your logic doesn't make any sense-- they're perfectly valid HTML/CSS commands. Internet Explorer doesn't choke on them (and it happens to be the most popular browser right now, and has been for quite some time..)
FireFox should fix this soon, as it isn't just bungie.net that is affected.
Not All Who Wander Are Lost
No...we understand that it is the 'expected result' (the Firefox bugs).
But there are two ways of thinking on that:
1- programming for/around these bugs is stupid. Program it the right way, and wait for the browsers to fix themselves. For instance, when Netscape 6.0 came out, I did not modify all of my pages to display in that piece of crap. Because 6.0 really was a piece of crap...Like the rest of the world, I realized that Netscape Navigator was a totally marginalized piece of software, and it was their problem to fix the bugs- which they mostly did in 6.1
2- If the company that you work for owns a huge chunk of the browser market, you make sure it works in your browser...and like I said before, if it makes your competition look bad- even better.
I don't think your verbal talent is lacking- I think it is your understanding of human motivation. What in the world would cause a Microsoft company to modify one of their sites to operate with a buggy browser, made by the competition? In this case they can even say 'well, we just designed it to the standards...'.
Do you really think they give a shit if they could fix it for Firefox? Why would they spend even 20 seconds on that?
And if you are thinking, "because then more of their customers could view the page" then you REALLY don't understand what is going on.
No reason to lie.