2 ms·
As a system programmer who used VB6 as a glue or ochestrator (early 2000s) of low level components I say the only important flaw I found was on its single thre
by wslh 4y ago
As a system programmer who used VB6 as a glue or ochestrator (early 2000s) of low level components I say the only important flaw I found was on its single threading model.
In the 2000s VB was rusty but amazed me when I remembered that pedantically (shame on me) criticized the VB developers of the 90s against the C/C++ hardcores. It was on high school though. Nerd issues.
- rprospero 4y agoI also remember my dismissive high school analysis of VB and wouldn't mind an opportunity to slap my younger self for blind dogmatism. However, I also remember that the fight was a two way street. My high school had classes in both VB and C++ and there were multiple calls from the local business community to cancel the C++ class. There was no reason to teach a dead language when knowledge of VB was enough for a lifetime career. Especially with the emerging web, where companies would need a ready supply of VB script developers and ActiveX control creators for their sites (JavaScript would be deprecated once the last five people using Netscape came to their senses).
- fatnoah 4y ago> As a system programmer who used VB6 as a glue or ochestrator (early 2000s) of low level components I say the only important flaw I found was on its single threading model. As a developer cutting my professional teeth in the late 90's / early 2000's, VB was amazing for building utilities and other bits of software run by individuals on their machines. When we tried to reuse components built for those applications in our web applications, issues with the threading (single threaded apartment) model soon became apparent, so we rewrote those in C++ in order to support the level of concurrency we needed.