Does anybody like React? • Hacker News Board

Re: Does anybody like React?

#351

Post by digitaltrees » Mon, Jun 01, 2026, 4:36 AM UTC

snemvalts wrote: post #197

lwansbrough wrote: post #100

Earlier quoted context omitted.

It does, if you care about ergonomics. The reactivity model is simpler and arguably less error prone. It does have its own templating syntax, which is trivial to learn. No more cumbersome to learn than JSX, which is a templating language designed by the React team. Not sure why you chose to make the distinction between JSX and Vue’s DSL as if JSX wasn’t developed for the sole purpose of facilitating React’s virtual D…

JSX is a very thin layer of templating logic inside JS. Meaning you have all the language features available while templating. Some arbitrary JS can result in templating. Vue's DSL is whatever language the developer implemented. Which is probably not enough, depends how much effort they put into it and how good they are in language design. Given that they cargo cult HTML tags to organize components in a pseudo-famili…

Sorry but JS is, and always has been, a crap language many are trying to escape. So saying react has the full power of JavaScript is an antipatten as far as I am concerned. Vue is better designed.

Re: Does anybody like React?

#352

Post by snemvalts » Mon, Jun 01, 2026, 8:24 AM UTC

Lukas_Skywalker wrote: post #220

snemvalts wrote: post #197

Earlier quoted context omitted.

JSX is a very thin layer of templating logic inside JS. Meaning you have all the language features available while templating. Some arbitrary JS can result in templating. Vue's DSL is whatever language the developer implemented. Which is probably not enough, depends how much effort they put into it and how good they are in language design. Given that they cargo cult HTML tags to organize components in a pseudo-famili…

While I understand the advantage of using the built-in language features (and I know why it is required to be done that way), I still think using {enable && } for conditional rendering, or {collection.map(x => } for looping are not the most obvious choices. If you ask people how conditionals and loops are written in JS, you will get 'if' and 'for' or variants of 'while'. So I get where the v-if and v-for are coming f…

Let's say you to render conditionally when `x` is present. You do `v-if="x"`. Now you want to refer to `x.y.z` in the body, while `y` is optional.

Can you be sure that the value is present? How do you check for it? What does Vue need to do to enable this functionality with static type checking with TypeScript?

With `{x && {x.y.z}}`, it's almost vanilla TS, it's the same as `x && x.y.z` in normal TS. Type narrowings that work in TS are guaranteed to work in React, without the framework having to do anything.

Less framework/library code required to make the same thing work. To me, that's the sign of a better abstraction and implementation.

Re: Does anybody like React?

#353

Post by BartBM » Wed, Jun 10, 2026, 7:23 PM UTC

em-bee wrote: post #347

WorldMaker wrote: post #344

Earlier quoted context omitted.

I was more of a fan of Durandal, which was Aurelia's predecessor. It was a SPA wrapper around out-of-the-box Knockout. It seemed cleanly focused and was useful in that you didn't need to learn a different view engine if you were already using Knockout. Following Rob's blog because of Durandal was a part of how I landed on "try to avoid Angular" and it did give me Aurelia as a bit of arsenal to say "hey, this framewor…

makes sense. i was obviously coming from angular, and as i said before, i did look at knockout and i found angular was the better choice. so i guess aurelia's appeal then came naturally. but then i didn't know about durandal, so i can't say how much i would have liked it. but this tells me that angular had a stronger influence on aurelia than i was aware of. that's not surprising of course, but still interesting.

As a React developer, I think Aurelia 2 is the best JS/TS framework today. I always use Aurelia for personal projects.