3 ms·

We've also built tools for guarantees around correctness. My video discusses our deployless tooling, and it's also discussed in the blog post: https://medium.co

We've also built tools for guarantees around correctness. My video discusses our deployless tooling, and it's also discussed in the blog post: https://medium.com/darklang/how-dark-deploys-code-in-50ms-771c6dd60671 https://medium.com/darklang/how-dark-deploys-code-in-50ms-77... We think a lot about how large teams build at scale, and while we don't support everything we'd need for large teams just yet, Dark is designed for this use case.

vemv 7y ago
I've read the blog posts in the past, and it seems quite likely that Dark could be a large conflation of concepts (as opposed to composition), which repeatedly traded off desirable properties for faster deployments. The opposite is not impossible though, I'm certainly open to see the actual offering and tradeoffs. I'm mostly expressing that Dark's marketing likely won't appeal to people who tend to question things a lot; extensive rationale is needed for us. Btw, it seems quite possible to hack a vanilla Clojure setup (Reloaded workflow, tools.deps, some CI magic) to offer deployments under 30s. I just don't see it as worth the effort, and also I actively pursue some healthy constraints (slightly slower deployments = more thought put into things).