A complete rewrite of wiki as a single page application
121–126 of 126 posts
Re: A complete rewrite of wiki as a single page application
#122Re: A complete rewrite of wiki as a single page application
#123The original wiki was a wonderful community, alive in that ineffable way that very few online communities are, totally free and public. I wrote a blog post [0] about how strongly it influenced me as a person and the gratitude I feel for it. Ward Cunningham is a respected and intelligent software designer who works on open projects for the public good. The immediate cynicism and dismissal I've seen of his new project…
Because first impressions are important. If you see a car with a small knob for a steering wheel, you'll find that it is more difficult to use. And even though the engine of the car might be a radical improvement, this still doesn't mean that it can be used, mainly due to the pesky knob instead of a steering wheel. Obviously, after a while of using a knob to steer, you can get used to it, but that initial lack of usa…
Re: A complete rewrite of wiki as a single page application
#124Earlier quoted context omitted.
It's not static. It's an editable wiki.
It's not (necessarily) dynamic, in the sense of DHTML, either. While I'm reading a page, I don't need to watch the page change. At best you could notify me that the page has changed, but I don't think I'll really get anything out of that. There probably are environments where live collaborative (Etherpad/Google Docs/etc. style) editing of communal content is useful, but I suspect that you're looking at "documentation…
It is interesting how true that is. If you're there in real-time, the timing of the various messages and interactivity provides a lot of context to what is being said. You're also not reading everything all at once in a blast of data, instead you have time to read and consider each one appropriately.
Re: A complete rewrite of wiki as a single page application
#125Re: A complete rewrite of wiki as a single page application
#126Earlier quoted context omitted.
Because first impressions are important. If you see a car with a small knob for a steering wheel, you'll find that it is more difficult to use. And even though the engine of the car might be a radical improvement, this still doesn't mean that it can be used, mainly due to the pesky knob instead of a steering wheel. Obviously, after a while of using a knob to steer, you can get used to it, but that initial lack of usa…
I am not really disagreeing with you, but I would like to point something out: if this UI becomes widely used, then the cost of getting used to it is not so important. BTW, this is why I like Bootstrap: my web sites may look similar to millions of other sites, but no one is likely to have problems using it.