Quote Originally Posted by FunkyDexter View Post
I assume that was sarcasm so I'll respond. I've used your definition of "what matters". You've laid it out enough times including in these two sentences.


I don't think I've put an interpretation on that or spun it in any way. You've been quite clear.

As for what MS thinks internally, again, they've been extremely clear and explicit. They're not bringing back VB6. They're not enhancing VB6. They've given a very public and lengthy statement to that effect. Again, I don't think I'm putting any interpretation or spin on that. They've been quite clear.
Yes, it was sarcasm, glad you found it. My english is getting better.
I know they are not bringing back VB6, what I was hoping is that they could develop it to the next level, not with an "interpreted" VB like in the old days.

So given that you know this:-
...is not available as an option (at least, not if you're expecting MS to deliver it) I ask again: why don't you switch to something else?

As I see it here are your options:-
1. Continue to use VB6 and "be docked in the past (no 64-bit, no full unicode, no OOP)" (your words, not mine)
2. Switch to an alternative language (I'd recommend .Net but I know you don't agree so source an alternative yourself).
3. Wait for someone else to update VB6 (It won't be MS but there are various Open Source projects out there that might come to fruition)
4. Update it yourself or get involved in an existing Open Source project

This, however, is not an option:-
5. Wait for MS to update it

So now you know what your options are (and aren't).

Pick one.
Good advice, I could never get there by myself, thank you.

PS: Like many others you keep saying that .NET is a language, but it isn't. It's a bloated "framework", just like women bags.