Marshall Cottrell

@deontologician I think you have the right idea though, something like `.pluck('a', 'b', 'c').defaults({ b: true })` might be pretty handy.

@lirbank did you create your tables manually? There's currently no way to configure the primary key field for a collection. Both the client and server make assumptions in code that...

First of all, I just want to say I appreciate how passionate everyone is about this project and I feel much the same way. Unfortunately the project is in a...

@deontologician see my comment on using `yeoman` for this kind of stuff [here](https://github.com/rethinkdb/horizon/issues/117#issuecomment-184515025). I also kind of think this issue is just a dupe of #583. If we're still considering...

@deontologician makes sense, I agree with everything you said. One caveat being that I don't think `eject`ing the backend into the same repo is gonna be the common case. I...

@deontologician sometimes it seems like we're trying to solve these problems from both ends. `hz init` could just create `.hz/server.js`, a boilerplate `express` app preloaded with middleware and/or Horizon plugins...

@deontologician so tl;dr I'm saying why not have `hz init` generate all the code you're talking about `hz eject` do. Migrating back and forth would be easier if we just...

@deontologician my thought is that the generated code would have something like `.hz/plugins/index.js` which would just contain: ``` js import Config from '@horizon/config'; export default Config.loadDynamicPlugins(); ``` At any point...

I just don't see a compelling reason to lock down the `hz serve` workflow so tightly. All (or at least most) users are developers and I think laying all this...

> There's an issue of surface area we're exposing as well. As far as I can tell, the public surface area is roughly the same in both cases. As I...