(why)should(nt) windows run on tiddlywiki?!!
has any one considered packaging tiddlywiki for win93
or even packaging window93 on tiddly wiki !?
(why)should(nt) windows run on tiddlywiki?!!
has any one considered packaging tiddlywiki for win93
or even packaging window93 on tiddly wiki !?
That is a hoot! And interesting.
I moved the post to Café.
interesting idea !
going off on that tangent abit
js-dos is a frontend for emulators that provides nice UI and infrastructure to run DOS or Windows programs in browser.
.js-dos.com/dos-api.html#adding-js-dos-to-your-web-page
.js-dos.com/save-load-game-progress.html
.js-dos.com/install-os.html#how-to-boot-with-empty-image
mind boggling … * intensifies *
If you run it on real hardware you need at least a 80386 with 4MB.
8D … turbo-button-optional
so you could boot dos from in html/js wTF
and run a dos/js ide
/in-theory
It is true that I do want to use TW to be able to control my machine.
On that every year gets worse as browser limitations BECOME Corporate Interests and absurdities (easier access online than offline to one’s files).
Unfortunately my JS ability is about -7.
TT
[= fortunately …
learnxinyminutes javascript
and tbh “in a browser” its not just “javascript”
it is the interaction between html/css/javascript and “document-object-model”
which is easy to type but enough to melt you brains
if you look at it for long enough
*imho
though … i guess it never just whatever language
but allways the language + environment
who wouldn’t want to store their tiddlers in “on” a w93_desktop.tid 
intermittently im drawn to the idea
but also easily distracted! =/
but honestly im more in favor of a “cli-like” ui
… because (of re-installing and re-configuring MSwin to many times it gets boring-af after a while, (also critically the dos shell lacks builtin documentation!!!
) )
i started counting clicks / per-thing
open browser
find exe , download
start “anoying-spam-filled-setup”
disable-spam
change-options , change-paths
repeat for next program in list
( yea i know unatended-cfg-gui is nice but shell/script is clearly more flexible ui (for repeating tasks))
conversely in a productive kbd input (ec)centric cli environment
you just type stuff (in one input ) , eg scripts in to a shell interpreter …
prog_lst=;
for this_prog in $prog_lst ; do
web-get $this_prog
…etc
done
or similar
with a little bit of string manipulation to
construct paths ( and an environment to quickly and disposablely check your syntax / assumptions are correct )
one-input
that could be likened to a tardis or [[sapient pearwood]]
“Multidimentional storage space, spanning across hundreds of possible pocket dimensions”
(you know what that sounds like description of ;- )
one-input :
with gui you have many inputs
consider “edit -mode”
… could (how) it be flatter 
any way mind boggling filters seam to be the new and evolving wiki scripting lingua-franca leading to exponential possibilities (& hopefully not exponential ram use =p )
