Re:Voyager 1 starts making sense again after months of babble
by kstrauser on Thursday March 14, 2024 @03:36PM
(#39708067)
Well, my grandpa didn’t know jack about computers, so I very well could have maintained code he’s written based on the disquality of stuff I’ve had to work on in the past.
But yeah. In “A Fire Upon the Deep”, Vinge talked about archaeological programmers. There’s no doubt in my mind we’ll reach that point. “Tell me again why time_t is only 64 bits?” “Pull up a chair while I dig out the LKML archive. You know, this was originally stored in electric fields, if you can believe it!”
Re:Voyager 1 starts making sense again after months of babble
by acheron on Thursday March 14, 2024 @04:06PM
(#39708377)
Fire up the subspace ansible and create a holodeck room for us to talk about it. You can't name the holodeck program "CON", "LPT1", "PRN", or "AUX", though, because those are MS-DOS device names. ( https://news.ycombinator.com/item?id=37076523 )
Re:Voyager 1 starts making sense again after months of babble
by myself248 on Thursday March 14, 2024 @04:28PM
(#39708572)
To this day, I use
COPY CON FILENAME.TXT
to make a quick-n-dirty note of something without leaving the terminal.
Re:Voyager 1 starts making sense again after months of babble
by kstrauser on Thursday March 14, 2024 @05:00PM
(#39708913)
I use `cat > foo.txt` all the time for the same reason.
Re:Voyager 1 starts making sense again after months of babble
by Arrath on Thursday March 14, 2024 @07:13PM
(#39710107)
There's an idea for another holodeck mishap episode right there.
The ship's replicators start spitting out PacMan ghosts which quickly overrun the passageways ala Tribbles, in the end it turns out Ensign Crusher attempted to pipe his holodeck game to PRN and the Ship's computer mistook that as a command to begin (3d) printing.
[0] https://www.minot.af.mil/News/Article-Display/Article/264580...