No troll. What are the (legitimate) reasons people are still using VB6 ?

[DllHell]

- reflection ... is already built-in (in any VB6-produced COM-binary)

You have a class in your vb6 project. How do you dynamically list props and their types or invoke methods? You can't which is a pain point if you want to do it

- better oop ... what exactly are you missing (remember that "inheritance is discouraged from" in the meantime)

this has been beaten to death. for people that want oop, it is missing.

- function overloading ... I find the concept of Optional Params and ParamArrays far better suited for the task, seriously

I've used both and the ability to have functions that take clearly defined objects or types is much nicer to look at. But you can still use paramarrays in .net so you have twice as many choices

- consistent 0 based arrays ... that's the default I thought (I sometimes use other LBounds, but rarely - but am glad to have the choice)

for some things, but not others. And the fact that there is confusion about this means it was definitely a mistake.

Oh, they are - believe me...
Every ".NET-WinForms-App" will have to be rewritten at the same time VB6-Users will have to "switch to something else".

.net <> winforms. And winforms is going open source (https://www.hanselman.com/blog/Annou...penSource.aspx).