Hey everyone, one of the founders here! We've written a blog post that pretty much sums up our vision on real time infrastructures and our drive for this product. Have a look: <a href="http://blog.telepat.io" rel="nofollow">http://blog.telepat.io</a>
I don't like the fact that the Tux logo is linked to <a href="http://linux.com" rel="nofollow">http://linux.com</a><p>Should be <a href="http://kernel.org" rel="nofollow">http://kernel.org</a> as linux.com has a spammy feeling..
I think your comparison with Meteor is not fair. You are not obliged to use Meteor in back and front, you can have a meteor backend and load a DDP client in about any language.
And as I'm doing one right now you can have a only front application talking to a rest server. So it's more flexible than what you tell in your comparison. Also I might not be fair because I'm a Meteor addict :D
This is great stuff!<p>I was wondering though, looking at the stack, if some parts couldn't be substituted with "lighter" alternatives? I'm assuming couchbase is being used for the changes feed and since you can't do adhoc querying you need "elastic search" for that, however wouldn't it be possible to replace both with just rehinkdb? Anyway I'm just speculating here, I should probably dig into the code.<p>Thanks for sharing this and keep up the good work!<p>Update: seems you'll still need elastic search for rethinkdb full text search [0]<p>[0] <a href="http://www.rethinkdb.com/docs/elasticsearch/" rel="nofollow">http://www.rethinkdb.com/docs/elasticsearch/</a>
Hi, for node-only usage, how is this different from Racer[0] (part of DerbyJS)?<p>[0]: <a href="https://github.com/derbyjs/racer" rel="nofollow">https://github.com/derbyjs/racer</a>