Hacker News Reader

Comment by breck | Hacker News Reader

The core React design pattern is nice, and the community is great, but the noise in the code.

What do you mean by noise?

Sh*t that sounds nice, but when stretched outside the simple documentation, has no purpose or meaning and ruins your life.

I’m looking at you -> { blah && }

What's the matter with that notation? I work in a code base many millions of lines large, see those every day, and think nothing of it.

The noise is the code.

Play the spaces between the notes.

Old school Perl coder here - rolling my eyes... ;-)

The Pathologically Eclectic Rubbish Lister.

Talk to a sendmail v8 admin who had to hand edit sendmail.cf rewrite rules.

With or without m4?

Without m4. You'll likely speak to a gibbering mess though.

I’m triggered.

This is just personal opinion: The one-way flow has made functional React components very noisy in terms of state and effects management.

For examples, here's a comparison implementing the same functionality using React hooks and Svelte: https://github.com/joshnuss/react-hooks-in-svelte

Now, there are ways to handle all this with less code in React as well (for example, MobX), but the current de facto defaults with hooks and Redux create so. much. boilerplate. for. every. little. thing.

I like and use React on almost a daily basis but I'll admit it can definitely be overly verbose sometimes (at least WidgetFactoryFactory's aren't common like in some other languages). I know next to nothing about Svelte though, I'd be interested to see how it compares to React in a complex app and what the big tradoffs are.

I think it's safe to say React wins on ecosystem but loses on verbosity w.r.t Svelte.

Reply on news.ycombinator.com