I've been following both ShareJS and Derby because, while I believe that the future of web application development is in realtime 'holy grail' frameworks, I ver

I've been following both ShareJS and Derby because, while I believe that the future of web application development is in realtime 'holy grail' frameworks, I very much dislike many aspects of Meteor, such as disregarding npm, the lack of proper server-side rendering (without the overhead of DOM) and the lack of importance placed on conflict resolution between client writes. I really want Derby, or something like it (eg AirBnB's rendr combined with realtime, OT models and collections) to succeed, however it really seems like Derby needs more community support and evangelism behind it, because I can't help but get the impression that most of the community focus in this space currently is on Meteor. As far as I am concerned, Meteor is the PHP of realtime 'holy grail' frameworks, as enjoys from just the same kind of popularity through 'worse is better' (where 'worse' is for the reasons I mentioned above). However, without a palpable, visible sense of community enthusiasm, a lot of fence-sitters such as myself are less likely to jump on board. Also guys please do something about racerjs.com, it doesn't inspire confidence in the project when it is continuously down.