Flynn (YC S14) Gamma and Meetup

Yeah, tup is neat. Much lower friction than the equivalent Makefiles as it can auto-detect dependencies and outputs in many cases. We've run into a couple issues, but for the most part it's been smooth sailing.

Not on the Flynn team, but having a single repository instead of many makes it easier to make changes that cross packages without having to worry if you broke some remote thing.

Here's an article that discusses this idea: https://www.digitalocean.com/company/blog/taming-your-go-dep...

Hey, Flynn cofounder here. We merged the repos (there were a few dozen!) after encountering a ton of friction landing project-wide changes and managing the build system (vendoring dependencies in every repo got ridiculous).

Contributors were also having a lot of trouble figuring out where to report issues and submit patches. On the whole the unified repo and build system has been a massive improvement to our productivity and the quality of the project. Unfortunately using components in a modular fashion can be harder, and we haven't come up with a great solution to that. We're still committed to keeping our components independently useful and would love to get feedback on what we can do better.

Flynn cofounder here. The primary difference between Flynn and cloudfoundry, dawn, deis, dokku, octohost, openshift, tsuru, etc is that Flynn is designed to run everything itself, not just 12 factor web apps. Most immediately this means that you can run databases inside of Flynn alongside other apps. In fact we've already wrapped up postgres.

Flynn also tries to be more technology agnostic, for example we don't depend on CoreOS or Docker.

It's worth noting that several of the other platforms including Deis claim to be production ready today while Flynn is still a few months out.

The difference in both features and goals will be a lot clearer in the coming months. What we have today is just the foundation and minimum viable feature set. Once that's rock solid, the real work gets started.