Comment by phist_mcgee
Comment by phist_mcgee 6 months ago
Entirely subjective and I would disagree with dart. JSX is one of the most important things react ever popularised in the frontend space.
Comment by phist_mcgee 6 months ago
Entirely subjective and I would disagree with dart. JSX is one of the most important things react ever popularised in the frontend space.
What do you find attractive WRT JSX versus other templating syntax?
Perfect world:
JS and CSS compile to native, somehow.
My ability to do this
function App() () { const items = get(url); render(items) }
Does not exist on native. It's 2025. Why is this?
----
It's because we don't have literate programmers. They don't know how to speak CLEARLY.
>It's because we don't have literate programmers. They don't know how to speak CLEARLY.
Mate, I think this is a bit of a reach.
It's a vent. I don't like writing comprehensive code for simple things. Philosophically, I believe code is a liability. Each line is a problem.
The article alludes to something people do. They wrote a whole lot of code to not write a whole lot of code. These are deep stories.
I suspect you maybe haven’t used Dart then because it’s genuinely not even close. I know in a philosophical sense everything is subjective when you squint hard enough but I’m also talking about very clear and concrete things.
Just to give one simple example. Take the concept of a mixin where you want to essentially create a partial class interface and use it for basic composition. An incredibly straightforward 101 level OOP concept.
Then take a look at how it works in Typescript here:
https://www.typescriptlang.org/docs/handbook/mixins.html
and contrast that with how you do the same thing in Dart here:
https://dart.dev/language/mixins
I’ve got extensive experience with both. I promise you Dart is much much much nicer to work with on every relevant metric I can think of.