3 ms·
> the fix, C#, came too late Because it wasn't a fix for VB - it was just the answer to Java. Somewhat unfortunately, that "answer" swallowed the whole MS dev
by toyg 4y ago
> the fix, C#, came too late
Because it wasn't a fix for VB - it was just the answer to Java.
Somewhat unfortunately, that "answer" swallowed the whole MS development ecosystem, and the VB world never really recovered.
- david927 4y agoI'd argue. I think it was both. Yes, it was an answer to Java but remember, VB apps didn't scale. They exploded at scale. And no matter how much you, as an organization, promised yourself you wouldn't scale up that VB app, it kept happening. So it was also an attempt to try to fix that.