mikemintz

One could buy long-term (LEAPS) put options to bet against a company, avoiding the unlimited downside of a naked short.

Thanks, I stand corrected! I always ignored initial values so I forgot about that case.

Check out compose.io

https://www.rethinkdb.com/blog/compose/

https://www.compose.io/rethinkdb/

I don't think there are actually any breaking changes. The release notes say "includeInitial" is breaking, but I think all of your existing application code will continue to run the same if you upgrade RethinkDB. It's just that new code using includeInitial will fail on old versions of RethinkDB.

This is a really exciting release! Atomic changefeeds make it much more consistent and robust to subscribe to realtime data in the client, and the performance improvements look incredible.

I made a simple chess app with React and RethinkDB: https://github.com/mikemintz/react-rethinkdb/tree/master/exa...

Hi Slava! Your project was immensely helpful for me to figure out what's possible. Optimistic updating is definitely the biggest and most challenging feature on my roadmap. I figured I'd save it until last so that by the time I start working on it some of those kinks would be figured out :) but I'm going to take a close look at the blocking issues.

Even when those RethinkDB issues get resolved, I still have some conceptual questions understanding how to make arbitrary queries update optimistically. For example, say that I'm subscribed to:

  r.table('proposals').pluck('name')

And I issue the following update:

  r.table('proposals').filter(r.row('votes').eq(0)).delete()

On the client side, because I used the pluck('name') operation in the subscription query, we can't possibly know which rows to optimistically delete since we didn't download the 'votes' field.

Do you know how this issue is addressed in meteor? I'm currently thinking I'll have to limit optimistic updating to queries that follow a simple structure, but I'd love a more general solution.

DB queries are validated through a whitelist on the server, so it should be impossible to run an unauthorized query when it's locked down. E.g. https://github.com/mikemintz/react-rethinkdb/blob/master/exa...

You no longer need an undergraduate degree from Stanford to do a symsys masters:

http://symsys.stanford.edu/ssp_static?page=msinfo.html