Quote Originally Posted by axisdj View Post
Lets say I move from vb6 to .net. I would pretty much have to re-write my app for many reasons, the last import I did rendered 80,000 errors in vb.net.
How did you even do that? The number of errors I get caps out at about 100. If you are talking about the conversion tool, that's understandable. It should never have been added because it was so terrible. I never used it, so I don't know. Was that reporting errors way above the cap for the compiler itself? It may well be. Copy and paste often did a better job than that converter seemed to.



So after all that work I would have the same app as I do now, but it may run slower, is not native and open to de-compilation.
You may well have the same app that you do now, but it will likely run faster from what little I can find on Google. In my experience, it will run at the same speed. As for the not native and de-compilation, that's a false fear as I've already stated. Like I said before, I'm currently re-writing a pair of VB6 apps where I don't have the source code. They will work slightly better than before (because of some advances in availability of external data, not due to code changes), but they will look and feel the same. Any code coder doesn't need your source code to re-create your program. The only question is whether or not they will. You're actually a whole lot better off if they do steal the source code, because you then have legal recourse. You have none if they don't have your source and still write a program that does the same thing (unless you patent the ability to click on something).


And at the end I am still at the mercy of MS who killed 100k lines of my code for the sake of OOP purity, and can only run on windows.
So, if that is your reason, why would you pick Delphi? It's another proprietary language. It has a history of breaking changes that is FAR worse than MS. It's not exactly the first word when it comes to cross-platform. And finally, you already have your hardware interface stuff in a C++ dll, which means that you have all kinds of options available.

At this point, you are looking at a total re-write, and just seem to be trying to figure out what to write in. The easy route is .NET, which does give you a route to cross-platform via Xamarin. However, if you are set against that, the obvious choice would be either Java or JavaScript. As much as I dislike JS and feel that it is a language that will change, it is probably the most cross platform, non-proprietary, language in existence today. Yes, it would be utterly different from VB6, but that's not necessarily bad. If you move to something sufficiently similar, you will keep expecting it to behave the same way, so you will keep tripping over what differences exist.



So lets say I re-write to delphi. BTW there is a convertor that would convert many of my classes which would speed things up. So what is the benefit: I get a native compiled app, that is able to be run cross-platform, maybe with better performance, on a language that has not broken previous versions completely like vb6- .net, that is open source, and free, with syntax that is more like vb6 than c++(QT Creator). I really think there is no competition here. As much as I hate moving to delphi because of some of the strange syntax, I think it is the right choice for me.
I certainly don't know Delphi all that well, but what you just described doesn't match what I thought I knew about it or what others have said on here. The language started with Borland and is now Embarcadero. What's open source about that? I also don't see anything free other than a free trial.