3 ms·
VB/VB6, with some Clipper and Foxpro mixed in. Switched to c# instead of picking up vb.net - in retrospect a good call.
by ejb999 5y ago
VB/VB6, with some Clipper and Foxpro mixed in.
Switched to c# instead of picking up vb.net - in retrospect a good call.
- zwieback 5y agoClassic progression - some of us came from VB Classic to C# others from C++ (at least in the Windows world). Now we're all one big happy family.
- kingcharles 5y agoEven though I grew up with C as a kid, I still prefer VB.Net over C# as I believe the code is far more human-readable and less prone to technical errors - BUT, there is just no support for VB.Net. I got stick of having to convert code snippets I would find and this year I finally bit the bullet and moved to doing everything in C#.
- drittich 5y agoSimilar route here. I went from VB classic to JScript on the server (and client, so was doing isomorphic JavaScript 19 years ago!) and then to C3 a few years later.
- hackerfromthefu 5y agoWell I used VB4-6 and Delphi 5-6 extensively, and my experience was Delphi was lightyears ahead of VB, and I say that as someone who was deeply familiar with both and made heavy use of Dan Appleman's Visual Basic Programmer’s Guide to the Win32 API. It sounds like you were maybe using it at a fairly surface level, for which VB was good because it was highly approachable sure, but the wheels fell off pretty quick when you had to push it. Delphi was beautiful because it made the easy stuff as easy as VB, but the hard stuff was still easy where in VB it was either impossible or required dropping down to Win32 APIs or calling other languages.