React is a great tool, but it isn't appropriate for a lot of projects.
For example, how do you bind a WebGL game engine to React UI state without duplicating your engine code into Redux or wrapping everything with observables, like with mobX?
Webpack can't build a proper ES6 library (yet), so modulizing React applications is a whole fun thing. Could you toss Webpack for your create-react-app starter, implement Rollup with Babel and make an ES6 library to work with the rest of your front end code? Yeah, but that's gonna take you a lot of time to figure out unless you've done it a lot.
People are looking at the wrong things. Loading Javascript is nothing compared to downloading it on a mobile connection, and for wired connections you usually have a faster CPU to load the JS.
Modern websites don't move slow because the React site is too big, they move slow because we are throwing a ton of tracking, realtime updates over sockets, large media content, etc to mobile devices over shaky TCP connections which are subject to slow start, head of line blocking, etc. -- nothing is slower than 2G/3G cell connections.
I don't know much about WebGL so gonna skip that. I totally agree that Site don't move slow because of React . That's my main point. I mean like people are not optimizing their sites and throwing 1.5 MB jpg file on the Portfolio main page which obviously gonna kill the performance and bandwidth. Rather optimizing things , they like bashing React because It has bigger bundle size than other frameworks(vue or svelte) and big code length which is a total misunderstanding. I'm not saying React is best for every project but can provide a good functionality overall if used properly. Thank u for the comment ! Much Appreciated!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
React is a great tool, but it isn't appropriate for a lot of projects.
For example, how do you bind a WebGL game engine to React UI state without duplicating your engine code into Redux or wrapping everything with observables, like with mobX?
Webpack can't build a proper ES6 library (yet), so modulizing React applications is a whole fun thing. Could you toss Webpack for your create-react-app starter, implement Rollup with Babel and make an ES6 library to work with the rest of your front end code? Yeah, but that's gonna take you a lot of time to figure out unless you've done it a lot.
People are looking at the wrong things. Loading Javascript is nothing compared to downloading it on a mobile connection, and for wired connections you usually have a faster CPU to load the JS.
Modern websites don't move slow because the React site is too big, they move slow because we are throwing a ton of tracking, realtime updates over sockets, large media content, etc to mobile devices over shaky TCP connections which are subject to slow start, head of line blocking, etc. -- nothing is slower than 2G/3G cell connections.
I don't know much about WebGL so gonna skip that. I totally agree that Site don't move slow because of React . That's my main point. I mean like people are not optimizing their sites and throwing 1.5 MB jpg file on the Portfolio main page which obviously gonna kill the performance and bandwidth. Rather optimizing things , they like bashing React because It has bigger bundle size than other frameworks(vue or svelte) and big code length which is a total misunderstanding. I'm not saying React is best for every project but can provide a good functionality overall if used properly. Thank u for the comment ! Much Appreciated!