AdmundfortGeographer
Getting lost in fantasy maps
Because mine is not a month old. It is in fact about two and a half years old.AllisterH said:Why can't yours switch between Mac and Windows?
Because mine is not a month old. It is in fact about two and a half years old.AllisterH said:Why can't yours switch between Mac and Windows?
Then it's good to know that they are not developing this in-house. If people would just read the whole blog entry (from Didier Monin's blog) that was cited a number of posts back, you might find some actual fatcs about this.Delta said:That shouldn't be too much surprise, because WOTC isn't really a software development house in the first place, <snip>
AllisterH said:Not to be rude, but I know my Mac has dual support for Windows and can run any Windows-based program.
Why can't yours switch between Mac and Windows? Mine sure as hell can. That said, I did buy it only last month....
The argument is not that cross-platform has no extra cost. The argument is that the costs to make it cross platform are fully realized and more by the extra customers when programmed with significant reusable code. That is exactly the case.Oldtimer said:I'm also amazed by the number of people claiming that cross-platform has not extra cost.
It's not any more expensive to create a Web app that works using Java or something else cross-platform. This was a decision made by WotC, not by economics or the realities of technology.Mistwell said:I'm not really addressing the issue of convenience. The cost of making something compatible for a second platform gets added to the general cost of a product.
You know, we just might have done that, we might even like to do it now . . . had someone posted the link. Otherwise, you know, the reading up on it all is a bit, uh, challenging. Thanks for the link. Uh, wait . . .Oldtimer said:Then it's good to know that they are not developing this in-house. If people would just read the whole blog entry (from Didier Monin's blog) that was cited a number of posts back, you might find some actual fatcs about this.
Blizzard's Mac team is also their foreign region localization team. They don't have to hire any additional people to do the ports and once the game has shipped, they would either have to lay people off until the next game gets to the localization stage -- then find, hire and retrain them -- or find something else for them to do. Having the Mac guys be on team to do Mac tweaks as needed in between major releases has ended up saving them money overall.Mistwell said:WoW PC users do in fact subsidize the Mac users on that system, with the increased price they pay for the product. Regardless of planning, it takes time and resources to convert it to use on a Mac, even if planned correctly from the beginning. Let's not deny that fact.
Blizzard has been creating Mac-compatible games for more than a decade.When you are dealing with the HUGE numbers involved with WOW
Oldtimer said:Their partner is Radiant Machine, which is a part of SolutionsIQ. The people they have committed to the project at Radiant Machine are not "straight out of college". Do a bit of research before you decide that the sky is falling.
Mistwell said:For the most part, a lot of them can do just what you're saying. They just don't WANT to do it.