r00ty wrote:Blai wrote:I like it how 90% of the people who commented on this thread see themselves as part time software developers and part time lawyers.
not me, I see myself as a full time software developer. Lawyer, no. But when I post legal opinion I make my lack of credentials clear.
you must be among the 10% that don't post crap without any sort of knowledge then.
I'm also a software engineer, and I'll never criticize someone else's work or decisions due to the fact that it's not my work and it's not my decision what to do with it.
allow me to quote one of your sentences: "I call bs on their claim to have lost code. "
WoW in it's early state was riddled with bugs (a quick glance at the patch notes will show you the insane amounts of bugs fixed early on).
If you had a project you worked on for years and you reached a state where you fixed 99% of the bugs (it can never be 100%) and everything works flawlessly on your updated project - would you keep the old, riddled with bugs, incomplete product while you have a better working one?
although I never worked in a big organization like Blizzard, I'm pretty sure there is no point keeping a database and code from 1.0 after they applied SO many changes to it to make it work better.
Also note that Blizzard never intended to go back with their product, so I do see no point in saving that OLD code. World of Warcraft is a game that constantly gets updated and more content is added to it over the years. They never developed a different product, they simply updated their core game to this level.
Again, before you decide to bash me over my inexperienced OPINION, try thinking outside the box and look at the bigger picture: there's no World of Warcraft and World of Warcraft: The Burning Crusade - It's the same game being updated over the years.