Well,
In my opinion TW is ill-suited as a computational notebook and the
already established solution in the Form of Jupyter is more than up to
the task. The only think I can see happen is TW having an interface to
the Jupyter Kernels, but even then, it doesn't quite fit TW's model.
The main problems seem to be:
- TW has a monolithic design, whereas for a computational notebook, the
Jupyter kernel <-> Interface divide serves it very well as you can
detach computation from the code/notes and therefore scale things much
better and work with different languages. For TW all I could think of
here would be WebWorkers.
- TW has a limit on data size. Nowadays, most datasets, no matter how
small are already larger than what TW might be able to handle, so they
would have to be in an external file/files either way.
So while I can see it being nice to have TW as an interface where your
results get stored and commands are issued, I don't quite see it play
out any of its advantages in this field and think TW's architecture puts
both hurdles and limitations on what you would be able to do.
/Andreas
--
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/922c6a71-5fb1-8ce0-17e8-90b19f4a6abd%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
