Re:The State of JavaScript 2018
by jakelazaroff on Monday November 19, 2018 @10:54AM
(#18487245)
I find the "build your own framework" aspect of React to be as much a curse as it is a blessing. You can skip some of the bloat, but you also have to kludge together multiple libraries of varying quality to get the same things you'd get out of the box with a "batteries included" framework.
[ Parent
| on HN ]
especially for new developers and organizations. You have a choice between a wide-open landscape and a script that you're deathly afraid to eject because you can never go back. Neither is great for someone considering adoption for a new commercial product.
Re:The State of JavaScript 2018
by chrisweekly on Monday November 19, 2018 @01:36PM
(#18488571)
Yeah, I hear you about the "eject" problem for create-react-app. In CRA1, react-app-rewired emerged as a reasonable approach to no-eject config extension, but CRA2's switch to Webpack 4 (itself having moved towards zero-config) broke almost all the rewired plugins. There are solutions in the works (eg babel-plugin-macros), and alt approaches like Neutrino, but timing is tough right now as there isn't a clearly-established and well-lit path for good defaults plus low-maintenance config.