Unity Web Player

» see unity3d.com as it lived, on the wayback machine

~ the obit ~

the first time a real 3d game ran inside my browser, there was a good chance the unity web player was the thing making it happen. for whatever reason this is the kind of detail an engineer remembers. you would land on a game page, it would tell you that you needed a plugin, you clicked install, restarted the browser, and then a 3d world ran in a rectangle on a web page. in the internet-cafe and early-broadband years that felt like a small miracle, since the browser on its own could barely draw a gradient.

unity shipped the web player around 2005, alongside the game engine itself. the idea was simple and, for its time, genuinely useful. unity compiled your game, the web player ran it in the browser through npapi, the old netscape plugin interface that every browser still supported. for a developer it meant you could put a real game on a web page without asking anyone to download and install a standalone application. a lot of browser games and small-studio demos rode on it.

then the whole plugin era ended at once. browsers decided that npapi plugins were a security and stability nightmare, which they were, and moved to kill the entire system. google announced the end of npapi in chrome and finished removing it in 2015. firefox followed. that did not just hurt the unity web player, it took down java applets and silverlight in the same wave. unity saw it coming and pushed everyone toward webgl, which runs in the browser with no plugin at all.

~ the rap sheet ~

~ the cracks ~

the plugin model was doomed for reasons that had nothing to do with unity. every plugin was a separate piece of native code running inside your browser with deep access to your machine, which made it a favorite door for attackers and a common cause of crashes. for whatever reason the web spent the late 2000s and early 2010s slowly building into the browser itself the things plugins used to do. once webgl could draw 3d natively, the only thing the unity web player offered was a security liability nobody needed anymore.

~ what it became ~

unity's answer was webgl, and it mostly worked. you could still ship a unity game to the web, it just compiled down to javascript and ran with no plugin and no install step. something was lost in the move. webgl builds were heavy and slow to load for years, and the easy magic of clicking install and getting a full game faded into a different kind of waiting. but the bigger truth is that browser gaming as a culture had already moved on. by the time the web player formally died, the games had gone to phones, and the plugin that once felt like a miracle was just one more thing you used to have to install.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »