Pros of tqdm

Pros of React

• 834

  Components
• 673

  Virtual dom
• 578

  Performance
• 508

  Simplicity
• 442

  Composable
• 186

  Data flow
• 166

  Declarative
• 128

  Isn't an mvc framework
• 120

  Reactive updates
• 115

  Explicit app state
• 50

  JSX
• 29

  Learn once, write everywhere
• 22

  Easy to Use
• 21

  Uni-directional data flow
• 17

  Works great with Flux Architecture
• 11

  Great perfomance
• 10

  Javascript
• 9

  Built by Facebook
• 8

  TypeScript support
• 6

  Speed
• 6

  Server Side Rendering
• 6

  Scalable
• 5

  Props
• 5

  Excellent Documentation
• 5

  Functional
• 5

  Easy as Lego
• 5

  Closer to standard JavaScript and HTML than others
• 5

  Cross-platform
• 5

  Feels like the 90s
• 5

  Easy to start
• 5

  Hooks
• 5

  Awesome
• 4

  Scales super well
• 4

  Allows creating single page applications
• 4

  Server side views
• 4

  Sdfsdfsdf
• 4

  Start simple
• 4

  Strong Community
• 4

  Fancy third party tools
• 4

  Super easy
• 3

  Has arrow functions
• 3

  Very gentle learning curve
• 3

  Beautiful and Neat Component Management
• 3

  Just the View of MVC
• 3

  Simple, easy to reason about and makes you productive
• 3

  Fast evolving
• 3

  SSR
• 3

  Great migration pathway for older systems
• 3

  Rich ecosystem
• 3

  Simple
• 3

  Has functional components
• 3

  Every decision architecture wise makes sense
• 2

  HTML-like
• 2

  Image upload
• 2

  Sharable
• 2

  Recharts
• 2

  Split your UI into components with one true state
• 2

  Permissively-licensed
• 2

  Fragments
• 1

  Datatables
• 1

  React hooks

Cons of tqdm

Cons of React

• 41

  Requires discipline to keep architecture organized
• 30

  No predefined way to structure your app
• 29

  Need to be familiar with lots of third party packages
• 13

  JSX
• 10

  Not enterprise friendly
• 6

  One-way binding only
• 3

  State consistency with backend neglected
• 3

  Bad Documentation
• 2

  Error boundary is needed
• 2

  Paradigms change too fast