On Feb 19, 10:33 am, Fernando Cassia <[email protected]> wrote: > Thoughts? Comments? Expletives? ;-)
The main question: Why should somebody with a Visual Basic app switch? Does (s)he get with Java everything that's in Visual Basic? If not, there's no reason to switch. If everything you have in Visual Basic is in Java too, then there still is no reason to switch. They would only switch if there's something in Java that's important to these people and that they can't get in Visual Basic, and if the switch is easy. Now Visual Basic is a mature ecosystems, so I doubt that such a thing exists. Plus it's Windows, so the natural tendency is to migrate to .Net. As often, Joel on Software says it best: http://www.joelonsoftware.com/articles/fog0000000052.html Sun tried this once before with Java Creator. I don't think Sun understood why people switch software or don't switch, otherwise they wouldn't have tasked Java Creator to lure millions of Visual Basic programmers into the Java camp (http://www.builderau.com.au/program/ java/soa/Sun-to-hand-out-Web-ready-Java-tool/ 0,339024620,320283319,00.htm). Just by looking at it you could see the problems: Java Creators made web apps where Visual Basic makes Windows apps, they needed an application server to run on, it couldn't use any of the Visual Basic components, it used a different language, and it probably couldn't import most Visual Basic programs flawlessly. So you had all these huge barriers to entry, and the result was predictable. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
