News for hackers. Stuff that matters.

A comment on The worst of the two worlds: Excel meets Outlook. Parent comment

Re:The worst of the two worlds: Excel meets Outlook by bsder on Saturday February 13, 2021 @08:52PM (#26128953)
> Then acceptance (and awe) - “Excel is UI, a DB, and business logic all wrapped in 1 thing that everyone already knows how to use.”

We had a programming language that matched that description ...

Visual Basic 6 -- and Microsoft killed it because it wasn't making them enough money.

[ Parent | on HN ]
Re:The worst of the two worlds: Excel meets Outlook by pjmlp on Sunday February 14, 2021 @05:06AM (#26131012)
They did not kill anything, they brought them into VB.NET, and I can tell many VBA users are quite happy to transition into VB.NET, as I experienced in a couple of life sciences corporations.

Having used VB back in the day, the only thing missing are a couple of people still not getting that VB.NET with Forms is just the same deal, even Me is available.

[ Parent | on HN ]
Re:The worst of the two worlds: Excel meets Outlook by bsder on Sunday February 14, 2021 @05:40PM (#26136973)
Except that all the little controls and plugins DIDN'T transition to VB.NET--and they're what made VB6 useful to common people.

And the hot code reload in VB.NET is nowhere near as useful as it was in VB6--and that was how common people debugged code.

I can go on and on.

VB.NET was not a useful replacement for VB6. I still know tons of businesses running VB6 code and, when they finally have to migrate, it won't be to VB.NET.

[ Parent | on HN ]
Re:The worst of the two worlds: Excel meets Outlook by pjmlp on Monday February 15, 2021 @01:48AM (#26139854)
Not enough money to buy little controls from Telerik, ComponentOne, GrapeCity,....?

Interactive .NET sessions have been working for several Visual Studio releases, at least all the way back to 2010.

The only issue is the anti-VB.NET atittude from some VB circles.

[ Parent | on HN ]