Alternatives to Handlebars.js logo

Alternatives to Handlebars.js

AngularJS, Mustache, React, Underscore, and doT.js are the most popular alternatives and competitors to Handlebars.js.
7.9K
308

What is Handlebars.js and what are its top alternatives?

Handlebars.js is a popular templating engine that allows users to create semantic templates using JavaScript. Key features of Handlebars.js include easy syntax for writing templates, logic-less templates, partials support for reusability, and helpers to extend template functionality. However, some limitations of Handlebars.js include limited support for complex logic and lack of built-in support for template inheritance.

  1. Mustache: Mustache is a logic-less templating engine that focuses on simplicity and ease of use. It supports various programming languages, making it versatile. Pros include its clean and simple syntax, while cons include its limited support for complex logic.
  2. Pug: Formerly known as Jade, Pug is a feature-rich template engine for Node.js and browsers. It offers concise and expressive syntax with features like mixins and includes. Pros include its robust functionality, but cons include a learning curve for beginners.
  3. EJS: EJS is an embedded JavaScript templating engine that allows for dynamic content rendering. It offers straightforward syntax and supports both server-side and client-side rendering. Pros include its simplicity, but cons include potential security risks with code injection.
  4. Nunjucks: Nunjucks is a powerful templating engine with features like inheritance, macros, and asynchronous support. It offers a syntax similar to Jinja2 and Django templates. Pros include its rich feature set, while cons include a slightly steeper learning curve.
  5. Twig: Twig is a flexible and secure template engine for PHP applications. It enforces separation of concerns and offers features like template inheritance and automatic escaping. Pros include its robust security features, but cons include performance overhead compared to simpler engines.
  6. Underscore.js: Underscore.js is a JavaScript library that includes a templating engine. It provides a minimalistic approach to templating with features like forEach loops and conditional statements. Pros include its lightweight nature, while cons include limited features compared to dedicated templating engines.
  7. EJS-Mate: EJS-Mate is an extension for EJS that adds layout and block support, enhancing template inheritance capabilities. It provides a cleaner way to manage reusable layouts and sections within templates. Pros include improved template organization, but cons include potential compatibility issues with existing EJS projects.
  8. React.js: React.js is a popular JavaScript library for building user interfaces that offers JSX, a syntax extension for writing HTML within JavaScript. It provides a component-based approach to UI development with easy data binding. Pros include its declarative nature, but cons include a different paradigm compared to traditional templating engines.
  9. Vue.js: Vue.js is a progressive JavaScript framework for building interactive web interfaces. It offers a flexible and intuitive syntax for templating with features like directives and components. Pros include its simplicity and performance, but cons include scalability challenges for complex applications.
  10. Blade: Blade is the templating engine used in the Laravel PHP framework, offering a mix of PHP and HTML syntax. It provides features like template inheritance, components, and conditional statements. Pros include seamless integration with Laravel, but cons include tying template logic to PHP code.

Top Alternatives to Handlebars.js

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

  • Mustache
    Mustache

    Mustache is a logic-less template syntax. It can be used for HTML, config files, source code - anything. It works by expanding tags in a template using values provided in a hash or object. We call it "logic-less" because there are no if statements, else clauses, or for loops. Instead there are only tags. Some tags are replaced with a value, some nothing, and others a series of values. ...

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

  • Underscore
    Underscore

    A JavaScript library that provides a whole mess of useful functional programming helpers without extending any built-in objects. ...

  • doT.js
    doT.js

    It is a fastest and concise javascript template engine for Node.js and browsers. It was created in search of the fastest and concise JavaScript templating function with emphasis on performance under V8 and Node.js. It shows great performance for both Node.js and browsers. ...

  • Vue.js
    Vue.js

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

  • Nunjucks
    Nunjucks

    Rich Powerful language with block inheritance, autoescaping, macros, asynchronous control, and more. Heavily inspired by jinja2. It supports all modern browsers. ...

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

Handlebars.js alternatives & related posts

AngularJS logo

AngularJS

60.9K
43.9K
5.3K
Superheroic JavaScript MVW Framework
60.9K
43.9K
+ 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 · 5M 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 · | 24 upvotes · 4.9M 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
Mustache logo

Mustache

2K
415
50
Logic-less templates
2K
415
+ 1
50
PROS OF MUSTACHE
  • 29
    Dead simple templating
  • 12
    Open source
  • 8
    Small
  • 1
    Support in lots of languages
CONS OF MUSTACHE
    Be the first to leave a con

    related Mustache posts

    React logo

    React

    172.6K
    142.5K
    4.1K
    A JavaScript library for building user interfaces
    172.6K
    142.5K
    + 1
    4.1K
    PROS OF REACT
    • 832
      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
      Server Side Rendering
    • 6
      Speed
    • 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
      Image upload
    • 2
      Permissively-licensed
    • 2
      Fragments
    • 2
      Sharable
    • 2
      Recharts
    • 2
      HTML-like
    • 1
      React hooks
    • 1
      Datatables
    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

    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
    Collins Ogbuzuru
    Front-end dev at Evolve credit · | 37 upvotes · 238.4K views

    Your tech stack is solid for building a real-time messaging project.

    React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

    ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

    Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

    I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

    See more
    Underscore logo

    Underscore

    1.8K
    589
    290
    JavaScript's utility _ belt
    1.8K
    589
    + 1
    290
    PROS OF UNDERSCORE
    • 85
      Utility
    • 55
      Simple
    • 40
      Functional programming
    • 32
      Fast
    • 28
      Open source
    • 20
      Backbone
    • 16
      Javascript
    • 8
      Annotated source code
    • 6
      Library
    CONS OF UNDERSCORE
      Be the first to leave a con

      related Underscore posts

      doT.js logo

      doT.js

      6
      19
      0
      A JavaScript template engine for Node.js
      6
      19
      + 1
      0
      PROS OF DOT.JS
        Be the first to leave a pro
        CONS OF DOT.JS
          Be the first to leave a con

          related doT.js posts

          Vue.js logo

          Vue.js

          54.2K
          44K
          1.6K
          A progressive framework for building user interfaces
          54.2K
          44K
          + 1
          1.6K
          PROS OF VUE.JS
          • 294
            Simple and easy to start with
          • 230
            Good documentation
          • 196
            Components
          • 131
            Simple the best
          • 100
            Simplified AngularJS
          • 95
            Reactive
          • 78
            Intuitive APIs
          • 56
            Javascript
          • 52
            Changed my front end coding life
          • 48
            Configuration is smooth
          • 38
            Easy to learn
          • 36
            So much fun to use
          • 26
            Progressive
          • 22
            Virtual dom
          • 16
            Faster than bulldogs on hot tarmac
          • 12
            It's magic
          • 12
            Component is template, javascript and style in one
          • 10
            Light Weight
          • 10
            Perfomance
          • 9
            Best of Both Worlds
          • 8
            Application structure
          • 8
            Elegant design
          • 8
            Intuitive and easy to use
          • 8
            Without misleading licenses
          • 6
            Small learning curve
          • 6
            Good command line interface
          • 5
            Logicless templates
          • 5
            Single file components
          • 5
            Easy to integrate to HTML by inline-templates
          • 5
            Like Angular only quicker to get started with
          • 4
            High performance
          • 3
            Component based
          • 3
            Vuex
          • 3
            Bridge from Web Development to JS Development
          • 3
            Customer Render ending eg to HTML
          • 2
            Lots of documentation
          • 2
            Concise error messages
          • 2
            Supports several template languages
          • 2
            One-way data flow
          • 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 · 5M 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
          Nunjucks logo

          Nunjucks

          79
          89
          6
          A templating language for JavaScript
          79
          89
          + 1
          6
          PROS OF NUNJUCKS
          • 4
            Supported by Mozilla
          • 2
            Easy sintaxis like JS
          CONS OF NUNJUCKS
            Be the first to leave a con

            related Nunjucks posts

            JavaScript logo

            JavaScript

            359.7K
            273.5K
            8.1K
            Lightweight, interpreted, object-oriented language with first-class functions
            359.7K
            273.5K
            + 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
            • 898
              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
            • 0
              HORRIBLE DOCUMENTS, faulty code, repo has bugs

            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 · 12.6M 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