6 ms·
> VB got a full rewrite into an object-oriented language and the IDE moved further away from the VB6 visual building paradigm. What do you mean by this? Visual
by viraptor 3y ago
> VB got a full rewrite into an object-oriented language and the IDE moved further away from the VB6 visual building paradigm.
What do you mean by this? Visual Studio today has a designer / code editor that works in a very similar way to VB6 that I remember. What do you think is missing?
- deleted 3y ago[deleted]
- reactordev 3y agoVB6’s concept of OOP was different. Sure the same keywords are found: Module, Sub, etc but it was rewritten to run on IL/NET VM. Fundamentally changing it from a COM compatible language to a .Net framework compatible one.
- wvenable 3y agoVB6's concept of OOP was simple enough it could have been translated into .NET and .NET is broadly compatible with COM. I'm certain Microsoft could have made it work. They really needed to consider VB6 as a backwards compatibility target instead of building VB.NET as a modern replacement. VB.NET really has no reason to exist; it's not compatible enough with VB6 but then also includes a bunch of VB6's weirdness.
- gabereiser 3y agoYeah, I agree. They didn't know it at the time but .Net and C# (their answer to java) would take over everything they did.
- emodendroket 3y agoA lot of people who wrote VB weren’t serious/professional programmers and VB.NET was too complex for them. For the serious programmer group, the stink of “VB” tainted it right out of the gate (despite having complete feature parity for a long time VB.NET jobs always paid notably less than C# ones). So it was kind of a compromise that satisfied nobody.
- analog31 3y agoThat was me. I wrote what I affectionately call "crapware," which are small apps that solve a problem but are not intended for use at scale. There was a lot of this stuff, such as little database queries, or hacking together a few industrial sensors with a crude display. Businesses ran on crapware. Maybe they still do. A few thousand lines of code that I wrote for a manufacturing fixture ran bug-free for more than a decade. I remember that just downloading and installing VB.NET was burdensome, especially in the plant where many of the computers were not networked. When VB.NET came out, programmers hung on to their VB6 disks, and kept using it for easily another decade. By the time VB6 really reached the end of the road, its replacements (e.g., Python for me) were up to speed, and free.
- jacquesm 3y agoI came across such a project recently built using FileMaker in 2001 or so. On the original hardware, no less.
- ta1243 3y agoI've written a lot of crapware, still keeps my employer working 15+ years on. Meanwhile "replacement" systems have come and gone, but the users still keep using the crapware. 1) See a business problem 2) Put something together to solve the problem 3) Move On
- MichaelZuo 3y ago
- highwaylights 3y agoHow much time do you have? P-code debugging with fully rewindable edit and continue. A one-true-way event model that was derided at the time but was really just years ahead of its time. Minimal runtime downloads to install apps locally, which also produced tiny, performant executables. The sweet, sweet With keyword. I know, I know. But I don’t care. Just be more aware of your namespaces. Also (and I still don’t understand why we can’t have this in VS Code when VS had this in 1998) object combos at the top of the code file for class and method (admittedly VS proper still has this I’m just grumpy at the regression)
- viraptor 3y ago> The sweet, sweet With keyword. VB.net supports With though? > Minimal runtime downloads to install apps locally, which also produced tiny, performant executables. .net framework 2.7 is guaranteed to be installed by default these days so you can deploy one exe without shipping your own runtime. Yes, officially you shouldn't, but there's so much stuff that depends on it now.
- sn_master 3y ago> .net framework 2.7 is guaranteed to be installed by default these days Yes, but that wasn't the case back in the mid-2000s when VB6 was dying and no one wanted to migrate to VB.Net
- wcoenen 3y ago> net framework 2.7 is guaranteed to be installed by default these days There is no "net framework 2.7": https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies https://learn.microsoft.com/en-us/dotnet/framework/migration...
- viraptor 3y agoTypo - I meant 4.7. Although it looks like they finally moved to 4.8 in w11.
- ShadowBanThis01 3y ago
- deaddodo 3y agoThe visual editor is the same...but even with VB Classic, you couldn't just design a UI and have it magically work, you needed to wire up the logic. That component has a much higher learning curve backed by a particularly more difficult to grasp language.