Macromedia and .NET pt2
Jesse and Brian all agree with my questions reguarding .NET and Macromedia and have some great feedback from the folks at Macromedia. With this information in mind its important to point out that Flex will have a .NET version and its due soon. Macromedia are also working solid on there .NET support. This is great news, but just the beginning.
Jeff Whatcott of Macromedia asked Jesse what the business case for CF running on the CLR is. Jesse's response was that there was none, ASP.NET 2.0 and Whidby would just make it pointless. I disagree, I have reposted my comment here.
Jeff I have to disagree with Jesse on CF running on the CLR, going head to head with ASP.NET may be based on what is known now and ASP.NET may in a .NET developers eyes have more features than CF, but does that mean that CF should never try to compete, no. Simply the reason is that before it ran on J2EE, ASP developers were never courted, they were never given a reason to use CF over ASP. Yes they were compared, but it was not enough when ASP.NET took over. Post J2EE/Jrun and how many .NET developers will take interest of a what is largely seen as a Java product (and how many J2EE coders care about the CLR)? The business case is simple, you need to court .NET developers, its an un-tapped market. Yes that absolutely means competing with ASP.NET on its on own home turf, is that such a bad thing?
The more this debate goes on the more I feel strongly about it. Not trying to compete on the CLR is a crazy thing to do, CF could compete on the CLR, its a lot of work but so what...