haradion

5 ms·

1.
by haradion 8mo ago
It doesn't really hurt in practice because it's only one part of the full backup procedure. Deduplicate to save space; re-duplicate the (smaller) backups to separate media for redundancy; scrub regularly for bit rot and rotate you
2.
by haradion 9mo ago
If you squint hard enough, this is really a pretty similar idea to Polkit [0] but with a much simpler communication layer. [0]: https://polkit.pages.freedesktop.org/polkit/
3.
by haradion 10mo ago
> All these named reset types could just be two separate reset commands, both pointing to a commit, one resetting the files on disk, one resetting the index. It sounds to me like you want `git restore -W` and `git restore -S`.
4.
by haradion 11mo ago
For the compiler in particular, it's pretty common practice to depend on a recent version. The backward compatibility situation is generally excellent, so the only real challenge is getting the compiler installed. That's generall
5.
by haradion 1y ago
With the right workspace mapping, you can pull in just part of the depot, which makes the repo size a lot more manageable.
6.
by haradion 1y ago
The Unison programming language is built around that idea: https://www.unison-lang.org/docs/the-big-idea/
7.
by haradion 1y ago
YMMV, naturally, but I've found that some embedded devices have really excellent hardware abstraction layers in Rust that wrap the majority of the device's functionality in an effectively zero-overhead layer. Timers? GPIO? Serial
8.
by haradion 1y ago
> or that third type of schema whose name escapes me RRELAX NG, perhaps?
9.
by haradion 1y ago
Well, for one thing, classic Outlook's HTML rendering engine (to the extent it's even an "HTML" rendering engine instead of a Word document rendering engine) has some fairly radical divergences from standard HTML/CS
10.
by haradion 2y ago
> The logical model is identical for every source control system. Most source control systems have some common logical concepts (e.g. files and directories), but there's actually significant divergence between their logical models.
11.
by haradion 2y ago
The file contents are logically distinct blobs. Packfiles will aggregate and delta-compress similar blobs, but that's all at a lower level than the logical model.
12.
by haradion 2y ago
Especially with Vue 3, most of the reactive state management you need for all but the largest and most complex of apps is built right into the core. Vuex and Pinia really aren't necessary for most users.
13.
by haradion 2y ago
OpenSSL does provide a callback mechanism to allow for key logging, but the application does have to opt in. IIRC, at least Curl does support it by default.
14.
by haradion 2y ago
I've found MDN and the Rust programming language docs to be pretty solid.
15.
by haradion 2y ago
I've found Nushell ( https://www.nushell.sh/ ) to be really handy for ad-hoc data manipulation (and a decent enough general-purpose shell).
16.
by haradion 3y ago
`git range-diff` can be handy for the reviewer when trying to "recover from" a mid-review force-push.
17.
by haradion 3y ago
I've got both a Metropolitan and a Prera, and I can second (third?) this recommendation. Fantastic pens.
18.
by haradion 3y ago
For the specific use case you're describing, I've found `git worktree` to be very useful. Overall, at least when it comes to features, I've actually had the opposite experience. That said, I'm one of those people such th
19.
by haradion 3y ago
Shallow/sparse clones help with some of the pain points there, at least around time to clone and local repo size.
20.
by haradion 3y ago
At least by Wikipedia's chosen sources [0], the attempted assassination of Gov. Boggs was linked, via circumstantial evidence, to Joseph's bodyguard, Porter Rockwell (who, even within the "Mormon" Church, is considered a
21.
by haradion 3y ago
By mainstream Christian standards, the doctrine is, quite frankly, "heretical", but members of The Church of Jesus Christ of Latter-day Saints (the primary branch of "Mormonism") very much consider themselves Christian,
22.
by haradion 4y ago
At least for (unlocked) flake sources, you could probably use a branch naming convention instead of a separate database, although that requires your repo to be set up a specific way.
23.
by haradion 4y ago
In my experience, this often indicates a poorly-fitting cut. If your belt naturally sits below your hips, you'll probably want jeans specifically designed for that.
24.
by haradion 4y ago
The same thing applies to any binaries downloaded from their site, so unless you you've got signed binaries (that use an independently obtained/verified chain of trust), trusting the server is your your only option. Even with sign
25.
by haradion 4y ago
Sure, in many cases. Depending on the situation, though, it may be no more hassle than any other USB GPIO device, so it's a decent enough cheap solution if you can't or don't want to use a Pi or a similar SBC.
26.
by haradion 4y ago
A little microcontroller with USB support (I like the Raspberry Pi Pico) can help with your GPIO woes.
27.
by haradion 4y ago
Your experience with NixOS mirrors mine. I got hibernation working with a little fiddling. Suspend-then-hibernate also mostly works but occasionally turns my laptop sleeve into an Easy-Bake oven, so I've started triggering hibernation
28.
by haradion 4y ago
When you follow the restrictions on stackless coroutines, the coroutine can, as you mentioned, elide stack allocations for the "child" coroutines. If you want to make a call that can't have its stack allocation elided, you ex
29.
by haradion 4y ago
> I mean, with "traditional" coroutines, it isn't the "language's runtime" which calls back into my code: it is whatever code completed the event. I get that the important part of this sentence is the intere
30.
by haradion 4y ago
You might think of Rust's async paradigm as "half a continuation, turned upside down". With traditional coroutines, after an async operation completes, the language's runtime calls back into your code, and you actively c

More ›