That’s a great question! I’ve always said that REALbasic is a good choice (for the most part) for people wanting to migrate from Visual Basic 6. The article points out that for most applications, they should probably stay in VB6 unless they’re highly visible in the organization or if they need something specific to .NET.
And therein lies the rub of migrating from one development environment to another. There’s pain involved. In fact, a lot of pain. Regardless of how good an automated conversion process is, it will always miss something and that something might be very subtle. So subtle in fact that it might take months to find it, or even worse, after it’s been released (because after all, who has time to properly test anything these days?).
Hiring a developer or even a service can be very expensive. One VB6 to .NET conversion service charges $1 per line of code. A VB6 project I worked on for years had 950,000 lines of code. There was no way that they could afford to get it converted to .NET because they didn’t have $950,000 sitting around. Doing it themselves would have cost them a minimum of a year with a team of experienced .NET developers. They thought they wanted to go to .NET but yet they could never give any good reasons why they wanted to go .NET other than it is the new ‘thing’ to code in.
Let’s face it, VB6 is still a capable language and while language purists might dismiss it, I’ve done and seen a lot of awesome code in it. Sure, to make a modern looking application you have to go through some hoops but it’s not that hard.
The situation with converting to REALbasic is similar to that of VB6. Unless you have a need for RB’s strengths, such as wanting to support Macintosh and Linux users, you’re probably better off staying in VB6. I’ve had quite a few people amazed at how much it costs to convert from VB6 to RB. For some reason they think it should be ‘easy’ because they both have the word BASIC in their name. Nothing could be farther from the truth: RB and VB are completely different languages and frameworks and only a skilled developer can convert between the two.
Converting from VB6 to .NET is always an option. If you do that you’re stuck with Microsoft for another decade and you’re still not supporting Mac and Linux users. REALbasic should be considered an option if you want to migrate away from VB6.
What are your thoughts?