Re:Upgrading from React 0.11.2 to 0.14.7 in 347 easy steps
by Touche on Saturday February 27, 2016 @05:13PM
(#11188756)
> Except React has been getting simpler with each release. First there was React.createClass. Then came ES6 classes. Now components can just be pure functions.
That's a pretty shallow definition of easier.
Re:Upgrading from React 0.11.2 to 0.14.7 in 347 easy steps
by funkysquid on Saturday February 27, 2016 @06:27PM
(#11188983)
Agreed - it seems like the largest problem they faced was using Scala build tools - so it's funny the blame is placed on Javascript.
Re:Upgrading from React 0.11.2 to 0.14.7 in 347 easy steps
by AgentME on Sunday February 28, 2016 @01:11AM
(#11190066)
>If you mean the toolchain, the keynote at React.js Conf made it clear that improving that part is a major goal for 2016
Then people will just complain there's yet another build tool, because progress or any change is bad!
Re:Upgrading from React 0.11.2 to 0.14.7 in 347 easy steps
by zaphar on Sunday February 28, 2016 @10:49PM
(#11193494)
If your only method of improving something is to rewrite it or add another layer then something has gone horribly wrong and people have a right to complain about it. I sincerely hope that the improvment's are not a rewrite or an additional layer to an already dangerously complex system.
Also, the author is using a Scala toolchain to build the JS frontend code. The standard toolchains (with the exception of Google Closure and Facebook's Flow) are all built around node.js.
There are even a number of code migrations available for React: https://github.com/reactjs/react-codemod -- but of course even those can't help you if you use non-standard tooling and let a web frontend codebase collect dust as browsers (and your dependencies) march forward.
Projects are never finished. If you cease working on a project, it just becomes unmaintained code.
EDIT: As someone seems to have flagged my account and I'm now apparently limited to two replies per hour or something ridiculous like that (yay for passive aggressive moderating tools?) my reply comes as an edit:
> That's a pretty shallow definition of easier.
It's a library that lets you describe DOM subtrees based on application state. How much simpler could it possibly be?
If you mean the toolchain, the keynote at React.js Conf made it clear that improving that part is a major goal for 2016 but none of that will help you if you want to solve everything with your existing Scala tools.