Alternatives to Semantic UI React logo

Alternatives to Semantic UI React

Material-UI, Semantic UI, Ant Design, Bootstrap, and reactstrap are the most popular alternatives and competitors to Semantic UI React.
217
358
+ 1
28

What is Semantic UI React and what are its top alternatives?

Semantic UI React is the official React integration for Semantic UI. jQuery Free, Declarative API, Shorthand Props, and more.
Semantic UI React is a tool in the Javascript UI Libraries category of a tech stack.
Semantic UI React is an open source tool with 12.9K GitHub stars and 4K GitHub forks. Here’s a link to Semantic UI React's open source repository on GitHub

Top Alternatives to Semantic UI React

  • Material-UI
    Material-UI

    Material UI is a library of React UI components that implements Google's Material Design. ...

  • Semantic UI
    Semantic UI

    Semantic empowers designers and developers by creating a shared vocabulary for UI. ...

  • Ant Design
    Ant Design

    An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...

  • Bootstrap
    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • reactstrap
    reactstrap

    It provides prebuilt Bootstrap 4 components that allow a great deal of flexibility and prebuilt validation. This allows us to quickly build beautiful forms that are guaranteed to impress and provide an intuitive user experience. ...

  • jQuery
    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

Semantic UI React alternatives & related posts

Material-UI logo

Material-UI

2K
3.3K
402
Material UI is a library of React UI components that implements Google's Material Design.
2K
3.3K
+ 1
402
PROS OF MATERIAL-UI
  • 131
    React
  • 80
    Material Design
  • 56
    Ui components
  • 26
    CSS framework
  • 22
    Component
  • 13
    Looks great
  • 10
    Good documentation
  • 10
    Responsive
  • 9
    LESS
  • 7
    Open source
  • 6
    Ui component
  • 6
    Code examples
  • 5
    Flexible
  • 4
    JSS
  • 3
    Supports old browsers out of the box
  • 3
    Angular
  • 3
    Fun
  • 3
    Very accessible
  • 2
    Interface
  • 2
    Designed for Server Side Rendering
  • 1
    Easy to work with
CONS OF MATERIAL-UI
  • 30
    Hard to learn. Bad documentation
  • 25
    Hard to customize
  • 19
    Hard to understand Docs
  • 6
    Extra library needed for date/time pickers
  • 6
    Bad performance
  • 5
    For editable table component need to use material-table

related Material-UI posts

Adebayo Akinlaja
Engineering Manager at Andela · | 28 upvotes · 1.4M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more

My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?

See more
Semantic UI logo

Semantic UI

885
1.5K
673
A UI Component library implemented using a set of specifications designed around natural language
885
1.5K
+ 1
673
PROS OF SEMANTIC UI
  • 157
    Easy to use and looks elegant
  • 92
    Variety of components
  • 64
    Themes
  • 61
    Has out-of-the-box widgets i would actually use
  • 57
    Semantic, duh
  • 44
    Its the future
  • 42
    Open source
  • 37
    Very active development
  • 31
    Far less complicated structure
  • 28
    Gulp
  • 9
    Already has more features than bootstrap
  • 8
    Just compare it to Bootstrap and you'll be hooked
  • 7
    UI components
  • 7
    Clean and consistent markup model
  • 6
    Responsiveness
  • 4
    Elegant. clean. readable. maintainable
  • 4
    Because it is semantic :-D
  • 4
    Good-Looking
  • 2
    Great docs
  • 2
    Consistent
  • 2
    Is big and look really great, nothing like this
  • 2
    Modular and scalable
  • 1
    Jquery
  • 1
    Easy to use
  • 1
    Blends with reactjs
CONS OF SEMANTIC UI
  • 5
    Outdated build tool (gulp 3))
  • 3
    Poor accessibility support
  • 3
    HTML is not semantic (see list component)
  • 2
    Javascript is tied to jquery

related Semantic UI posts

ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

See more
Hassan Mugabo
Software Developer at Codeparl Digital Services · | 3 upvotes · 5.5K views

Hi, I'm using Tailwind CSS for my project but I found Bootstrap and Semantic UI offering pre-built components like Model, Sidebars, and so forth. Is it possible to use Semantic UI or Bootstrap under Tailwind CSS?

See more
Ant Design logo

Ant Design

944
1.5K
219
A set of high-quality React components
944
1.5K
+ 1
219
PROS OF ANT DESIGN
  • 45
    Lots of components
  • 34
    Polished and enterprisey look and feel
  • 21
    TypeScript
  • 20
    Easy to integrate
  • 18
    Es6 support
  • 17
    Typescript support
  • 17
    Beautiful and solid
  • 16
    Beautifully Animated Components
  • 15
    Quick Release rhythm
  • 14
    Great documentation
  • 2
    Easy to customize Forms
CONS OF ANT DESIGN
  • 20
    Less
  • 9
    Large File Size
  • 4
    Poor accessibility support
  • 1
    Dangerous to use as a base in component libraries

related Ant Design posts

Sarmad Chaudhary
Founder & CEO at Ebiz Ltd. · | 9 upvotes · 606.8K views

Hi there!

I just want to have a simple poll/vote...

If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

Your advice would help a lot! Thanks in advance :)

See more
Shared insights
on
Material-UIMaterial-UIAnt DesignAnt Design

Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.

Here is a list of my requirements.

  1. Good documentation.
  2. easy CRUD ( date picker and date range picker bundled )
  3. built-in multi-lang feature or Great 3rd library support
  4. Admin dashboard template
  5. well code maintenance

Which is better for the long run?

See more
Bootstrap logo

Bootstrap

54.5K
12.5K
7.7K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
54.5K
12.5K
+ 1
7.7K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 944
    Consistent
  • 779
    Great docs
  • 678
    Flexible
  • 472
    HTML, CSS, and JS framework
  • 411
    Open source
  • 374
    Widely used
  • 367
    Customizable
  • 242
    HTML framework
  • 77
    Mobile first
  • 77
    Popular
  • 77
    Easy setup
  • 58
    Great grid system
  • 52
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 28
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 14
    Grids
  • 8
    Good for a person who hates CSS
  • 8
    Clean
  • 4
    Rapid development
  • 4
    Love it
  • 4
    Easy to setup and learn
  • 3
    Great and easy to use
  • 2
    Clean and quick frontend development
  • 2
    Boostrap
  • 2
    Community
  • 2
    Provide angular wrapper
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Easy to use
  • 1
    Geo
  • 1
    Not tied to jQuery
  • 1
    Design Agnostic
  • 1
    So clean and simple
  • 1
    Numerous components
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    Material-ui
  • 1
    Felxible, comfortable, user-friendly
  • 1
    Pre-Defined components
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Painless front end development
  • 1
    It's fast
  • 1
    Responsive design
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 15
    Grid system break points aren't ideal
  • 14
    Too much heavy decoration in default look
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 3.1M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 983.5K views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
reactstrap logo

reactstrap

152
155
3
Easy to use React Bootstrap 4 components compatible with React
152
155
+ 1
3
PROS OF REACTSTRAP
  • 3
    Prebuilt Bootstrap 4 components
CONS OF REACTSTRAP
    Be the first to leave a con

    related reactstrap posts

    My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?

    See more
    Shared insights
    on
    Material-UIMaterial-UIreactstrapreactstrap

    I need to create a footer. Can I use reactstrap and Material-UI, or is it one or the other? If it's only one, what is the best way to create a footer with MaterialUI?

    See more
    jQuery logo

    jQuery

    179.1K
    58.1K
    6.6K
    The Write Less, Do More, JavaScript Library.
    179.1K
    58.1K
    + 1
    6.6K
    PROS OF JQUERY
    • 1.3K
      Cross-browser
    • 957
      Dom manipulation
    • 807
      Power
    • 660
      Open source
    • 610
      Plugins
    • 458
      Easy
    • 395
      Popular
    • 350
      Feature-rich
    • 281
      Html5
    • 227
      Light weight
    • 92
      Simple
    • 84
      Great community
    • 79
      CSS3 Compliant
    • 69
      Mobile friendly
    • 67
      Fast
    • 43
      Intuitive
    • 42
      Swiss Army knife for webdev
    • 35
      Huge Community
    • 11
      Easy to learn
    • 4
      Clean code
    • 3
      Because of Ajax request :)
    • 2
      Just awesome
    • 2
      Used everywhere
    • 2
      Powerful
    • 2
      Nice
    • 1
      Widely Used
    • 1
      Improves productivity
    • 1
      Open Source, Simple, Easy Setup
    • 1
      It Just Works
    • 1
      Industry acceptance
    • 1
      Allows great manipulation of HTML and CSS
    • 1
      Javascript
    • 1
      Easy Setup
    CONS OF JQUERY
    • 6
      Large size
    • 5
      Sometimes inconsistent API
    • 5
      Encourages DOM as primary data source
    • 2
      Live events is overly complex feature

    related jQuery posts

    Kir Shatrov
    Engineering Lead at Shopify · | 21 upvotes · 823K views

    The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

    Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

    #FrameworksFullStack #Languages

    See more
    Ganesa Vijayakumar
    Full Stack Coder | Technical Lead · | 19 upvotes · 3.1M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    React logo

    React

    139.2K
    114.4K
    3.9K
    A JavaScript library for building user interfaces
    139.2K
    114.4K
    + 1
    3.9K
    PROS OF REACT
    • 787
      Components
    • 661
      Virtual dom
    • 570
      Performance
    • 497
      Simplicity
    • 440
      Composable
    • 178
      Data flow
    • 164
      Declarative
    • 125
      Isn't an mvc framework
    • 115
      Reactive updates
    • 113
      Explicit app state
    • 42
      JSX
    • 26
      Learn once, write everywhere
    • 20
      Uni-directional data flow
    • 19
      Easy to Use
    • 15
      Works great with Flux Architecture
    • 11
      Great perfomance
    • 9
      Javascript
    • 9
      Built by Facebook
    • 6
      Speed
    • 6
      TypeScript support
    • 5
      Easy to start
    • 5
      Cross-platform
    • 5
      Server Side Rendering
    • 5
      Scalable
    • 5
      Awesome
    • 5
      Hooks
    • 5
      Feels like the 90s
    • 4
      Scales super well
    • 4
      Functional
    • 4
      Server side views
    • 4
      Fancy third party tools
    • 4
      Excellent Documentation
    • 4
      Props
    • 4
      Closer to standard JavaScript and HTML than others
    • 3
      Rich ecosystem
    • 3
      Great migration pathway for older systems
    • 3
      Super easy
    • 3
      Simple
    • 3
      Has functional components
    • 3
      Allows creating single page applications
    • 3
      SSR
    • 3
      Fast evolving
    • 3
      Simple, easy to reason about and makes you productive
    • 3
      Just the View of MVC
    • 3
      Beautiful and Neat Component Management
    • 3
      Sdfsdfsdf
    • 3
      Very gentle learning curve
    • 3
      Start simple
    • 3
      Has arrow functions
    • 3
      Strong Community
    • 2
      Every decision architecture wise makes sense
    • 2
      Easy as Lego
    • 2
      Split your UI into components with one true state
    • 2
      Sharable
    • 2
      Fragments
    • 2
      Permissively-licensed
    • 1
      Image upload
    • 1
      Recharts
    CONS OF REACT
    • 36
      Requires discipline to keep architecture organized
    • 25
      No predefined way to structure your app
    • 24
      Need to be familiar with lots of third party packages
    • 9
      JSX
    • 7
      Not enterprise friendly
    • 5
      One-way binding only
    • 2
      State consistency with backend neglected
    • 2
      Bad Documentation
    • 1
      Paradigms change too fast

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 2.1M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Adebayo Akinlaja
    Engineering Manager at Andela · | 28 upvotes · 1.4M views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more
    AngularJS logo

    AngularJS

    52.1K
    38.2K
    5.2K
    Superheroic JavaScript MVW Framework
    52.1K
    38.2K
    + 1
    5.2K
    PROS OF ANGULARJS
    • 888
      Quick to develop
    • 588
      Great mvc
    • 572
      Powerful
    • 521
      Restful
    • 503
      Backed by google
    • 349
      Two-way data binding
    • 343
      Javascript
    • 328
      Open source
    • 306
      Dependency injection
    • 197
      Readable
    • 75
      Fast
    • 64
      Directives
    • 63
      Great community
    • 56
      Free
    • 38
      Extend html vocabulary
    • 29
      Components
    • 26
      Easy to test
    • 24
      Easy to learn
    • 23
      Easy to templates
    • 23
      Great documentation
    • 21
      Easy to start
    • 18
      Awesome
    • 17
      Light weight
    • 14
      Javascript mvw framework
    • 14
      Angular 2.0
    • 13
      Great extensions
    • 13
      Efficient
    • 10
      Easy to prototype with
    • 8
      Coffeescript
    • 8
      High performance
    • 7
      Mvc
    • 7
      Two-way binding
    • 7
      Lots of community modules
    • 6
      Clean and keeps code readable
    • 6
      Easy to e2e
    • 5
      One of the best frameworks
    • 5
      Easy for small applications
    • 4
      Fast development
    • 4
      Works great with jquery
    • 3
      I do not touch DOM
    • 2
      The two-way Data Binding is awesome
    • 2
      Typescript
    • 2
      Dart
    • 2
      Community
    • 2
      Hierarchical Data Structure
    • 2
      Be a developer, not a plumber.
    • 2
      Declarative programming
    • 1
      Common Place
    • 1
      Great
    • 1
      Very very useful and fast framework for development
    • 1
      Amazing community support
    • 1
      Readable code
    • 1
      Linear learning curve
    • 1
      Scopes
    • 1
      Programming fun again
    • 1
      The powerful of binding, routing and controlling routes
    • 1
      Consistency with backend architecture if using Nest
    • 1
      Fkin awesome
    • 1
      Opinionated in the right areas
    • 1
      Supports api , easy development
    CONS OF ANGULARJS
    • 10
      Complex
    • 3
      Dependency injection
    • 2
      Learning Curve
    • 2
      Event Listener Overload
    • 1
      Hard to learn

    related AngularJS posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 3M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.5M views

    Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

    • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
    • Vue Styleguidist as our style guide and pool of developed Vue.js components
    • Vuetify as Material Component Framework (for fast app development)
    • TypeScript as programming language
    • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
    • ESLint, TSLint and Prettier for coding style and code analyzes
    • Jest as testing framework
    • Google Fonts and Font Awesome for typography and icon toolkit
    • NativeScript-Vue for mobile development

    The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

    • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
    • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
    • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
    • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
    • Large scaling. Vue.js can help to develop pretty large reusable templates.
    • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
    See more