251 karma · joined September 23, 2010
Every save forms a new version online, but you can go back and retroactively mark certain versions as major milestones. Milestones are roughly equivalent to commits in Git.
Since we're primarily focused on graphic design formats, we don't attempt to do any merging of files since it's unclear that the end product would make much sense. We don't lock files either. If two users simultaneously edit the same file, one of them "loses" and shows up as a Conflicted copy that you can visually resolve in the Comparison view online.
[1]: http://helpx.adobe.com/photoshop/using/file-formats.html#lar...
We initially started out with tiered pricing based on storage. However, based on usage, we actually found that people rarely hit their storage caps. A better barometer for us is the number of people working together, which we approximate with projects. In that regard, our pricing plans are similar to Github's. Public projects are free and unlimited. Private projects are paid.
Old design: http://bit.ly/1nyPUCL New design: http://bit.ly/1rEA7FE
Original post: http://www.jayhuang.org/blog/pushing-code-to-github-as-linus...
College for me personally had little to do with academics and much more to do with the people I met once there. When I was leaving high school, I had little idea that this would be the case.
Can you comment on what led to this change? Inbound traffic looks like it's still pretty solid. Was it just that not enough people were converting to paid plans?
[1]: https://slack.com/
[1]: http://investor.fb.com/releasedetail.cfm?ReleaseID=835447
[1]: https://www.dropbox.com/s/7f6x473a6qaw4vi/Screenshot%202014-... [2]: https://www.dropbox.com/s/70zjz7x4tjh3u0k/Screenshot%202014-...
[1]: https://docs.newrelic.com/docs/python/python-agent-and-torna...
The upside of such an approach is that there is one central point of truth for everyone's info. Conversely, the downside is there's also one central point of failure.