I believe the wiki is among the most amazing things to come out of the web (and think Cunningham is a genius for inventing it, or discovering it, or whatever process made it happen), and I can't count the number of times I've lost an hour or two spelunking into the C2 wiki. But, I'm having a hard time making sense of this UI. The panels popping up seemingly infinitely into the right side of the screen (every click ma…
I'm both sad and enjoyed by the move. I'm attached to the deceiptively poor old wiki, because it contrasts with the great content quality. At the same time, they're migrating toward something off the map of current technologies, and so the spirit of the first wikiwikiweb is still alive. ps: if someone has an archive / mirror of c2.com, I'll be happy to leech.
A complete rewrite of wiki as a single page application
11–20 of 126 posts
Re: A complete rewrite of wiki as a single page application
#12Wow, that's some bad usability there. Talk about chasing the shiny over form and function. Javascript pages are the 'Flash site' of the 2010s and I can't wait until it's similarly consigned to its rightful place in the dustbin of history. All they do is waste my CPU time and memory, force me to enable a scripting language that is riddled with vulnerabilities just to see some content, and run more slowly than real pages would.
Re: A complete rewrite of wiki as a single page application
#13Wow, that's some bad usability there. Talk about chasing the shiny over form and function. Javascript pages are the 'Flash site' of the 2010s and I can't wait until it's similarly consigned to its rightful place in the dustbin of history. All they do is waste my CPU time and memory, force me to enable a scripting language that is riddled with vulnerabilities just to see some content, and run more slowly than real pag…
You're commenting on a topic that the majority of people here have probably debated and thought about at great length. I can't help you think that calls for a slightly more nuanced argument than the one above.
Re: A complete rewrite of wiki as a single page application
#14The wiki I know for telling me all the new cool stuff is junk switches to a SPA? That's ironic. But seriously, in my eyes, a wiki is excatly what a SPA should not be used for, because of its document based nature. Trying to fix an overload problem with an SPA tackles the problem from the wrong side imho.
What's wrong with a single-page app? Wiki has always been a living document, best that the implementation formalize and facilitate a nature. If you really miss the classic format or need time to adapt, nothing stops you from using a Federated Wiki client that generates a page from the JSON.
Re: A complete rewrite of wiki as a single page application
#15Wow, that's some bad usability there. Talk about chasing the shiny over form and function. Javascript pages are the 'Flash site' of the 2010s and I can't wait until it's similarly consigned to its rightful place in the dustbin of history. All they do is waste my CPU time and memory, force me to enable a scripting language that is riddled with vulnerabilities just to see some content, and run more slowly than real pag…
You're commenting on a topic that the majority of people here have probably debated and thought about at great length. I can't help you think that calls for a slightly more nuanced argument than the one above.
no argument is being made, stop being po-faced.
I agree with his sentiments and wish the internet were otherwise. I don't care how thoroughly brow beaten everyone is about this, I want it recorded that this is dumb and unnecessary.
Re: A complete rewrite of wiki as a single page application
#16The wiki I know for telling me all the new cool stuff is junk switches to a SPA? That's ironic. But seriously, in my eyes, a wiki is excatly what a SPA should not be used for, because of its document based nature. Trying to fix an overload problem with an SPA tackles the problem from the wrong side imho.
What's wrong with a single-page app? Wiki has always been a living document, best that the implementation formalize and facilitate a nature. If you really miss the classic format or need time to adapt, nothing stops you from using a Federated Wiki client that generates a page from the JSON.
The canonical form of a wiki page should be a page; it really is a document and so should be in a document format (in contrast, for something like a bank statement the data is primary (in some sort of structured format with e.g. numeric fields) and the page is merely a representation of it).
Re: A complete rewrite of wiki as a single page application
#17The wiki I know for telling me all the new cool stuff is junk switches to a SPA? That's ironic. But seriously, in my eyes, a wiki is excatly what a SPA should not be used for, because of its document based nature. Trying to fix an overload problem with an SPA tackles the problem from the wrong side imho.
And it displays that awful behaviour of pages that get new content after they are loaded...
Re: A complete rewrite of wiki as a single page application
#18Earlier quoted context omitted.
I'm both sad and enjoyed by the move. I'm attached to the deceiptively poor old wiki, because it contrasts with the great content quality. At the same time, they're migrating toward something off the map of current technologies, and so the spirit of the first wikiwikiweb is still alive. ps: if someone has an archive / mirror of c2.com, I'll be happy to leech.
https://archive.org/details/c2.com-wiki_201501
Oh, thanks a lot, didn't know archive.org had a system in place to download archived mirrors. 40 well used Megabytes.
Re: A complete rewrite of wiki as a single page application
#19Earlier quoted context omitted.
What's wrong with a single-page app? Wiki has always been a living document, best that the implementation formalize and facilitate a nature. If you really miss the classic format or need time to adapt, nothing stops you from using a Federated Wiki client that generates a page from the JSON.
The canonical form of a wiki page should be a page; it really is a document and so should be in a document format (in contrast, for something like a bank statement the data is primary (in some sort of structured format with e.g. numeric fields) and the page is merely a representation of it).
It can be both a SPA and a document. They are not exclusive.
Re: A complete rewrite of wiki as a single page application
#20The 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 so far makes me sad.
Why not look into what he's trying to do? [1]
Why not try to learn something about how it works, rather than look at it for twenty seconds and then complain?