3 ms·
I've only seen one issue in React that affected me.. when they started requiring PascalCase for component names with JSX. Everything else has been really nice.
by tracker1 8y ago
I've only seen one issue in React that affected me.. when they started requiring PascalCase for component names with JSX. Everything else has been really nice. I glommed onto Redux and thunks pretty early on, and have been wrapping around fetch about as long. I used Bootstrap for a long time, and progressed to material-ui with very little disconnect. Those have been my personal preferences for several years, and they haven't changed THAT much in terms of usage.
Now that's nothing like I've seen with say Angular, Angular2-6 (including the long, painful Angular 2 beta cycle). I've also seen tooling evolve, and some of that painful... Webpack and Babel have changed a lot. create-react-app doesn't solve it all, but helps abstract some of it.
Node has had growing pains and is finally fairly stable for those developing/adapting native code to run in node.
I haven't really had to re-learn anything for a project as it's progressed any more than I did 15 years ago on the backend.
- acemarke 8y agoThe JSX transform has, as far as I know, _always_ required PascalCase for component names. That's how it distinguishes between "this tag name is actually a variable pointing to a component" and "this tag name should be turned into a string".
- tracker1 8y agoNope.. early on, you could use any local variable... there was a whitelist of html elements... they did a cleanup that required the PascalCase and defaulted to html element render for anything else. It was around 0.10 or so, iirc.