4 ms·
I am very thankful for MS to abandon VB Classic and suddenly destroy years of my work on the merit of an egoistical businesses decision. After that I valued the
by holri 7y ago
I am very thankful for MS to abandon VB Classic and suddenly destroy years of my work on the merit of an egoistical businesses decision. After that I valued the freedom of software as no 1 priority, rebooted and never looked back.
- lopmotr 7y agoThe tool to port to .Net wasn't as bad as the article claims. I ported a pretty big messy WinForms application which was somebody else's years of work and today it's even more successful than ever. It took maybe a week or two to work through the many 100s of errors, but none were that difficult. I had already learned not to rely on proprietary binary libraries that were popular back then because you knew they wouldn't be supported in the future when you'd need them. I'm very grateful for VB.Net. It's much cleaner and safer than VB6. My biggest wish now is for a way to port to C# piecemeal instead of doing the whole project in one shot.
- holri 7y agoI never tried to porting tool. Because porting to another proprietary platform did not make any sense to me after I experienced first hand what non-freedom means. I learned my lesson the hard way.
- cm2187 7y agoHonestly there were many ugly things in VB classic that the destruction of backward compatibility fixed. Like the useless and inconsistent "set" keyword. Parameters being byref instead of byval by default. Collections being inconsistently 0 based or 1 based. Parenthesis for methods called as function but not as sub.