Alternatives to Angular logo

Alternatives to Angular

React, Polymer, Aurelia, Vue.js, and Meteor are the most popular alternatives and competitors to Angular.
1.7K
4.7K
+ 1
499

What is Angular and what are its top alternatives?

Angular is a popular open-source web application framework maintained by Google that allows developers to build dynamic single-page applications. Its key features include two-way data binding, routing, dependency injection, and the use of TypeScript for development. However, Angular has a steep learning curve and can be complex for beginners.

  1. React: React is a JavaScript library maintained by Facebook for building user interfaces. It is known for its component-based architecture, virtual DOM, and one-way data flow. Compared to Angular, React offers better performance and a more flexible approach to building applications.

  2. Vue.js: Vue.js is a progressive JavaScript framework that is easy to integrate into existing projects. It provides a simple and intuitive API, a virtual DOM, and reactivity features. Compared to Angular, Vue.js is lighter, has a simpler syntax, and allows for quicker development.

  3. Svelte: Svelte is a relatively new framework that compiles your components into highly efficient vanilla JavaScript at build time. It eliminates the need for a virtual DOM and offers better performance compared to Angular. Svelte's simple syntax and ease of use make it a popular choice for building web applications.

  4. Ember.js: Ember.js is a fully-featured JavaScript framework with a strong emphasis on convention over configuration. It includes features like Ember CLI, data layer with Ember Data, and a component-based architecture. Compared to Angular, Ember.js provides a more opinionated structure for building applications.

  5. Backbone.js: Backbone.js is a lightweight JavaScript library that provides the minimal structure needed for building web applications. It offers models, collections, and views for organizing data and user interfaces. Compared to Angular, Backbone.js is more minimalistic and suitable for smaller projects.

  6. Aurelia: Aurelia is a modern JavaScript framework that follows a modular and unobtrusive approach to building web applications. It provides a powerful data-binding system, dependency injection, and a simple API. Compared to Angular, Aurelia offers a more intuitive and flexible development experience.

  7. Meteor: Meteor is a full-stack JavaScript platform for building real-time web and mobile applications. It includes features like reactivity, data synchronization, and a built-in package system. Compared to Angular, Meteor simplifies the development process by providing everything needed to build and deploy applications.

  8. Polymer: Polymer is a JavaScript library for building web components to create reusable and encapsulated elements. It provides a declarative syntax, two-way data binding, and a set of pre-built elements. Compared to Angular, Polymer focuses on building custom elements and is suited for component-based development.

  9. Mithril: Mithril is a modern client-side JavaScript framework for building single-page applications. It is lightweight, fast, and efficient, with a simple API and minimal dependencies. Compared to Angular, Mithril offers a smaller footprint and better performance for applications with complex UI interactions.

  10. Sapper: Sapper is a framework for building server-rendered web applications using Svelte. It provides features like server-side rendering, routing, and code splitting for optimizing performance. Compared to Angular, Sapper offers a simpler approach to building universal applications with built-in features for server-side rendering.

Top Alternatives to Angular

  • 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. ...

  • Polymer
    Polymer

    Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds. ...

  • Aurelia
    Aurelia

    Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity. ...

  • Vue.js
    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • Meteor
    Meteor

    A Meteor application is a mix of JavaScript that runs inside a client web browser, JavaScript that runs on the Meteor server inside a Node.js container, and all the supporting HTML fragments, CSS rules, and static assets. ...

  • Knockout
    Knockout

    It is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), it can help you implement it more simply and maintainably. ...

  • 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. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

Angular alternatives & related posts

React logo

React

169K
139.7K
4.1K
A JavaScript library for building user interfaces
169K
139.7K
+ 1
4.1K
PROS OF REACT
  • 830
    Components
  • 672
    Virtual dom
  • 578
    Performance
  • 507
    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
  • 5
    Feels like the 90s
  • 5
    Excellent Documentation
  • 5
    Props
  • 5
    Functional
  • 5
    Easy as Lego
  • 5
    Closer to standard JavaScript and HTML than others
  • 5
    Cross-platform
  • 5
    Easy to start
  • 5
    Hooks
  • 5
    Awesome
  • 5
    Scalable
  • 4
    Super easy
  • 4
    Allows creating single page applications
  • 4
    Server side views
  • 4
    Sdfsdfsdf
  • 4
    Start simple
  • 4
    Strong Community
  • 4
    Fancy third party tools
  • 4
    Scales super well
  • 3
    Has arrow functions
  • 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
  • 3
    Very gentle learning curve
  • 2
    Split your UI into components with one true state
  • 2
    Recharts
  • 2
    Permissively-licensed
  • 2
    Fragments
  • 2
    Sharable
  • 2
    Image upload
  • 2
    HTML-like
  • 1
    React hooks
  • 1
    Datatables
CONS OF REACT
  • 40
    Requires discipline to keep architecture organized
  • 29
    No predefined way to structure your app
  • 28
    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

related React posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Zach Holman

Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

See more
Polymer logo

Polymer

553
461
122
A new library built on top of Web Components, designed to leverage the evolving web platform on modern...
553
461
+ 1
122
PROS OF POLYMER
  • 52
    Web components
  • 30
    Material design
  • 14
    HTML
  • 13
    Components
  • 5
    Open source
  • 4
    It uses the platform
  • 3
    Designer friendly. HTMLX concepts
  • 1
    Like the interesting naming convention for elements
CONS OF POLYMER
  • 1
    Last version is like 2 years ago? that's totally rad

related Polymer posts

Adam Rabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 6 upvotes · 123.2K views

At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

See more
Ido Shamun
at The Elegant Monkeys · | 6 upvotes · 89.8K views
Shared insights
on
Vue.jsVue.jsReactReactPolymerPolymer
at

For developing our #frontend applications, we decided to use Vue.js . Being such an easy to learn library, compared to React for example, it made everything so easy. At first we started with Polymer but the existing tooling and small community at the time made us look for alternatives.

See more
Aurelia logo

Aurelia

277
294
374
Next gen JS framework written with ES6 and ES7. Integrates with Web Components. No external dependencies except polyfills.
277
294
+ 1
374
PROS OF AURELIA
  • 47
    Simple with conventions
  • 42
    Modern architecture
  • 39
    Makes sense and is mostly javascript not framework
  • 31
    Extensible
  • 28
    Integrates well with other components
  • 27
    Easy to use
  • 25
    Dependency Injection
  • 22
    Modular
  • 20
    Great router
  • 16
    Adaptive Data Binding
  • 13
    Typescript, ES2015, ES2016
  • 11
    IoC, Modularity, Simplicity, Full Stack
  • 9
    Good binding system
  • 9
    Based on ES7
  • 6
    Testable
  • 6
    Convention based
  • 5
    Quick to develop
  • 4
    Solid Documentation
  • 4
    Evolving standards compliance
  • 4
    Smooth learning curve
  • 4
    Outstanding Support (paid)
  • 1
    Reactive binding system
  • 1
    TypeScript
CONS OF AURELIA
    Be the first to leave a con

    related Aurelia posts

    Adam Rabinovitch
    Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 6 upvotes · 123.2K views

    At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

    As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

    So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

    See more

    This is a stack i would use for my next project.

    backend Spring-Boot GraphQL

    #frontend Aurelia

    deploy Docker
    See more
    Vue.js logo

    Vue.js

    53.4K
    43.4K
    1.6K
    A progressive framework for building user interfaces
    53.4K
    43.4K
    + 1
    1.6K
    PROS OF VUE.JS
    • 293
      Simple and easy to start with
    • 229
      Good documentation
    • 196
      Components
    • 131
      Simple the best
    • 100
      Simplified AngularJS
    • 94
      Reactive
    • 77
      Intuitive APIs
    • 56
      Javascript
    • 52
      Changed my front end coding life
    • 48
      Configuration is smooth
    • 37
      Easy to learn
    • 35
      So much fun to use
    • 25
      Progressive
    • 22
      Virtual dom
    • 16
      Faster than bulldogs on hot tarmac
    • 12
      Component is template, javascript and style in one
    • 12
      It's magic
    • 10
      Perfomance
    • 10
      Light Weight
    • 9
      Best of Both Worlds
    • 8
      Intuitive and easy to use
    • 8
      Elegant design
    • 8
      Application structure
    • 8
      Without misleading licenses
    • 6
      Small learning curve
    • 6
      Good command line interface
    • 5
      Logicless templates
    • 5
      Like Angular only quicker to get started with
    • 5
      Single file components
    • 5
      Easy to integrate to HTML by inline-templates
    • 4
      High performance
    • 3
      Vuex
    • 3
      Component based
    • 3
      Customer Render ending eg to HTML
    • 3
      Bridge from Web Development to JS Development
    • 2
      Concise error messages
    • 2
      Supports several template languages
    • 2
      One-way data flow
    • 2
      Lots of documentation
    • 2
      Intuitive
    • 1
      GUI
    CONS OF VUE.JS
    • 9
      Less Common Place
    • 5
      YXMLvsHTML Markup
    • 3
      Don't support fragments
    • 3
      Only support programatically multiple root nodes

    related Vue.js posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M 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
    Johnny Bell
    Shared insights
    on
    Vue.jsVue.jsReactReact

    I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

    It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

    See more
    Meteor logo

    Meteor

    1.9K
    1.8K
    1.7K
    An ultra-simple, database-everywhere, data-on-the-wire, pure-Javascript web framework
    1.9K
    1.8K
    + 1
    1.7K
    PROS OF METEOR
    • 252
      Real-time
    • 200
      Full stack, one language
    • 183
      Best app dev platform available today
    • 155
      Data synchronization
    • 152
      Javascript
    • 118
      Focus on your product not the plumbing
    • 107
      Hot code pushes
    • 106
      Open source
    • 102
      Live page updates
    • 92
      Latency compensation
    • 39
      Ultra-simple development environment
    • 29
      Real time awesome
    • 29
      Smart Packages
    • 23
      Great for beginners
    • 22
      Direct Cordova integration
    • 16
      Better than Rails
    • 15
      Less moving parts
    • 13
      It's just amazing
    • 10
      Blaze
    • 8
      Great community support
    • 8
      Plugins for everything
    • 6
      One command spits out android and ios ready apps.
    • 5
      It just works
    • 5
      0 to Production in no time
    • 4
      Coding Speed
    • 4
      Easy deployment
    • 4
      Is Agile in development hybrid(mobile/web)
    • 4
      You can grok it in a day. No ng nonsense
    • 2
      Easy yet powerful
    • 2
      AngularJS Integration
    • 2
      One Code => 3 Platforms: Web, Android and IOS
    • 2
      Community
    • 1
      Easy Setup
    • 1
      Free
    • 1
      Nosql
    • 1
      Hookie friendly
    • 1
      High quality, very few bugs
    • 1
      Stack available on Codeanywhere
    • 1
      Real time
    • 1
      Friendly to use
    CONS OF METEOR
    • 5
      Does not scale well
    • 4
      Hard to debug issues on the server-side
    • 4
      Heavily CPU bound

    related Meteor posts

    Lucas Litton
    Founder & CEO at Macombey · | 13 upvotes · 548.9K views

    Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

    See more
    Shared insights
    on
    MeteorMeteorNode.jsNode.js
    at

    Mixmax was originally built using Meteor as a single monolithic app. As more users began to onboard, we started noticing scaling issues, and so we broke out our first microservice: our Compose service, for writing emails and Sequences, was born as a Node.js service. Soon after that, we broke out all recipient searching and storage functionality to another Node.js microservice, our Contacts service. This practice of breaking out microservices in order to help our system more appropriately scale, by being more explicit about each microservice’s responsibilities, continued as we broke out numerous more microservices.

    See more
    Knockout logo

    Knockout

    251
    200
    6
    Create rich, responsive UIs with JavaScript
    251
    200
    + 1
    6
    PROS OF KNOCKOUT
    • 3
      Data centered application
    • 2
      Great for validations
    • 1
      Open source
    CONS OF KNOCKOUT
      Be the first to leave a con

      related Knockout posts

      AngularJS logo

      AngularJS

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

      related AngularJS posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M 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 · | 23 upvotes · 4.8M 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
      JavaScript logo

      JavaScript

      351.2K
      267.4K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      351.2K
      267.4K
      + 1
      8.1K
      PROS OF JAVASCRIPT
      • 1.7K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.2K
        Lots of great frameworks
      • 897
        Fast
      • 745
        Light weight
      • 425
        Flexible
      • 392
        You can't get a device today that doesn't run js
      • 286
        Non-blocking i/o
      • 237
        Ubiquitousness
      • 191
        Expressive
      • 55
        Extended functionality to web pages
      • 49
        Relatively easy language
      • 46
        Executed on the client side
      • 30
        Relatively fast to the end user
      • 25
        Pure Javascript
      • 21
        Functional programming
      • 15
        Async
      • 13
        Full-stack
      • 12
        Setup is easy
      • 12
        Future Language of The Web
      • 12
        Its everywhere
      • 11
        Because I love functions
      • 11
        JavaScript is the New PHP
      • 10
        Like it or not, JS is part of the web standard
      • 9
        Expansive community
      • 9
        Everyone use it
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 8
        Most Popular Language in the World
      • 8
        Powerful
      • 8
        Can be used both as frontend and backend as well
      • 8
        For the good parts
      • 8
        No need to use PHP
      • 8
        Easy to hire developers
      • 7
        Agile, packages simple to use
      • 7
        Love-hate relationship
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        Evolution of C
      • 7
        It's fun
      • 7
        Hard not to use
      • 7
        Versitile
      • 7
        Its fun and fast
      • 7
        Nice
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        Supports lambdas and closures
      • 6
        It let's me use Babel & Typescript
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 6
        1.6K Can be used on frontend/backend
      • 6
        Client side JS uses the visitors CPU to save Server Res
      • 6
        Easy to make something
      • 5
        Clojurescript
      • 5
        Promise relationship
      • 5
        Stockholm Syndrome
      • 5
        Function expressions are useful for callbacks
      • 5
        Scope manipulation
      • 5
        Everywhere
      • 5
        Client processing
      • 5
        What to add
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Test
      • 1
        Hard to learn
      • 1
        Test2
      • 1
        Not the best
      • 1
        Easy to understand
      • 1
        Subskill #4
      • 1
        Easy to learn
      • 0
        Hard 彤
      CONS OF JAVASCRIPT
      • 22
        A constant moving target, too much churn
      • 20
        Horribly inconsistent
      • 15
        Javascript is the New PHP
      • 9
        No ability to monitor memory utilitization
      • 8
        Shows Zero output in case of ANY error
      • 7
        Thinks strange results are better than errors
      • 6
        Can be ugly
      • 3
        No GitHub
      • 2
        Slow

      related JavaScript posts

      Zach Holman

      Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

      But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

      But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

      Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

      See more
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more