I believe one of the reasons why there haven't been any for JavaScript or Node.js is because nothing is standardized, apart from possibly express and connect.
Authentication and authorization is yet to be standardized. This is the big part of an admin backend. Also, because there's no standard ORM, data store, or even schema, it's really hard to get something completely agnostic. You'd have to present a boat load of configurations for it to work, but then you wouldn't achieve "working right out-of-the-box."
Yeah -- I was expressly comparing to Rails, which has had a kind of de facto standardizing effect.
And in addition to not having an ActiveRecord-style de facto standard interface for CRUD, and having a much wilder profusion of datastores than the SQL/almost-first-class-citizen-Mongo in much of RailsLand, the node.js community is pulled in a lot of different directions because of Real-Time.
What's the future of ORMs in a real-time world? Projects like Derby/Racer are a fascinating/messy glimpse into what kinds of forces are shaping the data layer.
Look at how much harder simple things like validation/authorization are when you're dealing with an OT engine that doesn't understand schemas, and which do its job necessarily lives half in Redis and half in Mongo, using the ShareDB api ...
Node.js has a lot of wonderful excuses not to have an admin panel; most of them are related to why node is awesome.
That being said, I hope we get some admin panels. :) Passport.js is a decent Devise standin, for instance, and there are a lot more ORM/ODM options now than there were two years ago.
Comments
I believe one of the reasons why there haven't been any for JavaScript or Node.js is because nothing is standardized, apart from possibly express and connect.
Authentication and authorization is yet to be standardized. This is the big part of an admin backend. Also, because there's no standard ORM, data store, or even schema, it's really hard to get something completely agnostic. You'd have to present a boat load of configurations for it to work, but then you wouldn't achieve "working right out-of-the-box."
Yeah -- I was expressly comparing to Rails, which has had a kind of de facto standardizing effect.
And in addition to not having an ActiveRecord-style de facto standard interface for CRUD, and having a much wilder profusion of datastores than the SQL/almost-first-class-citizen-Mongo in much of RailsLand, the node.js community is pulled in a lot of different directions because of Real-Time.
What's the future of ORMs in a real-time world? Projects like Derby/Racer are a fascinating/messy glimpse into what kinds of forces are shaping the data layer.
Look at how much harder simple things like validation/authorization are when you're dealing with an OT engine that doesn't understand schemas, and which do its job necessarily lives half in Redis and half in Mongo, using the ShareDB api ...
Node.js has a lot of wonderful excuses not to have an admin panel; most of them are related to why node is awesome.
That being said, I hope we get some admin panels. :) Passport.js is a decent Devise standin, for instance, and there are a lot more ORM/ODM options now than there were two years ago.