Some more thoughts.

The problem with databases I see are: 

 - *Our users like files* and will go a long way to keep it that way. 
 - DBs need maintenence
 - DBs need to be secured
 - ... 

So in the end we need a service provider, that abstracts the complexity 
away. 

I personally would like to use a dat-project based approach, which is 
similar to a "file sync" mechanism. ... The beaker-browser uses dat as its 
foundation. 

PROBLEM here is: 

 - It's a young project with contains some fast moving targets. 

If you have a closer look at the dev-diary videos 
<https://www.youtube.com/watch?v=OUaqT6huJMg&list=PLBND3AXbdG41mp1VbNL6HF_lE3lBeb6wf&index=1>,
 
I think you can see, how nicely the "new" approaches would fit to 
tiddler-based TWs. 

 - Concepts show in the videos can only be *tested, if you compile the 
developers branch on your own*. 

have fun!
mario





-- 
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/ad7180ba-e4d6-4d19-bd25-578cf4842391%40googlegroups.com.

Reply via email to