Hacker News Reader

Comment by zyxzkz | Hacker News Reader

I don't think the problem with React is with the DOM aspect, it's state management and persistence where things get bogged down conceptually.

View on HN

React is pretty damn good. I don't really see the problem all these clones are trying to solve, including the latest Vue hype.

Going to digress a bit but I'm working on a project in Vue and while at first it seemed like a literal breath of fresh air I came to the awful conclusion that no matter what SPA framework/library you're using, if it's javascript, you gonna be using webpack + a medium size build pipeline for es2015, jade, scss, bundling, file watching, hot-reload etc. The arguments for small libraries aren't as strong anymore because the advantages of the larger ones have enough cost/benefit that you're going to be pulling them in EVENTUALLY so might as well do it from the beginning.

You don't happen to know how to get vuex working idiomatically with deeply nested data do you? I can work with it but only if I start passing around object references, which seems like a terrible idea.

No clue, haven't used vuex yet :/ .

ah ok, no worries - I think it's similar to Redux largely, which unfortunately includes being severely incompatible with nested state values.

In redux I use functional lenses to create composoable getter/setter functions to handle deeply nested data safely. I do that even without redux, but it is very useful there. Take a look at the lens functions in Ramda, or safety-lens

I'd never thought to use lenses for this. Thanks for the advice, that actually really helps!

Yea agreed, super confused on what's wrong with React. I know the renderer is being re-worked, but that only matters for Facebook-sized projects afaik, which 99.9% are not.

> including the latest Vue hype

I don't see anything here exceeding the hype on React...

> including the latest Vue hype

yeah, what's about that? AFAIK Vue isn't new and wasn't that special back then.

I've only previewed vue at this point so I can only say this about why it's "better": preference.

When I looked at vue2 I saw a lot of the same features as angular2 except the binding syntax looks better to my eyes and way of thinking.

When I look at jsx I go cross-eyed.

When I look at HTML, I want to "see" the view and construct it in my head. I don't want JavaScript mixed in it.

Note: I realize vue and angular bindings are essentially JavaScript in attributes, but they can (and should) be minimal and fade into the background IME.

If you look at React components as components, it makes a bit more sense, at least to me that the view rendering is part of the component, and not the inverse.

Well, Vue is a different approach... I find Vue closer to WebComponents than to React.

Thanks for reaction. I think so too. But other vdom implementaion is more bad things, like riot. React state and props system is not bes, but it's easy to use and understand for javascript developers. I think reactjs is enter maturity stage not bogged down.

Why? I don't think it is.

Reply on news.ycombinator.com