Reply to thread

Message

<blockquote data-quote="UngainlyTitan" data-source="post: 5344338" data-attributes="member: 28487">I can't comment on the production and shipping.But on the coding side software failure rate tend to be high. As to the tools alot depends on what they are trying, they could be simply putting a Silverlight UI on the current software (while still making changes for Dark Sun etc). That would allow the tools to run in a browser and in (as far as I know, not a silverlight developer) any OS. The cause of the delay could be it took longer than expected or something more fundamental. Or they could be reworking the whole thing to run in the cloud with a complete new build and not using any of the existing codebase. Hard to know, arguments could be made either way. It would seem to be a waste, unless there are fundamental architectural issue with the current tools that make them a dead end. By building new you loose the benefit from existing bug fixes and get the opportunity to introdouce a whole lot of new bugs.It could also be not software releated at all, there is one developer listed in the mainenance team, if he was off sick for any significant time it would knock their whole schedule out. There is pretty much no redundancy there and I have had a look at there object model in the past. Depending on the quality of documentation it could take a while to get a replacement developer up to speed.</blockquote>

[QUOTE="UngainlyTitan, post: 5344338, member: 28487"] I can't comment on the production and shipping. But on the coding side software failure rate tend to be high. As to the tools alot depends on what they are trying, they could be simply putting a Silverlight UI on the current software (while still making changes for Dark Sun etc). That would allow the tools to run in a browser and in (as far as I know, not a silverlight developer) any OS. The cause of the delay could be it took longer than expected or something more fundamental. Or they could be reworking the whole thing to run in the cloud with a complete new build and not using any of the existing codebase. Hard to know, arguments could be made either way. It would seem to be a waste, unless there are fundamental architectural issue with the current tools that make them a dead end. By building new you loose the benefit from existing bug fixes and get the opportunity to introdouce a whole lot of new bugs. It could also be not software releated at all, there is one developer listed in the mainenance team, if he was off sick for any significant time it would knock their whole schedule out. There is pretty much no redundancy there and I have had a look at there object model in the past. Depending on the quality of documentation it could take a while to get a replacement developer up to speed. [/QUOTE]

Verification