3 ms·
>> We programmed on them in VB6. And let me tell you, for all its downsides, VB6 was screaming fast. >> These crappy amateur applications were downright spee
by bluedino 12y ago
>> We programmed on them in VB6. And let me tell you, for all its downsides, VB6 was screaming fast.
>> These crappy amateur applications were downright speedy.
Compared to what? Visual Basic performance was a joke, even when you compiled it to native code.
- mattgreenrocks 12y agoThis is about user perception of performance: startup time, UI responsiveness, etc. Not raw CPU speed. It did fine on all those counts, even if you'd never let VB do your DSP work for you.
- mwcampbell 12y agoOn this topic, Chad Austin's essay "Logic vs. Array Processing" was quite illuminating for me. http://chadaustin.me/2009/02/logic-vs-array-processing/ http://chadaustin.me/2009/02/logic-vs-array-processing/ Granted, the platform surrounding VB6 arguably had too much hairy logic related to COM and ActiveX, and the fragile system that existed for registering such components before Windows XP introduced side-by-side assemblies. If you really want to pine for the old days, consider Delphi, where you could compile everything into one executable; just map that hunk of code into memory and go.
- makeset 12y agoYou wouldn't crunch numbers with it, but it was responsive and fast enough for most purposes, and had simple interfaces to faster native libraries for a lot of the rest.
- Shorel 12y agoIt was much faster than python. smirk