Thanks Josiah!  Looks like I can safely stay put then.  Since I only use it 
to keep track of my own notes I don't have to worry about impacting 
anyone.  And I don't use plugins either.

Because of the browser issues in the past, I use nwjs to launch my 
TiddlyWiki on the desktop.  So that isn't a concern either.

MJM



On Wednesday, October 31, 2018 at 4:44:56 AM UTC-4, @TiddlyTweeter wrote:
>
> MJM asked:
> Exactly *WHY* should I upgrade or migrate from Classic to 5!
>
> IF you have it working as you want it there is NO reason to "upgrade." Why?
>
> UPSIDE to staying with it ...
>
>    1. Its not an "upgrade," its largely a new system you would have to 
>    learn. Why do that work IF what you have already satisfies you?
>    2. A key point about TiddlyWiki architecture is its designed for the 
>    Long Term--its standards complaint so "older" Classic wiki should continue 
>    to work for years to come.
>    3. Classic code is still maintained and improved. See 
>    https://groups.google.com/forum/#!forum/tiddlywikiclassic.
>    4. The recent BROWSER problems with saving TW are a PITA but there are 
>    options that support Classic, so seamless saving is not dead.
>
> One DOWNSIDE ...
>
>
>    1. ONE issue, no one explicitly mentioned, is that innovation with new 
>    ways using Classic (plugins etc) are thin on the ground. This is because 
>    the active user-base is twindling. 
>    
> I conclude: IF you have all you need already don't bother with TW5.
>
>
> Best wishes
>
> Josiah
>

-- 
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 post to this group, send email to [email protected].
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/b3a6f2de-0726-4970-be33-25dde586995c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to