Deep dive · 05
VBScript: A Graceful Exit
It was born in the browser wars, did its real work in server rooms, and left office quietly in 2023 (the most administrative life of any BASIC dialect).
01Two births, one engine (1996)
VBScript appeared twice in 1996, and both appearances mattered. In the summer it shipped inside Internet Explorer 3.0, Microsoft's answer to Netscape: a small, interpreted subset of Visual Basic that could run inside web pages, positioned as a companion, and rival, to JavaScript, which Microsoft simultaneously implemented under the name JScript. Then at the end of the year it shipped with Internet Information Services 3.0 as the native language of a new technology called Active Server Pages. ASP turned out to be the significant half of the bargain. While VBScript in the browser was crippled from the start by its absence from any competing browser, VBScript on the server ran wherever IIS ran: and for the next decade, an enormous share of the dynamic web was written in angle-bracketed Basic.
02The dialect of the server room
Its second career was quieter and longer. Through the Windows Script Host (shipped with Windows 98 and Windows 2000) plain .vbs text files could drive the operating system itself: map network drives at logon, iterate files and folders, read the registry, interrogate Active Directory. The same engine took the other end of the working day: the .vbs that ran scheduled tasks at startup was, on a great many networks, the first thing a machine did after the login box. System administrators who had never bought a compiler suddenly owned a free automation layer, and the species logon.vbs multiplied across every corporate network on earth. The language asked little of its users: everything was a Variant, types were optional, and a working script was never more than a Notepad session away.
The depot's position on the dialect's qualities is fond but unsentimental. VBScript was VBA's stripped-down sibling: no compiled option, no editor beyond Notepad, and error handling whose flagship feature, On Error Resume Next, could convert a small bug into a large silence. It flourished anyway because it was there (preinstalled, documented, and good enough) which is how most software actually wins.
ASP pages were HTML with Basic stitched inside the tags: the whole idea of "server-side web development" wearing its training wheels.
03Losing the web, keeping the LAN
History's verdict on the browser half was swift: a client-side scripting language that only worked in one vendor's browser was not a web standard but a leveraging strategy, and the web chose the other one. The server half faded more slowly. Classic ASP gave way to ASP.NET at the start of the 2000s (a migration story entangled with the one told in VB.NET and the Great Split) but ASP pages and .vbs scripts accumulated a hinterland of dependability, the way working software does. Enterprises kept them because they ran. Nobody's job description ever included deleting a working logon script.
04The retirement (2023 → )
Microsoft finally made it official in October 2023: VBScript is deprecated, to be phased out of future Windows releases in stages, available at first, then disabled by default (as recent Windows 11 builds already do in Internet Explorer mode), then removed. The company's stated heir for administrative scripting is PowerShell, a decision the depot considers correct: PowerShell's object pipeline is a generational leap over parsing text, and clinging to a 1996 interpreter would be nostalgia, not engineering.
Still, retirements like this deserve a respectful obituary rather than a shrug. VBScript was, for millions of administrators and an entire era of the early web, the first tool that made a computer obey. The migration of aged .vbs fleets to PowerShell follows the same pragmatic arithmetic as VB6 migration: inventory, risk, contain, convert where it pays. And the dialect's family album remains open: the shared syntax across VB6, VBA and VBScript is one of the reasons skills transferred so easily across three decades of Microsoft platforms, a thread followed through the complete history and pinned to dates in the timeline.
Meeting a stray .vbs file in 2026? Read it before running it (between macro-era malware and email-borne worms), the file extension carries history. Classic admin patterns, annotated, live in the code depot.