Fork JavaScript 0.1.0

Fork JavaScript project is a general purpose, namespaced JavaScript library with Ajax, Events, DOM manipulation. There are a few bonus lines of code specifically for use with Ruby on Rails but Fork can be happily used outside of Rails also.
Main features:
- an aspiration for the highest quality code
- author documentation
- documented limitations (all libs have them but dont report them)
- in-browser unit/integration tests
- tested in a wide set of browsers.
- functions to help create gracefully degrading web pages
- namespaced code
- does not augment JavaScript built-in prototypes
- does not add a layer of sugar on top of JavaScript to make writing JavaScript like writing in another language
- minimizable with jsmin and includes already minimized versions
- MIT License
- plugin for tight integration with Ruby on Rails
Why?
There are many JavaScript libraries out there. Why add another one to the list? To create a quality library with a liberal license.
I like Ruby on Rails. The Rails default Prototype JavaScript library does not suit many development situations and contains code that makes developing for a wide selection of browsers difficult or impossible. Prototype has some great ideas in its mix but the implementation quality has been questioned many times. Prototype has influenced many JavaScript libraries and some of Prototypes best ideas have also influenced the Fork API.
Because Fork is a namespaced library, you may be able to use both Fork and Prototype simultaneously as you transition from one to the other.
I like the Yahoo! UI library. Of the JavaScript libraries Ive used it has the best API. The YUI library has many valuable nuggets of information about browser bugs and workarounds. The approach of YUI suits browser scripting well.
However there are more than a few places in the code where Im left scratching my head and thinking "why did they do that?" Probably that is how every developer looks at another developers code. The YUI API is the starting point for much of the Fork API.
Most libraries seem to develop too quickly. I like the general debian attitude of careful growth because the browser execution environment is wildly varied and deserves a certain degree of conservatism in the JavaScript we send to it.