Why not JSX?

[Rich-Harris]

I really need to write this blog post, because I'm bored of answering this question

[karanganesan]

What !!! Is this even a question ??? 🙈🙈🙈

[karanganesan]

@developit would like to share some thoughts about this question ? 😅😊

[vedam]

directly followed by

• why not mobx, hooks, router or what-not
• why not css-in-js
• why no typescript, devtools-support
• why not fill-in-what-you're-used-to

[karanganesan]

• why not coffescript

because the code get even more smaller with CS removing let and even the semicolon 🎉

<script>
    name = 'world'
</script>
<h1>Hello {name}!</h1>

so that even Hello World program can get smaller 🌠

[karanganesan]

New blog post name : Why not X?

@Rich-Harris it's better this way so that it answers all questions 🖖

[akaufmann]

@Rich-Harris
It's sad, but you can't win this fight. I think, maybe a blog post on why HTMLx is great - without mentioning JSX and why it's better than (JS)X - can achieve more? What do you think?

@vedam

why no typescript, devtools-support

No, this blog post should be: Why Typescript and good DevTools support is a high priority for us and you can expect it soon. 😉

PS: Thanks Rich, Svelte v3 brings fun back to development. Write Less Code, Get More Done 💯

[PaulMaly]

Btw, about TS, you can try this: svelte-ts-preprocess. Example of usage included in monorepo.

[pngwn]

I don't know if Rich meant for this to become a discussion issue but I just thought I'd say: Svelte could never use JSX, it fundamentally wouldn't work because JSX is just sugar over render functions. This wouldn't work for Svelte.

When Rich does get around to writing this article, I think we'll see the main reason Svelte doesn't use JSX is technical.

[Conduitry]

Hey chill out everyone. Rich being bored of answering this question does not mean let's have a bunch of opinions about something that is already settled.

[Rich-Harris]

Happily, most people are also bored of asking it. All you have to do is wait 5 years, it turns out