Ciao Siniy-Kit As far as I understand it the problem is not the DOM per se, which TiddlyWiki does not handle in the standard way, its the REFRESH mechanism. Everything has to be rebuilt when a change is made. The problem with this is that the more complex the TW gets the worse performance (generally) gets.
Its certainly worth comparing if a Node.js might work better. But its likely there is a limit. If it works better it won't be because of "lazy loading" since, as PMario says, in your usage as the issue centres on Tiddlers could be invoked in lists/filters. "Lazy loading" relates to simply that the Title only is permanently in memory--and the Tiddler content loads on click. It won't speed up lists or filters. In brief, at the moment, TW does not scale well. Since I am a bit of an amateur (I'm not a programmer) others may say otherwise... but I wrote this to hopefully elicit clearer answers. Best wishes Josiah Siniy-Kit wrote: > > The problem is not in speed loading. The problem is slow work of big TW5. > All navigating and menus become very slow. > <https://groups.google.com/d/msgid/tiddlywiki/3a1b4dcf-85cd-4252-9924-41ab03eb1024%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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d8690ee5-cc00-4016-ae09-7fd6734587f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
