[signifiers]

(author here) I think this was misunderstood. I don't mean the _entire_ Chromebook or OS was unstable -- just the opposite actually. I was referring to having to restart Termux twice in two weeks. Two weeks of constant wake/sleep cycles on and off battery, and plugging/unplugging from an external monitor.

In one case it was a hard kill and I lost one ssh window that had been open for a week. In the other, the Termux gui came up and I never dropped my session (the ssh process never died). I'm not yet familiar enough with the Termux internals to understand that. As far as the Chrome OS stability, it's been one of the most stable machines I own, and I say that as a long-time MBP & Librem owner. 99% of the reboots were intentional as I reinstalled the whole build from Powerwash to Erlang hello world, to make sure I got the details right for the post (and to help troubleshoot some minor install roadbumps a couple of my reviewers experienced).

On the presentations, I joined multiple Hangouts & BlueJeans (WebRTC) video client calls with zero trouble. Signal and Wire voice worked like a champ too.

So while I certainly understand some of the comments here, for _my_ use case — a reliable $160 multi-week travel/burner dev notebook with strong security, I'm more than satisfied. And of course it's not in the same league as my $2K++ MBP. I would never try to run a big JDK app, but for offline Go and Python work, it fits my bill.

[swiley]

Yeah, that's pretty terrible. My GNU/Linux machines have months long X11 sessions with firefox, libre office, hundreds (I've hit the window limit) of xterm windows, and lots of other stuff open while waking up and sleeping (s2ram) multiple times every day.

I've them crash once every few years after I'm done setting them up, usually it goes down because I run out of power or want to update the kernel. There's no good reason some GUI should die because of waking up from sleep.