Both of the following examples show the same thing, but the SVG representation doesn't convey the structure:

JSON Canvas:

  {
    "nodes": [
      {"id": "a", "type": "text", "text": "Alice",   "x": 20,  "y": 50,  "width": 40, "height": 10},
      {"id": "b", "type": "text", "text": "Bob",     "x": 170, "y": 50,  "width": 40, "height": 10},
      {"id": "c", "type": "text", "text": "Charlie", "x": 320, "y": 50,  "width": 40, "height": 10},
      {"id": "d", "type": "text", "text": "Dave",    "x": 170, "y": 150, "width": 40, "height": 10}
    ],
    "edges": [
      {"id": "ad", "fromNode": "a", "toNode": "d"},
      {"id": "bd", "fromNode": "b", "toNode": "d"},
      {"id": "cd", "fromNode": "c", "toNode": "d"}
    ]
  }

JSON Canvas:

    graph primitive
    easier to read, write, and reason about
    harder to render

    path primitive
    easier to render
    harder to read, write, and reason about

https://codepen.io/ItIsHappy/pen/vEXrXxg

Yes, I'm being pedantic, but that was the point of my comment. SVGs aren't interactive by default, you need to bring your own interactivity.

For static content, SVGs work great, but for interactive content the additional sematic layer of JSON Canvas has a clear benefit. SVGs represent connections using paths, while JSON Canvas uses a graph. This means SVG cannot connect a single node to more than 2 adjacent nodes. If I want to draw arrows from Alice, Bob, and Charlie all to Dave, then I need to create a second Dave or reference to that location somehow. (You can see this in your sword example by moving one of the edge points. The sword delaminates because only two of the four edges at that point can be connected together.) SVG provides limited tooling for this, but it gets rather complicated rather quickly.

What a nightmare! Are your findings and this list of malicious extensions published somewhere?

If your linter is able to action requests, then it probably makes sense to add too.

I bet it sounds like a dial-up tone!

A single spreadsheet used locally is probably the best imaginable tool for answering "what if I changed that."

That same sheet shared across an organization suddenly becomes a game of "what caused that change."

They never said they didn't.

> Really, I am not a co-processor in a bus for you to dispatch a job to me and raise an interrupt line whenever the fuck you fancy doing it.

I am! I'm perfectly capable of managing my own time and shoeing others away if needed. Please bother me! That's why I have a cell phone and a salary.

Almost certainly relevant: I work in manufacturing.

Here's a line from my local library's site:

> Our auditoriums are provided as a public service for use by individuals, institutions, groups, organizations, and corporations for a small fee, when not being used for library-affiliated or sponsored activities.

To promote some further reading:

OKLab isn't actually a perceptually uniform colorspace. It's better than others, but it was specifically chosen as a tradeoff between accuracy and speed (hence the name OK). When you start digging this deep, you quickly learn that we have yet to invent any perceptually uniform colorspaces; even the most precise models we have end up using fits and approximations. Color has some really inconvenient properties like depending strongly on brightness and background. Frankly, given the differences in human biology (having orders of magnitude differences in relative numbers of each cone, for instance), it's surprising we agree as much as we do! Human color perception is an endless pit of complexity.

(Note, I don't say any of this to detract from what you've built here, merely expand. Your site is awesome and I love it!)

Nobody is "pretending" anything. These have all been around for 15+ years at this point. Your ignorance does not imply intent to deceive on others part.

The flickering in particular was fixed only on the logo example, but now exists on the Three D Light Source Position example as well.

For issues, may I recommend a more "human-in-the-loop" approach?

The entire Manim CE Logo example, the `x - x_1` text from the Brace Annotation example, all text from the Sin Cos Plot example, and the entire Heat Diagram example all flicker roughly once per second.

The text looks rather fuzzy, especially the large M from the Manim CE Logo example.

The Three D Light Source example also doesn't appear to have any functioning directional lighting.