Sixth Edition is from 1975. Let's consider its contemporary large-scale multiuser OS environments: * PLATO at UIUC. Much more sophisticated graphics and extensive support for multiuser gaming, but requires custom (and expensive) terminals. Homegrown mainframe, then CDC hardware. * Michigan Terminal System at University of Michigan and elsewhere. Runs on IBM mainframes. * Multics, ITS, TOPS-10, and who knows what else…
This omits a bunch of others -- WYLBUR supported interactive program development on IBM mainframes at several universities, for example. (The "large scale" qualifier here is also a little bit dubious -- it seems to be a way of saying that anything running on a machine as small as a PDP-11 doesn't count. But there were timesharing systems on even smaller machines, such as PDP-8s.)
Research Unix Sixth Edition (WASM)
31–36 of 36 posts
Re: Research Unix Sixth Edition (WASM)
#32Re: Research Unix Sixth Edition (WASM)
#33Also it’s probably a lot more work to retarget the existing compilers to new back ends
Although if this is a new Go implementation, it’s probably a lot of work anyway
Re: Research Unix Sixth Edition (WASM)
#34Sixth Edition is from 1975. Let's consider its contemporary large-scale multiuser OS environments: * PLATO at UIUC. Much more sophisticated graphics and extensive support for multiuser gaming, but requires custom (and expensive) terminals. Homegrown mainframe, then CDC hardware. * Michigan Terminal System at University of Michigan and elsewhere. Runs on IBM mainframes. * Multics, ITS, TOPS-10, and who knows what else…
I've really wondered where things would be if TOPS-20 and Multics has made the leap to a modern architecture and continued development. The command interpreter for TOPS-20 was really intuitive, and if you've used Cisco iOS - you've used something that works a lot like TOPS-20.
Re: Research Unix Sixth Edition (WASM)
#35Why a simulated PDP-11 CPU rather than compiling to wasm? I guess because wasm is pure computation with no interrupts and so forth? Also no access to the stack Also it’s probably a lot more work to retarget the existing compilers to new back ends Although if this is a new Go implementation, it’s probably a lot of work anyway