Three words: Cost benefit analysis. Suits don't generally realize the value in Unix. Harris is also not the greatest shop around. They mostly leverage large numbers of medium talent in engineering. These are the kind of people who have been force-fed MSDN all their training lives, and so what should be a quality assessment become a matter of familiarity. Furthermore, they're probably just going to get another contract out of fixing the original problem.
Theis happens all the time. Until there an organized effort to support widespread UNIX development, it's going to be hard to take down MSDN, which makes a buisiness out of sending lots of information and software to anyone with a subscription. Much like ADC has become. It wouldn't hurt for Apple to organize a generic series of API's, code samples, and information packets about generic UNIX programming, and built a developer network out of that, but as far as I know it hasn't happened yet.
Comments
Originally posted by hegor
Read link,
Enough said.
http://www.techworld.com/opsys/news/...fm?NewsID=2275
Three words: Cost benefit analysis. Suits don't generally realize the value in Unix. Harris is also not the greatest shop around. They mostly leverage large numbers of medium talent in engineering. These are the kind of people who have been force-fed MSDN all their training lives, and so what should be a quality assessment become a matter of familiarity. Furthermore, they're probably just going to get another contract out of fixing the original problem.
Theis happens all the time. Until there an organized effort to support widespread UNIX development, it's going to be hard to take down MSDN, which makes a buisiness out of sending lots of information and software to anyone with a subscription. Much like ADC has become. It wouldn't hurt for Apple to organize a generic series of API's, code samples, and information packets about generic UNIX programming, and built a developer network out of that, but as far as I know it hasn't happened yet.