4 ms·
I know exactly what the differences are between VB5/6 and VB.NET and also saw the futility of adopting VB.NET for greenfield projects. I am no spring chicken.
by teh_klev 5y ago
I know exactly what the differences are between VB5/6 and VB.NET and also saw the futility of adopting VB.NET for greenfield projects. I am no spring chicken.
In the 90's I was neck deep in the land of COM/DCOM and CORBA. Our proof of the pudding, for the stuff we were building to talk to CORBA endpoints, was whether our VB5/6 apps could consume our bridge libraries and start passing sane data backwards and forwards with some janky J2EE horror show. And then we did the same with .NET1 (beta) via COM Interop to those libs etc etc. This is why I know the subject matter well, even if it is 20+ years ago.
Anyhoo, that's my appeal to authority, but I'll agree to disagree.
- laumars 5y agoI was a freelancer back then. So worked across several different stacks. VB6 was my goto for RAD. Delphi for performance. Wasn’t keen on C++ back then and the less said about Java (with regards to desktop applications) the better. I remember hating .NET v1 beta but I can’t for the life of me remember why. C# has definitely grown on me since but ironically these days I don’t touch Windows (nor even write GUI applications).
- teh_klev 5y agoAye, I rarely touch desktop stuff these days. Most of my efforts now get deployed into our Azure environments these days, which I have to confess I bloody love. I used to work for an ISP and Webhoster back in the 2000's building out provisioning and billing apps. With Azure I sure don't miss having to manage fleets of physical servers any more, even the big iron VM boxes we ran.