Tones, Agreed on all points. I didn't meant to suggest that the differences between Tiddlywiki and other programming environments are arbitrary or random. Generally TW is the way it is so it can do the things it does.
On Wed, Sep 30, 2020, at 10:04 PM, TW Tones wrote: > Ed, > > My programming days was more in the past, but I would argue that tiddlywikis > approach is different for a fundamental reason of architecture. If you were > to build something similar in any language you would have to ensure the > following and it would complicate the program massively; > * Cause all and any change in the whole solution to flow through immediately > to all references to that changed item > * Render all visible objects when a change occurs but do so efficiently, > including dealing with potential loops > * Allow the transclusions of transclusions etc... to work and be reliable > and avoid loops. > * Now wrap the vast majority of this is an environment that is somewhat > accessible to almost everyone > * Create not just an application but a platform which can be used to design > and document itself. > In the face of these facts it is my option tiddlywiki does the best job I > have ever seen. Yes we want to improve documentation and teach the concepts > effectively to improve ease of adoption and share the concepts. > > TiddlyWiki is not just a non-trivial Quine but a Quine platform. > > Regards > Tones > -- 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/546eea7b-88ba-4ca6-b7ae-91af3d5a9220%40www.fastmail.com.
