3 ms·
Recording changes as they happen is easier than inferring them after the fact That's all very well if you're trying to develop something like Google Docs, w
by michaelt 12y ago
Recording changes as they happen is easier than
inferring them after the fact
That's all very well if you're trying to develop something like Google Docs, where you can define change semantics the merge process understands, then constrain the editors to only allow changes that follow those semantics.
But the moment a user wants to take the code out of your editor to process it with some other tool - perhaps they want to sort that text file, or minify that javascript, or just edit in emacs because they like the keybindings - you're back to inferring the changes after the fact.
You'd have to build a lot of tools if you want to stop your users ever wanting to use a tool outside your editor :)
- dangoor 12y agoIt seems to me that the Eve folks have already decided to make that tradeoff though: a richer environment that is necessarily walled off at least a bit from the traditional "it's all text" approaches. Smalltalk didn't take over the world with that approach, but it's certainly interesting to explore.
- marssaxman 12y agoI'm not sure what makes it interesting to explore; it is hard to imagine a more reliable way to doom a programming tool to failure.
- filearts 12y agoIn Cloud9IDE they've done a very amazing job of integrating collaborative editor with bring your own server. From what I've been able to tell, both the built-in editor and filesystem watches will trigger change operations and the two are used together to produce a very seamless user experience.