VB6 is DEAD!

[Schmidt]

That's just a whole mass of self-righteous nonsense ...

Because?
See, I've already brought the reference to the Anderson-tale:
http://en.wikipedia.org/wiki/The_Emp...se_as_an_idiom

And BTW, what you just did is listed under: "The Courtiers Reply":
http://en.wikipedia.org/wiki/The_Courtier%27s_Reply

...intended to puff yourself up by insulting others.

Nah, come on ... where was the insult?
What shoe did you choose to put on (aka why do you *feel* insulted)?

I mean, I've calmly explained just my point of view... if you think that I'm utterly wrong,
then there's no reason to feel insulted - just laugh at me - or label me "backwards" or
"unwilling to learn new things" or just "VB-cry-baby" or whatever creative (and of
course non-insulting) attribute for a VB6-developer comes to mind *this* day.

Sure, you can look at the past and decide that your decision was the right one ...

That's not the point.

...and that it means that you were smart enough to see the future. Try knowing what is coming BEFORE

And that also is an allegation and was not the point.

There's a whole lot of other VB6-devs like me, who simply decided what they thought was right for them
to do (at that point in the past) - and "unwillingness to learn new things" or even more ridiculous:
"fear of OOP-concepts" was the least, believe me.

Most of us wanted to use a (simple to feed) native-compiler further - MS supported
the (fullblown) concept for C++ developers further in all those years, and preferred
native compilation themselves in their products - so there was nothing wrong
apparently, in using the concept ourselves.

[a long-winded explanation about Java and VM-based concepts...]

And no, Java didn't really appeal to me either (for the same reasons) - otherwise I'd
have supported concepts like Jabaco (VB6-Code to Java-ByteCode) and "moved on"...

You've bet on a horse that has now been shot. Were you smart enough to see that coming?

I've not bet on anything - I've just made a decision not to use some technological
concepts I had no use for and never liked.

Instead I've decided to use the compiler (I was already happy with) further -
and invested my time into things which I considered to have more long-term-
value, should MS decide to not support VB6-compiled Apps on future OSes...

Sometimes the decision "to wait until some things become more clear" is not
unwise, you know?
What I'm pointing out to you is simply, that I cannot understand why you
*still* mark people who made such a decision, as "living in the past" -
*especially* after experiencing all those confusing decisions and the latest
back-paddling maneuvers on the part of MS over the last years and months.

If somebody is apparently acting confused, then it would be a fault to
follow along unquestioningly (as you prove yourself, by not adopting
the Metro-concepts wholeheartedly, when I look at the posting-count
there) - many VB6-developers simply started a few years earlier, to act
reasonable, waiting things out, before investing time into "adventurous
things".

Olaf