I haven't been that surprised by something in a long time. Wow that is crazy. I made a little unfinished 3d Rubik's Cube site for fun a while back and the about section includes a link to his channel and some other older cubing channels. https://rubie-cubie.vercel.app/

I'm curious about your thoughts on omitting properties vs. setting them to `null` for a public facing API. I'm especially curious about your feelings on mixing and matching these strategies. Should you always stick to one strategy or is it ok to sometimes omit and sometimes use null to express the same idea that "the data is missing"?

An example of a null property:

    {
        "firstName": "John",
        "middleInitial": null,
        "lastName": "Doe"
    }

Compared to the omission of the property:

    {
        "firstName": "John",
        "lastName": "Doe"
    }

Essentially the idea discussed in this Stack Exchange post (ignoring the use of empty strings as an option): https://softwareengineering.stackexchange.com/questions/3437...

I felt the same way at first because I didn't know about wrap-reverse, but you can do it all using only the #pond selector

You might like noulith, a hobby language written by the person who won several of the recent Advent of Code events.

The about on GitHub reads "slaps roof of [programming language]* this bad boy can fit so much [syntax sugar] into it."

They even used the language in the most recent event Advent of Code and won. https://github.com/betaveros/noulith

To me the biggest reason is selector specificity, especially when it comes to authoring component libraries. Inline styles written with the style attribute are impossible to override without using !important, which only exacerbates the specificity problem.