Leo & bluespire,

Thank you both for you insights, they are very helpful.  I'm still finding 
out more and more about both, seems to be quite a bumpy process with 
valuable info all over the place.  TW5 seems to be progressing quite fast 
though. 

@Leo: yes I saw your other posts and been wondering the same, also your 
observation on how long TW has been around and seemingly abandoned in 
places.  Quite odd.  Perhaps some of the longtime users will be able to 
shed some light on this.

Many thanks

Pete

On Friday, 17 January 2014 01:08:56 UTC, Leo Staley wrote:
>
> I'm also new, but I've settled on TWC. TW5 still has loads of bugs to work 
> out, and is still missing quite a few core features like permalinks. 
>
> So, I personally suggest TWC. 
>
> I actually asked a related question yesterday. I wanted to know how I 
> should build my TWC so as to cause the least friction when adopting TW5 
> down the line, after it finally has the features I need. 
>
> On Thursday, January 16, 2014 2:34:23 AM UTC-7, Peter Vogt wrote:
>>
>> Hi tiddlerers,
>>
>> I'm a TW noob in a bind deciding whether to go for TWC with its mature 
>> ecosystem and online hosting methods or TW5 as it new, exciting, changing 
>> (and more future proof?), running on node js.  My requirement is for a 
>> personal wiki which is hosted on a vps, which will be built/populated from 
>> scratch.  I'm definitely of the 'small, sharp tools' mentality, and a data 
>> format which will lend itself to any future transformations is desirable.
>>
>> Are there any resources to help make this decision, or can someone give a 
>> few hints please?
>>
>> Many thanks
>>
>> Pete
>>
>

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to