4 ms·
Agreed - I also found React a bit clunky with the explicit getters/setters compared to Angular. JSX is a bit of a weakness IMO - I absolutely rather have templ
by Bahamut 11y ago
Agreed - I also found React a bit clunky with the explicit getters/setters compared to Angular.
JSX is a bit of a weakness IMO - I absolutely rather have templates in separate files to reduce complexity/concerns located in a file. It also adds build tool complexity, which there is too much of in frontend currently.
Otherwise, working in React is generally clean, but one can get that benefit by utilizing ES6 modules in general. React brings a lot of good things to the table, which is probably best exemplified by Angular 2 pulling a lot of ideas from it.
- woah 11y agoWho's stopping you from putting your jsx in a seperate file?
- Bahamut 11y agoBuild tool complexity is what I dislike - it's certainly possible, but the trend I dislike is build tooling increasing complexity of the build system of the frontend, decreasing accessibility for onboarding developers. JSX is an unnecessary offender in this department, bringing us farther away from plain HTML.
- iyn 11y agoHave you seen Webpack (https://webpack.github.io/ https://webpack.github.io/)? It's a very powerful tool, but it's quite simple to start with. I can recommend this tutorial: https://webpack.github.io/ https://webpack.github.io/
- iyn 11y agoHa, I just realized I posted the same link twice. This is the link to the tutorial: https://github.com/petehunt/webpack-howto https://github.com/petehunt/webpack-howto
- hobby_body 11y agoWhy use JSX at all, then? var d = React.DOM; d.div(null, 'Hello', d.strong(null, 'World'))