I'm pretty sure you've posted that gif of the waitress winking. That's also from Twin Peaks. Great show if you don't mind just watching David Lynch do his thing. I was entertained.
> this stuff looks interesting. i'll put it on the list of things to try, but never will.
@IsraelDelendaEst@dcc@threat@sjw@m0xEE@ins0mniak@mia@sysrq@jeff@meso The internet tough guy believes he has made a cutting remark: "That'll show those computer nerds that computers are a waste of time!" he types on a computer to send his words across other computers to arrive on their computers, passing through, in part, the computers that have been assigned the names "poa.st" and "freespeechextremist.com", both of which I have root on. "They should stop touching the computer!" he says to himself, not thinking for a moment that the implication is he'd not be able to communicate using the computer if that happened, and that if this is how he really thinks things should be, he is free to turn off his computer and toss it into the ocean.
> possible, all the while wishing I'd done more burpees instead of sitting on my flabby arse and wondering what the hell I thought I'd be doing with a computer post-collapse.
The wignat dogfucker decides to argue on the internet about whether other people should be discussing computers on the internet. The irony is lost on him.
Kill yourself, you wignat dogfucker. Every time you tag me, it's you showing up in a thread where you weren't tagged to REEEEE about something unrelated. I don't know what, if anything, you do for a living, but people that work with computers like to talk about computers.
In any case, it doesn't give my anything I want and it breaks things I am using. I'm more likely to start using X on OpenBSD than I am Wayland on Linux.
Yeah, I always hated being able to select a window manager that wasn't GNOME. I'm running fvwm2 and ratpoison and I hate that no one is forcing me into stupid gtk3 widgets *everywhere*. I wish this goddamn computer was Windows because I don't give a shit what I'm doing as long as someone else worries about it and notifications pop up that tell me to do things and there's no way to disable them. Every day I get up and think, "I can't wait for Wayland to make all of those Linux chuds into Windows users."
Asshole edition: "What kind of deck is this? It looks like...like a 50-gallon barrel of whiskey with several ammo crates riveted to the sides."
Limit on peripherals? Because a stack of microSD cards being available or not changes how much ARM I want to do. I'm gonna assume that I can get microSD cards by the pound with this unlimited budget, plus as many 18650s as I can eat. (Let's say a soldering kit and a solar panel, too.) Assuming we're talking portables only.
Unimaginitively, I think "Pelican case luggable" is a decent form factor.
For the post-apocalypse, redundancy and durability are going to matter a great deal. The MSG has a nice design: https://cyberdeck.cafe/mix/msg . He basically crammed a Pi and a mini-x86 (Core i7 NUC) into the same box. Probably, though, I'd just forego the x86 and emulate it if I run into an x86 emergency, and grab a Turing Pi 2, fill all the CPU slots with Pis, plug some spinning rust into the SATA ports for archival storage, fill up the NVMe slots, leave most of the boards powered off and underclocked most of the time.
The third image up there, "Patchbox OS", the ultra-wide screen? I haven't seen this machine but I have seen this panel: it's an 8.8" Waveshare 1920x480(!!) panel, and I love those. So cram one of those onto the parts manifest, tack on an extra e-ink display. Mount a mechanical HHKB and a three-button trackball, get one that doesn't protrude much: Thinkpad mouse device would be great, but the rubber clits wear out periodically and there is no Fry's after the apocalypse. (There is no Fry's now. We're in the post-apocalypse.)
If I can fit a radio transceiver in there somewhere and some suitable antennas, that would be nearly essential. If we're capped at 72 hours, I think it'd take maybe six, eight hours to transfer my venti arenas, my /home, and my /usr/src onto one of the disks, say I do that in parallel with grabbing all the shit from the CRUX ports repos and slackbuilds. When the dremel gets too hot to continue operating it or I'm waiting for some epoxy or resin to set or I have a minute for whatever reason, slurp source code and docs and datasheets for all the chips on all the boards in the thing, and docs for hardware that is likely to survive the apocalypse (because it was either durable or plentiful). It'll take five minutes to get all of Plan 9 copied over, but pulling down the aarch64 binaries and source for everything, that'll take a minute or two.
All that would be nice, but I'm more or less happy with the DevTerm, so if we're talking "the computer that you take to the desert island" (where the problem is "What's a nice cyberdeck?") instead of "the last computer you will own, maybe the last one you will see" (where the problem is getting as close to luggable supercomputer as possible), I'll just grab a DevTerm. No hinges, that's very nice, low power, lots of connectors. Maybe tack on some accessories: a USB enclosure for a few SSDs, one of those fold-out solar panel/battery combos they sell to hikers, and if I can make a HHKB and external Waveshare panel (IT IS SO WIDE IT IS MESMERIZING) work, then probably throw those in.
Apparently it is possible to get old, like really old, like "Written by Bill Joy", I mean old, like "Invoked as ex and if you want to use the visual mode, you have to hit `:vi` inside ex", vi working. vi (src/cmd/ex, it is old vi) from Research Unix v10 didn't build, but some dude named Gunnar Ritter has ported it and last updated it in 2005. I have attached his tarball because SourceForge is still making you sit through a 5-second timer just to download a fucking tarball. (I had flashbacks to the early 00s. They need the ad revenue, man, you can't just host a 215kB tarball for free.) Then I had to tweak the Makefile because it expects the CHARSET env var to not be set (and $current_anno_domini Unix uses it), then it built but I had to set a TERMCAP because by default it can't cope with just TERM, but you can link in ncurses by tweaking the Makefile again, but *this* time I was able to use the 80s vi in question to edit its own Makefile. `./ex Makefile` and then `:vi` to enter visual mode and keep in mind that it starts you at the bottom of the file because ex(1) is an extended ed.
At any rate, it works. Here's a screenshot of me using it to edit its Makefile. It enables cursor blinking, because everyone was using CRTs in the 80s and even when it was ported in 2005, I think CRTs were still normal. I had a CRT. If I still used vi much, maybe I'd try to use this as my main vi for a while.
@ins0mniak@cjd@gh0st@jeff@lain@m0xEE@meso@mia@sjw@sysrq@threat@tiskaan Yeah, I used vi until about 2011 or 2012. Long time. vim/screen/ctags/urxvt, added extra ctags support for languages I used, stuff like that. I still use vi sometimes but it's usually either nvi or busybox's vi so that I don't have to disable all the dumb shit they add to vim every release; I just use ed for config files on servers half the time.
BOFH of freespeechextremist.com, and former admin. The usual alt if FSE is down: @p@shitposter.club, and others. I am no longer the admin. FSE has no admins now. Welcome to the FSE Autonomous Zone.I'm not angry with you, I'm just disappointed.I am physically in Los Angeles but I exist in a permanent state of 3 a.m.I have dropped a bytebeat album, feel free to DM me for a download code or a link to a tarball: https://finitecell.bandcamp.com/album/villain . There is a chiptunes album there, too.Revolver is coming: https://blog.freespeechextremist.com/blog/revolver-kickoff.html