Another leak in the JavaScript single-threaded facade (or a bug in Jest, really).
Asserting expect(...).toStrictEqual(...) fails with two structurally identical objects created by two different Node worker threads because their prototypes are not the same (though identical). Asserting expect(structuredClone(...)).toStrictEqual(structuredClone(...)) works.
Last time I looked, the docs were like "Elm for JavaScript developers" or at least "Elm for front-end developers", hence opaque to me. But the language has a lot of promise.
@henrikjernevad The only exception that springs to mind is that when it becomes necessary to generalise some code, it's sometimes worth going further than immediately necessary. 2/3
@henrikjernevad The criterion in this case should be to come up with a well-rounded abstraction (a good concept, if you like).
The trick is to consider what general extension the current extension might be part of and then ask the question: is the general extension simpler than the specific extension needed right now?
How can we judge simplicity? Two clues are if it's easier to document or easier to test.
I know, Git is a mess. But, since we're stuck with it, we may as well try to learn how it works with resources like this, which aims to lead to some form of Git enlightenment.
@amoroso After the initial couple weeks of steep learning curve, circa 2008, I have been happy with git and its slightly awkward "porcelain". I started with an intense practical session with some colleagues -- @nebhale will recall -- and then got a better mental model from https://eagain.net/articles/git-for-computer-scientists/ (works for mathematicians too).
(git switch -c was quite an improvement over git checkout -b for creating a new branch.)
@danielsiepmann@Anachron I wonder if there's an easy way to obtain an account's average posting frequency? I would take a punt on an infrequent poster but probably avoid the more prolific.
Made a breakthrough in how I think I can make this digital garden work. It always comes down to finding the right tool for the job, and I may have an idea of what might work for me.
Yesterday I read the recently published JSONPath RFC (RFC9535) and listening to an interview with one of the creators of SQL https://www.datacamp.com/podcast/50-years-of-sql-with-don-chamberlin and worst of all i poked around in sqlite code to figure out how the scheme table works...guess I just have to accept that I'm a query language nerd.
Spent the day trying to come up with a draft of the digital garden setup. It's been a tough one, because I'm not quite able to get to the point I’d like it to be.
But I'm resigned to making something to start with. Something I can improve when my skills and tools allow. So I'll keep plugging away at it.
@henrikjernevad@rjomara I've played with Logseq as an alternative to Obsidian. (Unfortunately, I can't find the resource requirements of either Logseq or Obsidian to know how big a VPS they'd need.)