3 ms·

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

by davedx 10y ago

ben_jones 10y ago
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.
- beaconstudios 10y ago
  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.
  - ben_jones 10y ago
    No clue, haven't used vuex yet :/ .
    - beaconstudios 10y ago
      ah ok, no worries - I think it's similar to Redux largely, which unfortunately includes being severely incompatible with nested state values.
      - girvo 10y ago
        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
        beaconstudios 10y ago
        I'd never thought to use lenses for this. Thanks for the advice, that actually really helps!
twsted 10y ago
> including the latest Vue hype I don't see anything here exceeding the hype on React...
xaduha 10y ago
> including the latest Vue hype yeah, what's about that? AFAIK Vue isn't new and wasn't that special back then.
- IanDrake 10y ago
  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.
  - tracker1 10y ago
    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.
carlosdp 10y ago
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.
tracker1 10y ago
Well, Vue is a different approach... I find Vue closer to WebComponents than to React.

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

by davedx 10y ago

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

ben_jones 10y ago

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.

beaconstudios 10y ago
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.
- ben_jones 10y ago
  No clue, haven't used vuex yet :/ .
  - beaconstudios 10y ago
    ah ok, no worries - I think it's similar to Redux largely, which unfortunately includes being severely incompatible with nested state values.
    - girvo 10y ago
      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
      - beaconstudios 10y ago
        I'd never thought to use lenses for this. Thanks for the advice, that actually really helps!

twsted 10y ago

> including the latest Vue hype I don't see anything here exceeding the hype on React...

xaduha 10y ago

> including the latest Vue hype yeah, what's about that? AFAIK Vue isn't new and wasn't that special back then.

IanDrake 10y ago
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.
- tracker1 10y ago
  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.

carlosdp 10y ago

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.

tracker1 10y ago

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