> To protect the privacy of our members, their data, and to ensure site stability, we do look for extensions that scrape data without members’ consent or otherwise violate LinkedIn’s Terms of Service.

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

It's interactive, for starters. You can do that with SVG, of course, but the boilerplate required would be larger than the `.canvas` file. You can externalize the boilerplate, but then you're no longer creating portable SVG files, and if we're going to create an SVG-like DSL we may as well try out this JSON-like DSL.

Interactive like this? https://yqnn.github.io/svg-path-editor/

I still don't see your point. Why wouldn't I always choose SVG? What problem or pain point is being solved?

It's not interactive for me:

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.

Cool, now show me a codepen with an interactive JSON Canvas?

This isn't obvious to me. You can have javascript external to the svg for making it interactive, it doesn't have to be embedded in the svg. And the interactivity for json canvas isn't embedded in the canvas json either.

If we're adding external interactivity, we're treating each as a custom DSL format and need to evaluate them as such:

JSON Canvas:

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

SVG:

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

I suspect vibe coders might actually want you to consider turning to Claude for accountability and ownership rather than the human orchestrator.

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

It's sending sound parameter information (e.g. filter cutoff at 12khz, resonance at 1.6, Q of 0.89) along with note information (e.g. start playing note A4 with velocity 80). You could absolutely use a MIDI CC channel to convey this information. The OP-32 chooses a different route and encodes this into an audio signal so that it can transmit it over the air using the speaker/mic instead of a wireless stack.

I bet it sounds like a dial-up tone!

For better or worse...

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."

So, what does having inference done by NVIDIA directly add?

> Can't you fucking do your homework beforehand, think your idea thoroughly, and then have at least a small written paragraphs about it before interrupting your colleagues.

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.

They could be!

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.

I'm colorblind, but I ended up getting a 0.0028 "much better than average" score. Hmm... Fun site!

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!)

CPython (the compiler) is the most popular implementation of Python (the language) like GCC, Clang, and MSVC (compilers) are implementations of C (the language). Other Python implementations include PyPy, Jython, and IronPython.

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.

saying the most popular hides the actual reason why it is popular though. it is the original python implementation. it defines the standard and functions a reference for all others. for better or for worse other implementations have to be bug-compatible with it, and that is what puts them not on equal footing.

for C compilers no reference implementation exists. the C standard was created out of multiple existing implementations.