3 ms·
I get the sense that a wiki was, in spirit, supposed to be simple bit of code to turn a read-only website into something that acted more the way the web was ori
by derefr 10y ago
I get the sense that a wiki was, in spirit, supposed to be simple bit of code to turn a read-only website into something that acted more the way the web was originally envisioned, where every hypermedia document could be WYSIWYG-edited inline in a web browser and then PUT back, or appended to and then the appendment POSTed, without needing anything like a <form> element.
Since browsers never did move toward that paradigm (though contentEditable was a half-step), I can understand the desire to re-implement that vision more thoroughly, by essentially implementing a "browser the way it should be" within the browser, and then having that better browser talk to your backend.
Sure, you could do it as a full hypermedia-editing-capable browser of its own instead (i.e. another "quick hack", this time in Electron) but doing it as a SPA means not requiring people to download+install your app to edit the site. (Or, you could say, the app is zero-click installed, ephemerally, when you access the site. If other sites used this software by referencing the same SPA JS bundle from the same CDN, it'd give about that effect.)