3 ms·

I'm a bit weary of this project since neither the website nor the readme mention any tradeoffs. Surely, if I choose Nerv over React I miss out on something—what

by mxstbr 9y ago

I'm a bit weary of this project since neither the website nor the readme mention any tradeoffs. Surely, if I choose Nerv over React I miss out on something—what is that something? Why would I _not_ use Nerv? Opened an issue, hoping one of the authors chimes in and clarifies: https://github.com/NervJS/nerv/issues/10 https://github.com/NervJS/nerv/issues/10

mxstbr 9y ago
Thinking about this more, the React team recently (for the v16 rewrite) rewrote almost their entire test suite to use their public API. I wonder what'd happen if you ran that test suite with Nerv—if it passes all those tests that'd be a great confidence booster! Anybody up for trying?
- e12e 9y ago
  Wasn't aware of the major v16 rewrite (I'm not working on a react front-end at the moment). But seeing overviews like: https://dzone.com/articles/react-16-release-whats-new https://dzone.com/articles/react-16-release-whats-new (also: https://reactjs.org/blog/2017/12/15/improving-the-repository-infrastructure.html https://reactjs.org/blog/2017/12/15/improving-the-repository...) makes me much more positive towards react - feels like there's some people taking the stuff quite seriously. Still not sure about the whole js idea, portable code that's unsigned etc - but things like this feels a little less... Cowboys and cool-aid than I'm used to from the js side of things. Some discussion here that I missed: https://news.ycombinator.com/item?id=15339983 https://news.ycombinator.com/item?id=15339983
  - acemarke 9y ago
    Yeah, the React team takes backwards compatibility very seriously. They did finally drop some deprecated methods from the main package in React 16, but made them available as separate packages, and even wrote codemods to automatically replace usages. I can recommend several resources for understanding the changes in React 16: - Lin Clark's fantastic ReactConf presentation on "A Cartoon Intro to Fiber": https://youtu.be/ZCuYPiUIONs https://youtu.be/ZCuYPiUIONs - The official announcements for React 16: https://reactjs.org/blog/2017/09/26/react-v16.0.html https://reactjs.org/blog/2017/09/26/react-v16.0.html and https://code.facebook.com/posts/1716776591680069/react-16-a-look-inside-an-api-compatible-rewrite-of-our-frontend-ui-library/ https://code.facebook.com/posts/1716776591680069/react-16-a-... - A good summary of the major changes: https://www.infoq.com/news/2017/05/react-fiber-closer-look https://www.infoq.com/news/2017/05/react-fiber-closer-look - Two articles looking at the user-facing features and changes: http://www.benmvp.com/slides/2017/reactboston/fiber.html#/ http://www.benmvp.com/slides/2017/reactboston/fiber.html#/ and https://www.robinwieruch.de/what-is-new-in-react-16/ https://www.robinwieruch.de/what-is-new-in-react-16/
codingdave 9y ago
> hoping one of the authors chimes in and clarifies That is an example of exactly why not - the support behind React is huge. Even if we take their word that Nerv is great from a technical perspective, it doesn't have the same level of community support. Not that I am suggesting we ignore anything new just because it has a smaller community... just pointing out a downside that should be considered before using it on production projects.

by mxstbr 9y ago

mxstbr 9y ago

Thinking about this more, the React team recently (for the v16 rewrite) rewrote almost their entire test suite to use their public API. I wonder what'd happen if you ran that test suite with Nerv—if it passes all those tests that'd be a great confidence booster! Anybody up for trying?

e12e 9y ago
Wasn't aware of the major v16 rewrite (I'm not working on a react front-end at the moment). But seeing overviews like: https://dzone.com/articles/react-16-release-whats-new https://dzone.com/articles/react-16-release-whats-new (also: https://reactjs.org/blog/2017/12/15/improving-the-repository-infrastructure.html https://reactjs.org/blog/2017/12/15/improving-the-repository...) makes me much more positive towards react - feels like there's some people taking the stuff quite seriously. Still not sure about the whole js idea, portable code that's unsigned etc - but things like this feels a little less... Cowboys and cool-aid than I'm used to from the js side of things. Some discussion here that I missed: https://news.ycombinator.com/item?id=15339983 https://news.ycombinator.com/item?id=15339983
- acemarke 9y ago
  Yeah, the React team takes backwards compatibility very seriously. They did finally drop some deprecated methods from the main package in React 16, but made them available as separate packages, and even wrote codemods to automatically replace usages. I can recommend several resources for understanding the changes in React 16: - Lin Clark's fantastic ReactConf presentation on "A Cartoon Intro to Fiber": https://youtu.be/ZCuYPiUIONs https://youtu.be/ZCuYPiUIONs - The official announcements for React 16: https://reactjs.org/blog/2017/09/26/react-v16.0.html https://reactjs.org/blog/2017/09/26/react-v16.0.html and https://code.facebook.com/posts/1716776591680069/react-16-a-look-inside-an-api-compatible-rewrite-of-our-frontend-ui-library/ https://code.facebook.com/posts/1716776591680069/react-16-a-... - A good summary of the major changes: https://www.infoq.com/news/2017/05/react-fiber-closer-look https://www.infoq.com/news/2017/05/react-fiber-closer-look - Two articles looking at the user-facing features and changes: http://www.benmvp.com/slides/2017/reactboston/fiber.html#/ http://www.benmvp.com/slides/2017/reactboston/fiber.html#/ and https://www.robinwieruch.de/what-is-new-in-react-16/ https://www.robinwieruch.de/what-is-new-in-react-16/

codingdave 9y ago

> hoping one of the authors chimes in and clarifies That is an example of exactly why not - the support behind React is huge. Even if we take their word that Nerv is great from a technical perspective, it doesn't have the same level of community support. Not that I am suggesting we ignore anything new just because it has a smaller community... just pointing out a downside that should be considered before using it on production projects.