Sparkle is more of an all in one, more WYSIWIG (kind of, mostly) - part of the decision was that I needed something as simple and intuitive as possible to replace a dead iWeb that my wife uses to maintain her site (yeah, old!). She’s not a web developer, and not at all into coding or computer terms so anything that smelled even remotely of code would have been a bad fit.
I might get Rapidweaver later when it’s time to update the more elaborate sites done in Freeway, but for now we needed something that a real non-coder could manipulate without too much of a learning curve.
Simplicity counted, too - no additional plugins to add or buy, a more or less WYSIWIG interface, live previews in browsers. She’s already saying that Sparkle doesn’t work like iWeb, but she also seems to be figuring things out without too many issues.
So, I guess it came down to a minimal learning curve, visual interface vs. more power, more control and a steeper learning curve (vs I losing time explaining things and dealing with user frustration, never fun).
It was also fairly simple to track development history to make sure that Sparkle is still in active development.
freewaytalk mailing list
email@hidden
Update your subscriptions at: