I’m mainly looking at this from a performance perspective and the jsx spec, but I could see language tooling still being needed in the case of changes to the API with a compiler.

But I also understand the appeal, JSX has been around for a while and you would think it could handle statements and features we use regularly in JS in templates.

Even though there are some drawbacks of JSX, I think handling this with a compiler is more practical than changing the tooling space for what seems like a slightly improved developer experience.

Something to consider is this also would require a decent bit of tooling change in parsers like babel and vite plugins if you were to create a new spec and extension.

If we can somehow modify the existing spec but get the same benefit, like statements and closure state that would be great

Absolutely!

Animating things is hard. The course reveals how great animations borrow from familiar patterns around us and in the real world.

This is the stuff that gets noticed on projects, especially things like motion design which Josh's course covers incredibly well in an interactive way.

Reminds me of tails of iron

Out of curiosity, what would you call the component that has to the knobs on the XY pad?

I notice that it’s used a lot on the blog and course platform

If I recall I ran into some browser support issues with transform-box

Bills super bowl or chiefs three peat, I’d be happy with either one :)