Need advice about which tool to choose?Ask the StackShare community!
Both React's community and component library are far more robust than that of Vue. Not only that, but more companies seem to use React, so it only makes sense to learn it so that one can maximize their opportunity. I also love the way React forces you to think when designing things as it truly is OOP as its finest.
We choose React for our client-side implementation because of React's virtual DOM implementation and component rendering optimization. It can help our app to be more stable and easier to debug. Also, react has strong support from the dev community. There is an enormous amount of reacting libraries we could use, which will speed up our development process.
As a backend dev, it was quite easy to go with vue over react. Important note that Im now talking about Vue2 maybe the are crucial changes in third version, but the second one is super easy to get into without spending too much time learning concepts. And vue-cli is just a breeze to start a project with.
What a debate to wade into - React vs. Vue.js. Prototyping of applications is much, much faster in Vue.js. React, I believe, has a much heavier developer learning experience - so hiring pure Javascript developers allows us to work in a much more framework agnostic way. However, React still has a place within our application stack - it's much more performant out of the box.
The project is a web gadget previously made using vanilla script and JQuery, It is a part of the "Quicktext" platform and offers an in-app live & customizable messaging widget. We made that remake with React eco-system and Typescript and we're so far happy with results. We gained tons of TS features, React scaling & re-usabilities capabilities and much more!
What do you think?
When I started TipMe, I thought about using React frontend. At the end, plain, simple jQuery won.
I had to build this iteration of the site fast and by using jQuery I could keep using Django as a full stack development tool. One important point is Django form (combined with Django Bootstrap3) means that I don't have to reinvent form rendering again, which will be the case with React.
Over time, more interactivity seeped into the site and React components start making its way into the codebase.
I now wish the site is built using React so that I could add more user friendly interfaces easier (no more fuddling with server states) but I would still say jQuery helped me get past those early days.
Pros of Famous Framework
Pros of jQuery
- Cross-browser1.3K
- Dom manipulation957
- Power807
- Open source660
- Plugins610
- Easy458
- Popular395
- Feature-rich350
- Html5281
- Light weight227
- Simple92
- Great community84
- CSS3 Compliant79
- Mobile friendly69
- Fast67
- Intuitive43
- Swiss Army knife for webdev42
- Huge Community35
- Easy to learn11
- Clean code4
- Because of Ajax request :)3
- Just awesome2
- Used everywhere2
- Powerful2
- Nice2
- Widely Used1
- Improves productivity1
- Open Source, Simple, Easy Setup1
- It Just Works1
- Industry acceptance1
- Allows great manipulation of HTML and CSS1
- Javascript1
- Easy Setup1
Pros of React
- Components777
- Virtual dom660
- Performance569
- Simplicity494
- Composable439
- Data flow177
- Declarative162
- Isn't an mvc framework124
- Reactive updates114
- Explicit app state112
- JSX40
- Learn once, write everywhere25
- Uni-directional data flow19
- Easy to Use18
- Works great with Flux Architecture14
- Great perfomance10
- Built by Facebook8
- Javascript7
- Speed5
- TypeScript support5
- Easy to start4
- Awesome4
- Feels like the 90s4
- Scalable4
- Hooks4
- Props3
- Excellent Documentation3
- Scales super well3
- Cross-platform3
- Server Side Rendering3
- Obama3
- Fancy third party tools3
- Server side views3
- Functional3
- Very gentle learning curve2
- Simple2
- Closer to standard JavaScript and HTML than others2
- Super easy2
- Rich ecosystem2
- Allows creating single page applications2
- Fast evolving2
- Simple, easy to reason about and makes you productive2
- Start simple2
- Just the View of MVC2
- Beautiful and Neat Component Management2
- Sdfsdfsdf2
- Has functional components2
- Has arrow functions2
- Strong Community2
- Great migration pathway for older systems2
- SSR2
- Fragments1
- Every decision architecture wise makes sense1
- Split your UI into components with one true state1
- Sharable1
- Permissively-licensed1
- Image upload0
- Recharts0
Sign up to add or upvote prosMake informed product decisions
Cons of Famous Framework
Cons of jQuery
- Large size6
- Sometimes inconsistent API5
- Encourages DOM as primary data source5
- Live events is overly complex feature2
Cons of React
- Requires discipline to keep architecture organized36
- No predefined way to structure your app24
- Need to be familiar with lots of third party packages23
- JSX9
- Not enterprise friendly7
- One-way binding only5
- Bad Documentation2
- State consistency with backend neglected2
- Not Typescript1
- Paradigms change too fast1