You probably don't need a JavaScript framework
slack-files.com
You probably don't need a JavaScript framework
1–10 of 356 posts
Re: You probably don't need a JavaScript framework
#2I have been avoiding JS for years (not out of hate, just the job) and every time I dabble in the node/js framework ecosystem I end up turning away frustrated.
I have a few small personal projects that I haven't started due to lack of desire in building the front end I want, after reading this I'm going to give them a shot and see how far I can go with out all the goodies!
Re: You probably don't need a JavaScript framework
#3You don't need one, but if you don't eventually adopt one, you'll end up writing one.
Re: You probably don't need a JavaScript framework
#4The cycle continues...
No framework -> Backbone -> Angular -> React -> No framework
We should be back towards using a simple MVC skeleton by the end of 2016.
Re: You probably don't need a JavaScript framework
#5I don't use React for speed. I use it because manipulating the DOM to make it reflect the application state is hard. It's something a program should do for me. React is that program.
Re: You probably don't need a JavaScript framework
#6React doesn't exist to handle the massive amounts of data that facebook has.
React exists to make complex UIs easier to build and maintain.
Being able to just write the code once to render a UI from some state and then just reloading the entire UI when the state changes is an incredible simplification of your code.
That the author kind of misses this point makes me pay less attention to the rest of the post.
Re: You probably don't need a JavaScript framework
#7React doesn't exist to handle the massive amounts of data that facebook has. React exists to make complex UIs easier to build and maintain. Being able to just write the code once to render a UI from some state and then just reloading the entire UI when the state changes is an incredible simplification of your code. That the author kind of misses this point makes me pay less attention to the rest of the post.
"That the author kind of misses this point makes me pay less attention to the rest of the post."
Too bad. The author addressed everything you said. You just didn't read past the sentence you quoted.
Nowhere does the piece imply that you should render every state change server-side. In fact, it goes on to show, with specific examples, of how you can get data-binding and partial-update behavior with web-native APIs. The argument is that most people don't need React, not that they don't need AJAX or data binding.
Re: You probably don't need a JavaScript framework
#8React doesn't exist to handle the massive amounts of data that facebook has. React exists to make complex UIs easier to build and maintain. Being able to just write the code once to render a UI from some state and then just reloading the entire UI when the state changes is an incredible simplification of your code. That the author kind of misses this point makes me pay less attention to the rest of the post.
[deleted]
Re: You probably don't need a JavaScript framework
#9You don't need one, but if you don't eventually adopt one, you'll end up writing one.
Sure, you may well end up writing one, but it's likely to be a fraction of the size. My current entire app is running at half the size of jquery, which is getting me awesomely quick page loads even on poor mobile connections. The dev time was longer, but not crazily longer, and the surface area for testing is somewhat smaller
Re: You probably don't need a JavaScript framework
#10React doesn't exist to handle the massive amounts of data that facebook has. React exists to make complex UIs easier to build and maintain. Being able to just write the code once to render a UI from some state and then just reloading the entire UI when the state changes is an incredible simplification of your code. That the author kind of misses this point makes me pay less attention to the rest of the post.
"That the author kind of misses this point makes me pay less attention to the rest of the post." Too bad. The author addressed everything you said. You just didn't read past the sentence you quoted. Nowhere does the piece imply that you should render every state change server-side. In fact, it goes on to show, with specific examples, of how you can get data-binding and partial-update behavior with web-native APIs. Th…
That doesn't address the fact that, to some of us, React simplifies creating, testing, and maintaining complex UI due to its functional nature. React is simple to me, and that's why I like using it.