3 ms·
Tcl was born three years earlier. The AOLServer, which was heavily multithreaded and based on Tcl, was developed in 1995: https://en.wikipedia.org/wiki/AOLserv
by thesz 4y ago
Tcl was born three years earlier.
The AOLServer, which was heavily multithreaded and based on Tcl, was developed in 1995: https://en.wikipedia.org/wiki/AOLserver https://en.wikipedia.org/wiki/AOLserver
You also can easily guess who of these two get i18n right earlier.
The AOLServer was made possible by the decisions to have an API to have specific versions of interpreters (including highly constrained safe ones), by forcing extensions to have per-interpreter state and make interpreters communicate by messaging on Tcl level. This resulted that if your extension worked with several interpreters in single thread execution, it would work with several threads ruunning in parallel. The same is for just Tcl code, which does not even know which thread it gets executed on.
Thus, Python developers did not do any looking around.
- blacksqr 4y agoTcl also has a simple but effective package management architecture, that required specification of package versions from the start, so no version hell. Later, a fully functional multiplatform binary package server/client was developed for Tcl [0]. It died of neglect while pythonistas spent (are spending) years trying to build something satisfactory. [0] https://wiki.tcl-lang.org/page/Teapot https://wiki.tcl-lang.org/page/Teapot