I felt the “considered harmful” style of titles have been overused that no one would reasonably consider it anything but click bait; and so used it as ironic-click-bait.

Right. It's a tired trope at this point. Sort of like "disrupting" this or that business segment.

Naming collisions are a pretty real problem when you get to building large systems. They’re a big enough problem for something like CSS Modules to exist (explained further down in the post).

I considered exploring it but css selector performance just doesn’t matter with todays engines. There are far greater issues, and far better performance wins than “optimising your selectors”.

Makes sense, I would just worry that if I built my whole stack around this, suddenly I hit a breakdown point where I have a ton of attribute selectors and now adding new DOM elements to a content view takes a millisecond.

I'm more wary about this than I used to be since someone managed to accidentally cause tsc to need multiple seconds to compile a single file by making a small change to a type definition. Big O still can bite you!

Just to update everyone: the domain has been renewed and is being transferred over to my account (as the current lead maintainer). We’ll use some funds to ensure it stays active for a long time and this won’t happen again.

That’s awesome, great to hear.

Sorry to hear that Andrew. If you'd like to point me to issues or PRs where you've contributed and don't feel like you had a good response, I'd be happy to follow up on them.

Appreciate the sentiment, but I moved on a long time ago to some tools that I feel better suit my needs. Nothing but love for the project and good on you for keeping it breathing.

Hi, I'm the current lead maintainer of Chai.

We don't own the domain name, the previous maintainer/author does. It seems to have lapsed. There's not much I can do about that other than attempt to contact the previous maintainer, which I've done.

I am not sure if you know, but domain registrars have a policy that allows the organization or company to be able to get ahold of the domain.

For example, if the domain is registered under a former employee and you cannot get ahold of that employee, the organization or company can fill out a form provided by the registrar to gain access to the domain.

This would certainly apply to you, and you should be able to get ahold of the domain name (and renew it). You will need to provide certain documents in order to prove that your organization should have access to the domain. What is required depends on the registrar.

Also, I would contact the domain registrar and tell them that you'd like to pay for the renewal (so they will change the name servers back to your previous name servers) while the details are worked out about domain ownership.

If you have any trouble with ANY of this, get in touch and I will help you get it taken care of, you should be able to find me via a search for my user id.

The subdomain chai.js.org is available and it may be worth investigating that as an alternative. (https://js.org/ has more details)

Much love. I like chai a lot. Thanks for your work.

Since you're here, and the online docs are currently missing, do you know the best way to a stacktrace from a failed Chai assertion? Basically, if I do:

    import chai from 'chai';
    chai.config.includeStack = true;
    try {
      chai.expect(1).to.equals(2);
    } catch (e) {
      console.log(e.stack);
    }

In the REPL, I'm getting `e` as an AssertionError with a trace, but in my running code, the error is coming back as a vanilla object without a stacktrace. Sorry that this is clearly not the right forum for this kind of question.

Failed expectations always throw an AssertionError, and they always have a stack. It might be the test runner you have which is breaking or hiding the stack?

Thanks; figured it out. I was passing the object to a parent thread and the class properties were being removed in the process. Thanks for the help.

Deno uses uint8array (pretty much Nodes Buffers (Node Buffers subclass UInt8Array these days)) for almost all methods. For example Deno comes with `Deno.readFile` which returns a Promise<UInt8Array>, but they include the special case Deno.readTextFile because of how common it is to convert the contents to a string.

Ah of course, that seems obvious in retrospect. Thanks for clarifying it for me!

You can’t thickness plane plywood reliably. The laminations are often too thin and will tear apart in low spots, or uneven glueing on the laminations will cause it to delaminate. It’s likely to make more of a mess than a usable product.

Then of course there’s the issue that not everyone owns a thickness planer, or they own small planers which can only feed in materials smaller than, say, 400mm wide which adds likely too many constraints for these projects.

Exactly this. The idea was to consume as much complexity in the design and keep the build process as simple as possible so as many makers as possible with only a few tools could work with the designs.

That’s some good feedback! We’ll look into adding screenshots. As most of the components have no CSS (the ones that do are mostly layout, no theming) - they don’t look great, they are mostly useful for their behaviours.

We use Catalyst for internal components on GitHub.com, but we actually convert them to plain Web Components when we open source them, so that many projects (even those without catalyst) can benefit.

I'd like to gently encourage that perhaps the Catalyst forms be published too. I feel like we're getting the not-as-understandable, downcompiled, kiddie-script version of the real thing via this process, and that while open source, we're not getting an experience with how the sausage gets made.

Also it'd be lovely for those who are going in on Catalyst to have some well written robust components to either imitate or extend. And if multiple components are leveraging the shared Catalyst library, the marginal size of using a new component ought be significantly less.

Even without, thanks! Leaving Catalyst version available does seem like an excellent learning opportunity for all, & have some great technical upsides, but it's great that these components are available.