Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> so you can’t have a class attribute

Because it's a thin wrapper directly translatable into a JS function call. `className` is JS

 help



I know WHY it’s not possible, but that’s a design limitation of the parser being templating on top of JS, instead of a separate DSL with escape hatches for JS, like most other templating engines

It's not really a design limitation, as this way it simplifies the parser, the DSL, the templating... Basically everything. And your entire templating/parsing could be just "convert this to a function call"

Yes, it simplifies the engine, at the cost of developer experience. Like useMemo, that now is compiled in automatically with the new react compiler.

> Yes, it simplifies the engine, at the cost of developer experience.

Given that its taken the world by fire and nearly everyone adopted JSX/TSX as the templating language, doesn't seem like developer experience suffered.

> Like useMemo, that now is compiled in automatically

A completely different beast, and this one definitely makes DX suffer.


There are many reasons why JSX is popular, react being the biggest one, where subsequent frameworks wanted to leverage people’s knowledge.

However angular, svelte, vue and more have a specific DSL for templating.


`class` is a valid property name in JS, since ES5 (2009).

React opted for backwards compatibility at the time it came out, and never made the upgrade - you can write `class` in Preact.


> React opted for backwards compatibility

I think they opted for what these properties are actually called in Javascript: https://developer.mozilla.org/en-US/docs/Web/API/Element/cla...

I wish they'd stick with that for all properties though.


The rationale was to follow the DOM property names to avoid clashing with reserved keywords; not because mirroring JS was the goal. Data attributes for example have always been data-*, readonly, contenteditable in lowercase, mirroring HTML.

That is probably my bias showing, because I'd rather they adipted the JS property names for everything :) Less confusion



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: