3 ms·
I worked for a shop that was heavily invested in Visual FoxPro, after that time had come and gone. I spent a few years switching most stuff to Python and Postgr
by kstrauser 7y ago
I worked for a shop that was heavily invested in Visual FoxPro, after that time had come and gone. I spent a few years switching most stuff to Python and PostgreSQL, then moved to another city. When I checked in with some friends from there to say hi, I found out that they'd replaced all my "weird Python stuff" with good, standard VB.Net (starting in 2013). I didn't know whether to laugh or cry (with strong leanings toward the latter). It's too bad. I love that company and the people there, but I'd like to smack the person who convinced them to go for that particular rewrite, or at least make fun of them in public.
- eitland 7y agoThe obvious choice for anyone who has tried a few languages should probably have been C#, but personally, if it was my choice to make and the team was experienced in Visual Foxpro I'd probably choose VB.Net if they wanted it. The alternative would be C#. Full disclosure: Languages sorted by when I learned them: - Basic - Visual Basic - C - Assembly - Java (well, I "learned" that I was hopelessly ineffective with it. Still got a B.) - Javascript - Python - PHP - AutoHotKey - Java (actually learned it) - Perl - Delphi - C# - VB.Net Reasons: Once I actually understood the value of a real typed language there's no way I'll go back except for scripting and small one-offs.
- kstrauser 7y agoThing is, there was only one person there who was really maintaining the VFP stuff. We'd already done the switch for everything else. I agree about strongly typed languages. I'd never give Python and its strong typing to switch to a scripting language.
- smacktoward 7y agoThe hitch there is that there's not so much an ecosystem for individual Microsoft products as there is a Microsoft ecosystem, where all the products are puzzle pieces that snap into each other. So if you're in that ecosystem and a Microsoft product you're currently using stops being available, there will be a strong gravitational pull drawing you towards other Microsoft products to fill the gap. You can fight that tendency by bringing in non-Microsoft products, but even if they're much better than the MS alternatives, MS people are always going to feel weird about using them. It's like telling them to defy gravity by standing on a chair all day.
- jonathanlydall 7y agoI think his dismay was that they chose VB.Net over C# for their rewrite.
- kstrauser 7y agoYou're right. If they'd picked C# (again, in 2013 or so!), I would have been disappointed but understanding. Hey, it's not my project anymore and you've gotta pick what works best for you and your team, not to satisfy my preferences. But to finally be on an open non-Microsoft platform, and then to change back to it for VB.Net? That's just mystifying.