[BC] Bye Bye IE6

[Robert Meuser]

In Microsoft's case it is marketing and education. The typical path they 
have taken is to introduce new products that are initially cheap and in 
the case of compilers and DBs, easier to use than other tools in the 
market. This causes in house development to tilt towards those products. 
Pretty soon it is difficult to not have a Microsoft shop.

  Not meaning to insult anyone but my guess is that a lot of broadcast 
software was developed at least in part by programmers who were 
specialized in broadcast operations first and computer programmers 
second and used the more user friendly MS development tools. That is one 
reason that such a high percentage of BC software requires a Microsoft 
OS and MS only shops come into being.

I have had Mac and PC shops running on Novel networks since the late 80s 
and I will admit to doing what I described above as well. We rolled our 
own digital audio system and it was MS based even though we had MAC 
audio workstations in the house. The main reason - we could develop 
hardware I/O boards and easily write directly to them under DOS while 
the MAC interface was less accessible and more complicated. We also 
fiddled with QNX but in those days supporting hardware that was not 
approved was quite difficult.

Of course modern Microsoft interfaces are probably on par with MAC as 
far complexity is concerned. Most people are constrained in either case 
from straying too far from what established API's allow.

On 12/19/11 3:17 PM, Cowboy wrote:
> On Monday 19 December 2011 01:50:19 pm Mike McCarthy wrote:
>> The same can be said for many things.  And the monoploy (or at minimum a
>> limited polyopoly) you describe is applicable is many instances and
>> business.  It's not just OS and computing.
>   True, but how does that excuse dedicated Microsoft shops when there
>   are much, *much* less expensive, and more reliable, alternatives ?
>