Metamorphing Machine I rather be this walking metamorphosis
than having that old formed opinion about everything!

The long road to relieve an angry heart

A few months ago I e-mail interviewed someone for the very first time!
It got me thinking who else I would like to interview, and the first name that popped up was Bruce McKinney.
For those who don't know who he is, he's written the seminal book Hardcore Visual Basic. It was a must-read for anyone seriously invested in Visual Basic.
By reading him, one can be certain that not only this guy understands Visual Basic's history, but he also loves the language.
When MS released VB.NET, Mr. McKinney was not happy, to say the least. (You can read his rant here.) So much so that he simply stopped using Visual Basic at all.

As the years went by, I was lucky enough to read some more instances where he shared his opinions about VB.NET (here, here, and here.)

His most recent involvement in anything VB-related was a few years ago.
These days it seems he's much more into politics than programming.

Anyway, I admire Mr. McKinney. That's why I was kind of shocked when I re-read "for the first time" his statements that VB6 "(...) was a bad foundation for adding new language features." and that "(t)he original VB was one of the coolest hacks in history, but still a hack."

This man forgot more about VB6 than I could ever hope to learn during my whole life.
My interpretation of what he said is that VB6's next version would have to break things, no matter what.
Like many VB6 programmers, I felt betrayed by MS' galore of incompatible changes to Visual Basic.
They said they did not break the language, but fixed it. I did not buy it.
Even after reading what their reasoning was, it didn't matter. They were mistaken. Period.

But... We're talking about Bruce McKinney here. So, maybe, just maybe, I was... wrong?

Another thing that caught my eyes was this article.
It says, among other things, that .NET and C# are a tangled mess and being evolved at such a neck-breaking pace that even seasoned developers are at a lost on how to navigate it, leave alone beginners.
In contrast, MS announced some time ago that it does not plan to evolve Visual Basic.NET as a language any more.
Yes, the same MS that created such beloved languages like VB itself, C#, F#, and TypeScript, is sunsetting VB.
It was disappointing. After a long and slow decline, we got the confirmation of something we always knew: They don't care about us or "our" language.
But, seeing how C# is becoming bloated and more bloated with every release, can we take VB's "stability" as a... good thing?

For many years I've held a grudge against grunge music because it's "stolen" Heavy Metal's place.
It took me a lot of time and maturity to understand that that's just how things are. What's new becomes old, and then there's something new.

And now, given these two points above, I'm starting to consider if the time to let my heart heal from all this long anger has finally come.

Next week I tell you about my experience using B4A.

Andrej Biasic