Tcl and Tk are fantastic, and if this is where it ended, John Ousterhout would have secured his place in history - this is only 1 piece of his contributions, though - see too:
* Log structured file system[0]
* parallel Make[1] (Adam de Boor from Sprite project, not JO hisself)
* RAFT consensus protocol[2]
* Various notable teachings [3][4][5]
I like it better than the alternatives. The challenges come from vendors who had atrocious in house scripting languages (Synopsys) and then shoehorned their architecture into Tcl. You have to deal with a lot of opaque handles for things that should be native objects.
elhosots · · focus · HN ↗
Kudo’s to Mr Osterhout’s long lived legacy
bch · · focus · HN ↗
Tcl and Tk are fantastic, and if this is where it ended, John Ousterhout would have secured his place in history - this is only 1 piece of his contributions, though - see too:
[0] <a href="https://en.wikipedia.org/wiki/Log-structured_file_system" rel="nofollow">https://en.wikipedia.org/wiki/Log-structured_file_system[1] <a href="https://man.freebsd.org/cgi/man.cgi?query=bmake&sektion=1" rel="nofollow">https://man.freebsd.org/cgi/man.cgi?query=bmake&sektion=1
[2] <a href="https://en.wikipedia.org/wiki/Raft_(algorithm)" rel="nofollow">https://en.wikipedia.org/wiki/Raft_(algorithm)
[3] <a href="https://en.wikipedia.org/wiki/Ousterhout's_dichotomy" rel="nofollow">https://en.wikipedia.org/wiki/Ousterhout's_dichotomy
[4] <a href="https://web.stanford.edu/~ouster/cgi-bin/papers/threads.pdf" rel="nofollow">https://web.stanford.edu/~ouster/cgi-bin/papers/threads.pdf
[5] <a href="https://web.stanford.edu/~ouster/cgi-bin/aposd.php" rel="nofollow">https://web.stanford.edu/~ouster/cgi-bin/aposd.php
CorrectHorseBat · · focus · HN ↗
kevin_thibedeau · · focus · HN ↗