3 ms·

I think newobj is referring to the non-atomic nature of dropbox sync: there is no "commit" or singular upload, but rather a continuous sequence of changes. The

by shykes 14y ago

I think newobj is referring to the non-atomic nature of dropbox sync: there is no "commit" or singular upload, but rather a continuous sequence of changes. The question then is: how does this affect deployment? For example you might see markup changes deployed without the corresponding css changes. I would guess the answer is that the "deployment" is so lightweight and fast (minify a few text files and copy them somewhere) that it's ok to re-run the deployment step at every single new file change. I'm a big fan of this workflow. Good job Cole!

colevscode 14y ago
Yes. The worst you might see is a few seconds of mismatched styling, or an occasional error that would resolve when the next dropbox cycle pushes a refresh. The only deployment operations that involve inter-file dependencies at this time are the minification and concatenation that occur during optimization. And we don't recommend turning on optimization during development-- it does slow things down, and we haven't implemented source mapping yet so you'd have to debug obfuscated code.