It's not a bad question, really. One reason is that JavaScript is the only popular language with no standard library.

not a bad question, though poorly (immaturely) articulated.

in addition to mbrubeck's comment, i'd say that javascript has grown from merely providing neat actions to webpages, to being model, view and controller.

at my startup we (er, the other developer) ported/mimic'd django's mvc to javascript. we're building a firefox extension, so this is particular critical as the extension must provide the full mvc for the "website."

edit: as a ff extension, our models are backed by sqlite files. in jester and kiwi are models objects? that is, are these frameworks purely for client-side applications, or for javascript-server stuff?

In Kiwi models are simply representations of server side resources.

Client side and meant to be used with REST Apis on the server

It's not an obsession, I wrote it because I needed something like this for my current work. I know there are quite of bunch of javascript frameworks out there, but the ones I looked at where either too huge or clunky, or didn't fit my needs. My intention was merely to share it with the community and propose the base for a hopefully collaborative project.