It's funny to me when we denouce BASIC unconditionally but promote the web as an application platform when in most cases, they're used for the same reasons (pervasiveness, compatibility, ease of distribution, technical accessibility)
I don't think either would be a programmer's "first choice" based on engineering qualities alone.
@jjg anyone else wonder if the web would have been better to develop for if visual basic had ended up being the scripting language?
@alienghic not me :)
However I *do* think Visual Basic was a superior tool for developing applications (note I didn't say *good*, just superior to the web)
@jjg i agree its not great... But i think vb had modules back then which would've been an improvement over the early web
@alienghic I guess it depends if you're referring to VB or vbscript (the latter was supported by IE, the former not). As far as I know, vbscript didn't support modules.
Before .NET I wrote a lot of VB modules for server-side bits on Microsoft platforms.
I don't have strong feelings about which language is better between js and vbscript, but having a language which is owned by one company has disadvantages.
Before access they had ODBC and VB could talk to a the Jet database engine? though I think that was also used by Access?
I think ADODB was part of it, but it seems like there was something else.
Anyway, not important, but invoking Greenspun really takes me back!
@alienghic
There was some sort of CGI thing though I can't can't remember what it was called. If I remember right you made two files, one that was kind of like the "UI"/html side and then one that was more like the "code". It was super-funky, may have been part of the IIS that you could download for NT 3.51...
Anyway it sucked, and then ASP came out which looked good by comparison :)
@donblanco