parf wrote:Well, I still don't understand how someone dares to blame users for bad design decisions. Like a bad cook blames visitors for not having taste buds developed enough.
There is a large difference between "bad design decisions" and design constraints. Many years worth of electrons have lost their little quantum lives here in the forums talking about the designers' goals and objectives with how Scrivener is designed and how those decisions have consequences on down the line.
In any event, in all of my years in computing (back from CP/M on forward) attempts to user-proof a system have never been a substitute for user education. This notion that a user doesn't have to know anything about the constraints an application runs under and that the application will magically mitigate (when possible) and resolve (when required) all the potential error conditions under the hood really only applies when that is one of the initial design objectives and, usually, even then, falls short of the mark.
Scrivener is *not* one of those programs. One does, in fact, have to have a functional understanding of how it works in order to get the best performance from it, and realize that it has constraints. If one cannot (or does not want to) accept those constraints...well, perhaps Scrivener is not the right software for the one. Not every tool is right for every user -- if they were, there wouldn't be so many of them!