One way to ameliorate the effects of the "SaaS crunch" (as a user, i.e. potential casualty) is to stop establishing path dependencies on services altogether whe

One way to ameliorate the effects of the "SaaS crunch" (as a user, i.e. potential casualty) is to stop establishing path dependencies on services altogether when a document is sufficient for the problem at hand. In the case here, that isn't as difficult of a mental leap compared to other things, because of what they are from the very start: notebooks. These are documents; what we're talking about is something that you can prepare on your own machine and then ship off to somewhere else when it's time to share—whether that's by dumping it onto your own Web space, or attaching to an email. It should have never been the case that e.g. classrooms, etc. were standardizing on a single service provider to handle this problem in the first place.