Thanks Arlen for your characterization, it's very helpful in conceptualizing "TiddlyWiki Philosophy". I think it's good there is a discussion about the name, even though it doesn't seem like there is any obvious immediate consensus.
Changing the name might only have a small influence over the overall marketing strategy for TW, but introducing new ways to think about TiddlyWiki as a syntax / language is helpful. - Mark On Thursday, March 12, 2020 at 10:16:08 AM UTC-7, Arlen Beiler wrote: > > LOL, I didn't mean to make it sound like it was headed toward PHP! I meant > it was headed toward being a stand-alone specification with an > implementation in Javascript, but which could be re-implemented in a > different language due to the wikitext characteristics. It still could be > but NodeJS is mature enough that another implementation will probably never > be needed. Good summary. > > Arlen > > On Thu, Mar 12, 2020 at 12:11 PM TiddlyTweeter <[email protected] > <javascript:>> wrote: > >> Ciao Arlen >> >> This is one of the most interesting overviews I have ever read about TW! >> >> I redacted parts of it to foreground the main thrust. >> >> Many thanks! >> >> TT >> >> Arlen Beiler wrote: >>> >>> TiddlyWiki is not a multi-user platform. In fact, it is arguably not a >>> platform at all. It is actually a syntax. >>> >> >> >>> It is a specification, not a library. >>> >> >> >>> It can be implemented in any language. >>> >> >> >>> Jeremy has implemented it in a Javascript library ... >>> >> >> >>> It could just as easily be implemented in PHP as a server-side >>> multi-user CMS ... >>> >> >> >>> That was the original direction TiddlyWiki Five was headed. >>> >> >> >>> Popular demand has since been slowly pushing it toward some Javascript >>> dependencies, but it is still a specification. >>> >> >> >>> It just so happens that browsers make it really easy to implement >>> specifications that only involve one user editing a document at a time and >>> not needing to serve it across the network. The network optimizations came >>> much later in the form of TiddlyServer and Bob... >>> >> >> >>> Anyway, hope that gives some perspective on the possibilities of what we >>> have in our hands. From someone who has spent his TiddlyWiki time poking >>> around the Javascript implementation and trying to make it do stuff it >>> wanted to be able to do but never got around to doing. Ok, >>> >> >> >>> * I know that sounds funny, but in the early days there were a lot of >>> stubs in the code and it was obvious that certain things were intended to >>> be implemented but there was never a demand for it so it never happened. * >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/902ff950-c475-4967-936e-11cdce2e532a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/902ff950-c475-4967-936e-11cdce2e532a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ac6b7d4b-073a-46df-898e-d9fdc08b6f16%40googlegroups.com.

