465 karma · joined August 25, 2021
As if they didn’t already get enough negative attention.
It’s like Asimov’s entire timeline, a series of visionaries steering the world in the direction they want. Except there’s an additional challenge, in that they have to act without derailing Seldon’s goals. I think the books do a great job of showing that conflict.
Edit: agreed about the battle of wits aspect, but that’s also just Asimov being himself.
I can't figure out if you're talking about a nuclear war changing the world, or a nuclear disarmament process that somehow also leads to energy production.
A prof had to ask me to set it back because they couldn’t figure it out.
A few years ago, trying to have the same conversations on reddit, everything degraded into personal attacks eventually.
In my region(s) of France, they either suck or only play very big names. I envy people who live in range of a good local radio.
It's its own form of exploration, at least in the versions with fun cave generation: you always end up in some cave complex that you can then explore. But I'm happy to see that it's less needed now, because interesting caves are more commonly accessible from aboveground.
- Alt-Tab takes between 0.1 and 2 seconds to work, apparently at random. Windows are skipped, also at random, so I can't predict which window I'll get. I can't even switch to another window and back; most of the time, the order will get messed up.
- Bringing up the notification pane and the overview with all desktops sometimes works instantly, sometimes stutters and takes 3 seconds. The animations are always half-baked and awful to follow.
- Switching desktops with Ctrl+Win+Arrows sometimes seems to re-organize all windows at random, for no reason at all.
These issues usually happen a few weeks of heavy use after install. I don't have any third-party software that messes with Explorer. Re-installing fixes them for a few days or weeks. That was on a Dell XPS 15 with a Core i7 and 16GB of RAM, and it also happens with my larger, well-cooled workstation at the office.
macOS has its own multiple-desktop weirdnesses, but in general it's polished and works predictably on my M1 MBA. Windows was just painful to use, mostly because of the above issues. It seems like UI features have a lot of inefficiencies that Microsoft can't or won't factor out.
Also, Windows 10 desktops can't be re-organized, which I imagine would be trivial to implement, and makes the macOS desktops much more practical.
I don't follow that. In a Dockerfile, I want to install software, and software is usually distributed in packages like .deb. Why can I `RUN apt-get install libabc` and have a clean, automatic install of libabc, but not do the same with a libabc.deb file on my host filesystem?
> It sounds like you want a mechanism for COPYing all filesystem changes resulting from a RUN instruction without having to know what those changes are ahead of time.
That's one way of doing it, but it's more complex than the obvious solution:
> I don't follow the part about mounting a host dir in the build (how it would help)
It simply lets me give the build container access to libabc.deb, so I can `RUN apt-get install /mnt/host_folder/libabc.deb`, which will install libabc without putting `libabc.deb` itself in an image layer.
It would have been trivial to add this, but the Docker devs rejected it because "multi-stage builds can do this" (wrong), and it would lead to "non-reproducible builds" (because downloading packages from the network is somehow more reproducible?).
They finally added it as a non-standard option, which means a build process that relies on it won't work with a Docker install that uses the default config. It's the devs making it needlessly hard to use Docker for a perfectly valid use case.
If you're wondering why I want to install that locally-built software via a .deb, it's because we want to distribute it to all our systems, and we want to have only one packaging method to maintain.
Do you mean os.path, pathlib.Path, or something else? I use pathlib.Path all the time and never get filesystem errors anymore, it's really practical.
Copying a list of paths will break if the package changes, and it can’t easily do anything done by pre-install and post-install scripts (like changing a file, registering a GPG key, etc.)
The official excuse from Docker is that “multi-stage builds cover that use”, but that’s not true if you need to install local packages. I think the buildkit feature that lets you mount folder in the build container is a hidden admission that this is wrong, but it’s annoying that the build process will then only work on machines where a non-standard option is set.
docker-compose is just one folder per service, much more practical.
Edit for details: `Σλ∀φ` is a chore to read for me. These letters only make sense if I've absorbed the author's notation beforehand, like in a math proof. I parse the snake case version instantly, because my brain is trained for that. And I understand it much more quickly, because it says exactly what the function does in the way I would represent it in memory.