Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="AbdulAlhazred" data-source="post: 5484531" data-attributes="member: 82106">Right. Honestly I don't think IE6 is the big factor here anyway, nor IE7, which is actually at this point less prevalent than 6. The REAL big consideration for a development group is tooling, build process, and just overall development work process. If you're a MS shop, which WotC most certainly is, you REALLY do not want to propose retooling your dev process at the start of a major critical line of business application development cycle with an aggressive schedule. There's a reason programmers stick to their familiar tools like glue. MS Visual Studio (or any other modern IDE) is a VERY complicated piece of software, many times more complex than say Office. It ties into the rest of your shop's tooling in a 1000 different little ways. The development process is going to involve expertise in a lot of different tasks and rely on a very intimate knowledge of many different things for success. OCB isn't the worlds most complicated application, but it is complicated enough. It has to serve a very high load, is locked into working with other existing tools and resources and existing data formats, and is going to be utilizing probably 4-5 different languages that your developers have to be able to understand and use well.So you stick with your tools and do what you know how to do. For good or ill they built a team that knows how to execute using MS technology. That decision was made a long time ago and unmaking it really isn't an option. I doubt there was even one hour of debate as to what front end technology to use. It was Silverlight or nothing. Switching would have been insane. Any senior tech lead that had even suggested it would have been out the door in an hour flat. That's just how it goes. When the dust settles and there's time to go back and experiment with how to integrate other tools and technologies into their application stack, and a good strong business reason to do that, then they probably will. In the meantime they had an OCB to get out the door. They did it. Notice, it was still a rough job. If they'd have gone and done it in say HTML5/JS we'd be waiting another 6 months, and there'd not have been old CB updates either, because every man is on the job 24/7 death march style.</blockquote>

Verification