YUI Library

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

~ the last words ~

yui showed up in my project setup around 2008. i was a few years out of university and writing web stuff for hire. the choice was between jquery (small and plugin-driven) and yui (large and widget-heavy). i used yui for a couple of admin panels because the autocomplete and calendar components saved me from writing them from scratch. it was the right call at the time. by 2012 i had stopped reaching for it.

the yahoo! user interface library launched february 13 2006 out of the yahoo developer network. it was one of the first big open-source frontend frameworks released by a major web company, and for a few years it sat alongside jquery and prototype as the third option you would actually consider. it shipped a css reset stylesheet that became the default reset for half the web. there was a calendar component and a rich text editor that did not require flash, plus a profiler and a test harness baked into the build. the docs were good.

yahoo killed it on august 29 2014 in a tumblr post written by julien lecomte. the announcement cited the rise of npm-based modular tooling and a steady drop in interest in monolithic libraries. yahoo did not commit to a replacement. yui 3.18.1 was the final release, and the github repo went into archive mode shortly after.

~ the record ~

~ how it landed ~

yahoo open-sourced yui at a moment when most large web companies still kept their frontend code private. for 2006 that was unusual. the framework arrived already production-hardened because yahoo had been running it on yahoo.com and yahoo mail for over a year before the public release. people noticed. for the second half of the 2000s yui was the framework you reached for if you wanted batteries included and did not want to assemble fifteen jquery plugins yourself.

the technical bet was the opposite of jquery's. jquery believed in being small and being one thing. yui believed in being a stack. you could use just the core, or you could pull in animation or ajax helpers or drag-drop or autocomplete or a chart widget from the same versioned bundle. for the dashboard-style apps yahoo was building that was the better fit, and for the rest of the web it was the better fit for a while too.

~ what killed it ~

npm killed it. when node-based tooling arrived around 2011-2012 the frontend stack reorganized itself around small composable packages installed through a package manager, and the case for a single large versioned library evaporated. webpack pulled the build-tool job out of yui's hands in 2012, and react pulled the widget job a year later. by 2014 yui was already a legacy choice on new projects, and yahoo had no business reason to keep paying engineers to maintain it.

~ the long tail ~

the css reset survived longer than the library. eric meyer's reset and yui's reset together defined the convention of zeroing out browser default styles before applying your own, which is still standard practice in 2026. the calendar component was forked into a dozen smaller libraries that lived on for years after the parent project was archived. yahoo itself was bought by verizon two years after yui shut down and renamed to oath in 2017, which is its own death story. yui's github repo is still up. the docs site went down in 2020.

@}-->--

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

« previous  ·  random  ·  next »