JSX can be syntax highlighted and linted easier.
What if a variable that is being referenced is missing at that time in the component's lifecycle?
JSX makes so much more sense, making code the parent of the template, instead of keeping code and template as siblings.
This has been a debate since long before React or Angular existed. Keeping code and templates together typically makes sense to programmers while keeping the template as html in a separate file means you can edit it in any html editor, no special tools needed. I've always been partial to keeping them together, but working with designers who prefer it the other way, I can at least respect where they are coming from.
Re:Angular v16
by paulddraper on Thursday May 04, 2023 @10:43AM
(#35816152)
I mildly agree.
I note that Vue and Svelte have the same issue, and yet I rarely hear this criticism of them.
> requiring multiple files for "hello world"
False (unless you're counting angular.json conf file for Angular CLI??)
> It uses invalid HTML, with attribute syntax including brackets and parentheses
And what, JSX is valid HTML????
FWIW Angular templates is completely valid HTML. (The only non-standard thing is that the attributes are case-sensitive.)