I’ve built a virtual museum with nearly every operating system you can think of
41–50 of 236 posts
Re: I’ve built a virtual museum with nearly every operating system you can think of
#42Re: I’ve built a virtual museum with nearly every operating system you can think of
#43I hadn't realized Domain/OS emulation was viable these days. It's one of the few systems that has actually "lost" features - the terminal-window-like thing (called pads, I think?) when in line mode had a dividing line at the bottom where your unconsumed typeahead was visible and you could continue to edit it until it got read - not just one line, the entire unconsumed input. (Not that it's a particularly desirable fe…
Re: I’ve built a virtual museum with nearly every operating system you can think of
#44This triggered a rabbit hole search that had me rediscover Packard Bell Navigator[1]. The nostalgia and joy this page brings me is hard to describe. I hope everyone remembers their formative tech journey so fondly. 1: https://en.wikipedia.org/wiki/Packard_Bell_Navigator
I never experienced it but somehow I still feel nostalgic for it. For all we've gained there's so much we've lost as well, I'm sad my kids won't grow up with anything like this.
Re: I’ve built a virtual museum with nearly every operating system you can think of
#45I hadn't realized Domain/OS emulation was viable these days. It's one of the few systems that has actually "lost" features - the terminal-window-like thing (called pads, I think?) when in line mode had a dividing line at the bottom where your unconsumed typeahead was visible and you could continue to edit it until it got read - not just one line, the entire unconsumed input. (Not that it's a particularly desirable fe…
Currently the terminal doesn't really process input itself, it just gives the program running the "raw" fd.
If instead the terminal gave the processes a pipe (for instance) and consumed all the pty input itself (and its end of the pipe being a buffer of that content), why wouldn't it be the same?