Re:Stop Building on Corporate-Controlled Languages
by tclancy on Wednesday January 18, 2023 @01:43PM
(#34430988)
I'm not totally sure what that means. VB and the change to .NET are kind of a one-off event. A "VB developer" could mean anything from someone writing VB/ ASP in a text editor with minimal syntax highlighting to someone using a drag and drop editor and never writing code to someone who was really just writing fancy Excel macros. If you want to suggest some of the people working in a GUI only had trouble making the transition, I suppose it's possible, but .NET offered VB.net and VisualStudio still had drag-and-drop editors. So why would they need to be interns? Because people started organizing code differently in folders and linking DLLs?
[ Parent
| on HN ]
Re:Stop Building on Corporate-Controlled Languages
by stcroixx on Wednesday January 18, 2023 @03:27PM
(#34432573)
At the height of VB6 usage, there was no VB.net or Visual Studio. There was the VB6 windows binary that was a GUI form builder and IDE. ASP was brand new and for web development, so there was not much overlap in the dev community. I don't think it was even possible to write VB code in a simple text editor and compile that without the VB IDE. Cold Fusion and Power Builder were similarly corporate controlled and suffered the same fate.
A C programmer during the same time period saw almost no changes to their language or job opportunities.