gh-throw

It's really good, actually. I don't think they stream 4K but for most people that barely matters (screen either too small or too far away for it to make a huge difference).

They have a rotating selection of Criterion films. Heavy on documentaries (of the plays-the-festival-circuit variety, not the narrated-by-David-Attenborough variety) too, if you like that sort of thing. Usually several fairly-recent good movies as well. It's where I watched Ex Machina, for example. Kids' features really lacking, mostly low-quality stuff that would have been (maybe was?) bargain-bin straight-to-VHS material back in the day. No substitute for PBS or Disney+ for that purpose. Material for adults is much stronger.

Views are limited per-month but unless you consistently watch more than a movie a week on that service specifically you'll never have a problem with it.

I've got an address that qualifies for two library systems, and the one I'd normally use didn't have it, so I had to get a card for the one I'd practically never use otherwise to gain access to Kanopy.

> Film has such a huge library of "great movies", I have over 700 films logged on letterboxd, with a pretty decent spread of years/countries and I would say I still know basically nothing about film.

Film is so full of great stuff that there exists a reasonably-curated meta best-of-list of 1,000 great ones... with an overflow list of the next 1,000 that's also almost all excellent, and those still aren't a comprehensive list of all the films worth watching.

https://www.theyshootpictures.com/gf1000.htm

(Possibly NSFW because of screen-caps from movies)

1) Yes, I know, that's how long Firefox has been going down the wrong path, performance-wise. They've only recently seemed to kinda start addressing that ("now we're as good as Chrome, finally!" OK but Chrome is also bad, so....)

2) I'd prefer software just, you know, not be bad. Safari, for all its problems, demonstrates that there's nothing inherent in a modern desktop web browser that requires it to be grossly inconsiderate of your system resources.

I definitely don't consider Firefox's resource use (battery, CPU, memory) something to aim for. Pre 2.0 Firefox? Hell yes, it was part of what got everyone on it in the first place. After 2.0, when it started to bloat rapidly for unclear reasons? Not so much.

- Any health problems for anyone concerned in the first couple months (which is when it's most likely, for the mother and baby in particular, obviously) will be really, really bad, as far as making those weeks much worse than they'd otherwise be.

- If you get very unlucky (sometimes) or suck at sleep training (way, way more often) get ready for years of bad sleep, yourself. If you're good at this the dreaded "sleep zombie" stage of parenting is only ~2-3 months long, though, so no big deal in the scheme of things, and even better if you've got a spouse who isn't the kind of person to "punish" their partner any time they have to be awake by making them also be awake (lots of people truly are like this, and I think it's nuts, if you do some good trading-off with one another, then the first couple months are actually really easy and you'll only be sleep-deprived like half the time, at worst)

- If your kid is sick, at all, then sleep in those early weeks will be exceptionally terrible, as kid illnesses tend to manifest in frequent waking & crying that can't always be assuaged with milk or rocking or whatever. Even a mild illness can make those early nights damn dark, and you may have trouble figuring out what's wrong (may take shopping for a doctor to find one who won't just rudely brush you off as a newbie parent with a "colicky" baby and actually listen to you and try to figure it out)

- They can be incredibly expensive, for all kinds of reasons, including but not limited to healthcare expenses (in the US), damage (ours have done over a thousand dollars of damage to stuff around our house in some years, more if we counted the rate of wear on e.g. flooring or the cost to pay for repairs on all kinds of things that we were able to do ourselves very cheaply), education (paid directly or, more commonly, in much higher housing expenses than you'd otherwise have). Oh and as they get older, food. (clothes and toys are negligible expenses compared to the rest, unless you don't want them to be)

Basically if no-one gets sick and you take sleep training seriously, they're just expensive and everything else is barely a problem... until they get old enough to start going places on their own, and then you get a whole new set of worries :-)

A move to anything similar to Electron is gonna be the same to me as the project dying. In either case, I'll no longer use it. That's a shame.

[EDIT] "but it's already XUL!" right but XUL-based GUI programs can run great on machines without enough memory to use Slack or VSCode without hitting swap, even if those were the only programs open. My source for this: I've been using XUL apps since the days when machines with 128MB of system memory were pretty damn high-end. They were kinda heavy back then, but basically fine. They're straight-up lightweight by today's standards.

10-to-1 that mouse had a really nasty short in it somewhere.

Not only that, the screen’s super-ugly. It looks like part of some “kitchen sink” demo of UI elements.

Glad it’s not just me annoyed every time I open that and am reminded how crap it is now.

My example of what? I’m not sure what you mean. As far as I can tell my example is that I only use Brew to install software for which the question “which version do I want?” may always be answered with “the latest” or “I don’t care”, so I don’t have an upgrade problem.

Anything I need at a particular version gets installed some other way, unlike how I operate on Linux, where anything I need at a particular version plus a bunch of other stuff all gets installed outside the package manager (talking workstation usage specifically)

GP and a sibling comment (quote: "Something as simple as "brew upgrade youtube-dl" could end upgrading dozens of _unrelated_ packages, such as postgres--which ends up breaking my local development environments.") seem to describe using Brew to manage dependencies of applications they are developing, which I do not do, and wouldn't do with a Linux workstation's package manager either, so I never have those problems. That's what I was pointing out.

For me, Brew is for managing my personal software I use that doesn't come from Apple. Project dependencies, including the version of the compiler or interpreter for the language you're writing, don't belong brew-managed in most cases, which seems to be what's tripping people up when they try to use it for that.

Yes, containers run better on Linux because they're native. No quibble there. I just find I'm much, much better able to cleanly manage my personal software (not project dependencies, which, again, I wouldn't try to manage with my workstation's Linux package manager, either) with Brew on macOS than in any Linux distro I've used. 99% of what I ever want to run (outside the base OS, and project dependencies) is on there, available at a single "brew install", after I do nothing more than install Brew itself, versus 50-95% on Linux (depending on the distro), where I find myself adding all kinds of extra repos and installing one-offs a variety of ways just to get to a baseline level of having all the stuff I need at new-enough versions. And the interface is above-average, in my opinion (but again, Portage/Emerge is my favorite package manager on Linux and maybe the only one aside from Void's that I've found pleasant to use, so I may just be weird)

I think I must use it differently from how other people do. I use it to install tools I'll use directly, so I practically always want those to be at latest (or otherwise don't really care what version they are). If I need something at a particular version I'd use a container, or install it manually in some isolated folder, or something like that, since odds are if I need something at a particular version I'm going to need it at multiple particular versions and to be able to re-create the installation on other environments.

So I end up with:

System -> Apple-managed

My tools, as in programs I personally use -> pretty much entirely Brew, in fact I think on my current workstation this category is 100% brew-installed

Dependencies of anything I'm working on -> some language-specific version manager (which itself is may be brew-managed, actually) plus containers or VMs with scripted installs, probably.

On linux my experience is typically more like:

System -> package manager

My tools -> package manager, plus some sketchy extra repos that I hate to add but do anyway because I don't want to screw with manually updating things, plus several things installed manually, plus a bunch of things on older versions than I'd like but not worth the trouble/risk of finding some way to upgrade without it being a PITA.

Dependencies of anything I'm working on -> some language-specific version manager (almost certainly not available in the distro's official repos) plus containers or VMs with scripted installs, probably.

So for my use, Brew cleans up the "My Tools" workflow very nicely compared with Linux, excepting, kind of, my days back on Portage/Gentoo, which of course has its own problems.

Huh. I've seriously used... I dunno, maybe five Linux package managers, on workstations and servers alike, plus poked at a couple others, and the only one I'd almost rather use day-to-day than Brew is Portage, but even that, probably not.

I like having the system strictly separate from my crap, and I think the UI is fairly good. The variety of packages available out-of-the-box is outstanding. I miss it when I'm on Linux, now, in a workstation-not-server context (yes, I know, there's LinuxBrew, but the package set is much smaller and less well-maintained). I started on MacPorts but got sick of it borking itself every few months such that it was faster to nuke the directory and reinstall everything than to figure out what it'd screwed up this time (granted, that was about a decade ago, maybe it's great now).

Brew gives off all kinds of signals of being something I'd hate (cutesy; a system tool written in Ruby; breaks with norms) but I like it a ton.

I think computer geeks tend not to recall how many hard-won insights and how much time it took for them to reach the point where learning "the basics" of MS Office would only take ten hours of study & practice. We think it's easy because we're building on decent-to-good mental models of how computers & software & networks operate.

Normal people don't have those, and every second of the thousands of hours it'd take to gain them would be miserable for them. Not everyone enjoys this crap. Most aren't born with the kind of good abstract and/or spatial reasoning abilities that makes this stuff relatively easy to figure out, either.

"You can pass your life in an equable flow of happiness, if you can go by the right way, and think and act in the right way."

The "think in the right way" takes just a little practice. The "act in the right way" is the hard part, and the whole thing falls apart, in exactly the way you've noticed, without both. I've yet to achieve both, personally, though simply having "think the right way", with a little moderating wisdom from age, isn't nothing.

I think a trap in general with systems like Stoicism, or Zen Buddhism, or similar, is believing that thinking or knowing is anything more than one maybe-necessary-but-certainly-not-sufficient step.

(frankly, I'm not even sure what "go by the right way" means, yet, and would have to return to the original Greek to figure out whether it's just a summation of the two following ideas, or something separate—however, as I'm still working on "acting", I'll leave that for another day)

[EDIT] For those reading this without having read Meditations, it's heavy on duty and obligation, which is deep in the "doing" side of the above dichotomy. The "think the right way" is largely about ignoring that which one cannot control, but the trouble is that anything in the immediate past becomes "beyond one's control", which is where the parent's slipped-deadlines and such become easy to brush off without the duty-and-obligation and act-the-right-way habits balancing it out. Can absofuckinglutely confirm that if you get very good at the "think the right way" side, and only that side, it gets dangerously easy to not be bothered by failure or inaction.

Phoenix/Firebird was sold first through its incredible speed, compared to IE, plus popup blocking. The tabs were a nice bonus but the other two were the features that got all of us pushing the browser on every friend and relative who'd let us, even if they'd never use/understand tabbed browsing (some don't, to this day).

Not to pile on (as the idea isn't necessarily, immediately crazy):

1) The filesystem is a surprisingly decent datastore,

and,

2) Unless your write-volume is unreasonably high for a GH repo, your main problem is making sure your locking (and unlocking) is rock-fucking-solid; Git has built-in locking, but I bet Github has either replaced it or has some serious state-machine stuff going on to manage it outside of Git itself,

also and,

3) Reads on files are ultra-cacheable, obviously, and reads on HTML pages are too, and serving a second-or-two-stale read isn't a problem ~100% of the time in GH's use case, so read volume isn't really a problem.

[EDIT] source: have designed and developed a git-backed, client-accessible product at a much smaller scale than GH, but enough to see where the problems & strengths could/would be, at greater scale.

[EDIT EDIT] oh and with a bunch of clients using a bunch of different repos that effectively never interact except through normal git-push/PR behavior, obviously horizontal scaling is a breeze and a half. All you need is a little routing to figure out which repo is where. Git itself, plus your locking solution (whatever that may be), give you the tools you need to migrate from one server to another if you need to move a repo, probably with an unnoticeable amount of downtime (=locked repo) if you're clever about it.