Hacker News new | ask | show | jobs
by y_g 3982 days ago
Meh. For > 15 years I have been architecting I/O intensive server products (web caches, wan optimization, filesystems) and unless it is crashing, we mostly don't worry about the operating system. Our performance issues are of our own doing, and are dealt with in user space, as with nearly everything we do.

I thought this paper was kind of silly when it came out, and still think it is.

Also, while I'm piling on Ousterhout, Tcl has got to be the most overrated winner of the ACM system software award.

2 comments

This is a Usenix paper from 1990. The past is a different country...

Tcl plus the Welch book is pretty good. You get purely event driven programs. I've replaced three or four Big Piles O' Java (that didn't work) with Tcl scripts and in short amounts of time. Nothing particularly wrong with Java, but these Piles still existed...

The Welch book is the critical component...

Its nearest neighbor is Python, which is also just fine except that package management then becomes a real chore. It's also easy to forget that Scotty ( the SNMP extensions to Tcl ) was the real winner back in the first dotcom era.

It's probably pretty lousy for web caches, wan optimization and filesystems. It's very good at constructing workstation-based programs to run against embedded systems.

Also, while I'm piling on Ousterhout, Tcl has got to be the most overrated winner of the ACM system software award.

Sprite OS and the log-structured file system were his more interesting achievements, anyway.