![]() I never could have imagined being able to read the source code of. NET community and have watched it grow and thrive into what it is today. As far as I’m concerned VB.NET is a dead language now and I was proved right. At least, I’ve never seen a company start a new project in VB.NET in years. ![]() Any developer with less than ten years experience probably hasn’t even seen VB.NET. However, they’re always legacy apps on their last legs, where there’s maybe one old programmer keeping it from falling apart and nobody else knows how to support it. Sometimes even on rare occasions a website written in classic ASP. NET Framework application written in VB.NET. These days I still come across the odd old. NET compared to VB6 would eventually win them over. In the end, the speed, structure, peers and power of. Sure I came across the odd stubborn senior that refused to accept the inevitable, but critical mass and their management usually helped them along the way. ![]() The more they used C#, the more they loved it. I also believed that for the web, C# was closer to JavaScript and that had become the de facto browser scripting language, making the context switch easier for website developers. Every piece of documentation Microsoft put out and every code sample they provided, pushed, promoted and prioritized C# over VB.NET and I was convinced that C# would eventually dominate VB.NET. However, I was convinced that C# was the future, and I’d impress this on the management teams that would hire me. It felt closer to what they were used to. Or they had come from classic ASP (VBScript) where you didn’t have to compile your code. The truth was that many VB6 developers had come from background of VBA, working with Microsoft Access in corporate IT departments. Everything to them felt foreign and wrong. Subroutines and functions were backwards. They wanted their IF’s, ELSE IF’s and END IF’s. For VB6 and VBScript developers C# was a monumental paradigm shift. When I would start with a new team the initial responses from developers were always the same. I’d developed a reputation (purely by chance) for migrating teams to. I had also previously worked at HP’s rival beforehand. NET into several companies with this kind of tech stack. I was a very early adopter of C#, became a bit of an evangelist consultant and introduced it with.
0 Comments
Leave a Reply. |