2 ms·

VB6 does not equal VB.Net. I personally know developers who switched careers after Microsoft transitioned to .Net. I worked with them around 2001. They didn'

VB6 does not equal VB.Net. I personally know developers who switched careers after Microsoft transitioned to .Net. I worked with them around 2001. They didn't understand OOP concepts and were not interested in having to relearn everything. It felt totally unfamiliar and strange to them. Microsoft tried to make the syntax somewhat familiar, but at the end of the day .Net is an object-oriented programming language and VB6, try as it might, was not. And that was too steep of a hill to climb for them.

canadianfella 4y ago
[dead]
geoffmanning 4y ago
Seriously? Good riddance to the "developers" that couldn't adapt. The job market is littered with garbage developers, and it's exactly the type of developer that can't adapt to a new language or style of programming that are the ones that aren't really meant to be a developer. Hopefully they found their niche in the economy. - Ex-VB6 programmer turned VBA programmer turned VB.NET programmer turned C# programmer turned Python programmer turned Javascript Programmer (and all the non-pro projects and gigs inbetween, C++, Go, Elixir, Java, Kotlin, etc).
pjmlp 4y ago
It did not on version 1.0, but most of the differences were fixed in later versions. As if COM as used in VB6 isn't OOP.