Alternatives to Pug logo

Alternatives to Pug

EJS, Handlebars.js, React, TypeScript, and Mustache are the most popular alternatives and competitors to Pug.
1.1K
1.1K
+ 1
430

What is Pug and what are its top alternatives?

This project was formerly known as "Jade." Pug is a high performance template engine heavily influenced by Haml and implemented with JavaScript for Node.js and browsers.
Pug is a tool in the Templating Languages & Extensions category of a tech stack.
Pug is an open source tool with 20.5K GitHub stars and 2K GitHub forks. Here’s a link to Pug's open source repository on GitHub

Top Alternatives to Pug

  • EJS

    EJS

    It is a simple templating language that lets you generate HTML markup with plain JavaScript. No religiousness about how to organize things. No reinvention of iteration and control-flow. It's just plain JavaScript. ...

  • Handlebars.js

    Handlebars.js

    Handlebars.js is an extension to the Mustache templating language created by Chris Wanstrath. Handlebars.js and Mustache are both logicless templating languages that keep the view and the code separated like we all know they should be. ...

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

  • TypeScript

    TypeScript

    TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript. ...

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

  • Smarty

    Smarty

    Facilitating the separation of presentation (HTML/CSS) from application logic. This implies that PHP code is application logic, and is separated from the presentation ...

  • Jinja

    Jinja

    It is a full featured template engine for Python. It has full unicode support, an optional integrated sandboxed execution environment, widely used and BSD licensed. ...

  • Hogan.js

    Hogan.js

    Hogan.js is a 3.4k JS templating engine developed at Twitter. Use it as a part of your asset packager to compile templates ahead of time or include it in your browser to handle dynamic templates. ...

Pug alternatives & related posts

EJS logo

EJS

119
217
12
An Embedded JavaScript templating Language
119
217
+ 1
12
PROS OF EJS
  • 4
    It'a easy to understand the concept behind it
  • 4
    For a beginner it's just plain javascript code
  • 2
    Quick for templating UI project
  • 1
    You almost know how to use it from start
  • 1
    Çelik ayna
CONS OF EJS
    Be the first to leave a con

    related EJS posts

    Handlebars.js logo

    Handlebars.js

    6K
    2.4K
    310
    Minimal Templating on Steroids
    6K
    2.4K
    + 1
    310
    PROS OF HANDLEBARS.JS
    • 106
      Simple
    • 77
      Great templating language
    • 51
      Open source
    • 36
      Logicless
    • 20
      Integrates well into any codebase
    • 10
      Easy to create helper methods for complex scenarios
    • 7
      Created by Yehuda Katz
    • 2
      Easy For Fornt End Developers,learn backend
    • 1
      Awesome
    • 0
      W
    CONS OF HANDLEBARS.JS
      Be the first to leave a con

      related Handlebars.js posts

      React logo

      React

      112.7K
      90.5K
      3.8K
      A JavaScript library for building user interfaces
      112.7K
      90.5K
      + 1
      3.8K
      PROS OF REACT
      • 758
        Components
      • 652
        Virtual dom
      • 563
        Performance
      • 486
        Simplicity
      • 436
        Composable
      • 175
        Data flow
      • 159
        Declarative
      • 124
        Isn't an mvc framework
      • 113
        Reactive updates
      • 111
        Explicit app state
      • 32
        JSX
      • 23
        Learn once, write everywhere
      • 19
        Uni-directional data flow
      • 16
        Easy to Use
      • 14
        Works great with Flux Architecture
      • 10
        Great perfomance
      • 8
        Built by Facebook
      • 7
        Javascript
      • 5
        TypeScript support
      • 5
        Speed
      • 4
        Feels like the 90s
      • 4
        Scalable
      • 4
        Easy to start
      • 4
        Awesome
      • 3
        Fancy third party tools
      • 3
        Hooks
      • 3
        Functional
      • 3
        Server side views
      • 3
        Props
      • 2
        Rich ecosystem
      • 2
        Obama
      • 2
        Very gentle learning curve
      • 2
        Has functional components
      • 2
        Simple
      • 2
        Closer to standard JavaScript and HTML than others
      • 2
        Super easy
      • 2
        Has arrow functions
      • 2
        Strong Community
      • 2
        Great migration pathway for older systems
      • 2
        SSR
      • 2
        Fast evolving
      • 2
        Simple, easy to reason about and makes you productive
      • 2
        Excellent Documentation
      • 2
        Scales super well
      • 2
        Just the View of MVC
      • 2
        Server Side Rendering
      • 2
        Cross-platform
      • 1
        Fragments
      • 1
        Start simple
      • 1
        Every decision architecture wise makes sense
      • 1
        Permissively-licensed
      • 1
        Beautiful and Neat Component Management
      • 1
        Sdfsdfsdf
      • 1
        Allows creating single page applications
      • 1
        Split your UI into components with one true state
      • 1
        Sharable
      CONS OF REACT
      • 35
        Requires discipline to keep architecture organized
      • 23
        No predefined way to structure your app
      • 21
        Need to be familiar with lots of third party packages
      • 8
        JSX
      • 7
        Not enterprise friendly
      • 4
        One-way binding only
      • 2
        State consistency with backend neglected
      • 2
        Bad Documentation

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 1.6M 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 · | 26 upvotes · 772.6K 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
      TypeScript logo

      TypeScript

      52.8K
      40.6K
      462
      A superset of JavaScript that compiles to clean JavaScript output
      52.8K
      40.6K
      + 1
      462
      PROS OF TYPESCRIPT
      • 163
        More intuitive and type safe javascript
      • 97
        Type safe
      • 73
        JavaScript superset
      • 46
        The best AltJS ever
      • 27
        Best AltJS for BackEnd
      • 14
        Powerful type system, including generics & JS features
      • 10
        Nice and seamless hybrid of static and dynamic typing
      • 9
        Aligned with ES development for compatibility
      • 9
        Compile time errors
      • 6
        Structural, rather than nominal, subtyping
      • 5
        Angular
      • 3
        Starts and ends with JavaScript
      CONS OF TYPESCRIPT
      • 4
        Code may look heavy and confusing
      • 2
        Hype

      related TypeScript posts

      Yshay Yaacobi

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      Adebayo Akinlaja
      Engineering Manager at Andela · | 26 upvotes · 772.6K 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
      Mustache logo

      Mustache

      1.6K
      354
      50
      Logic-less templates
      1.6K
      354
      + 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

        Smarty logo

        Smarty

        533
        55
        0
        Template engine for PHP
        533
        55
        + 1
        0
        PROS OF SMARTY
          Be the first to leave a pro
          CONS OF SMARTY
            Be the first to leave a con

            related Smarty posts

            Jinja logo

            Jinja

            399
            212
            7
            Full featured template engine for Python
            399
            212
            + 1
            7
            PROS OF JINJA
            • 7
              It is simple to use
            CONS OF JINJA
              Be the first to leave a con

              related Jinja posts

              I have learned both Python and JavaScript. I also tried my hand at Django. But i found it difficult to work with Django, on frontend its Jinja format is very confusing and limited. I have not tried Node.js yet and unsure which tool to go ahead with. I want an internship as soon as possible so please answer keeping that in mind.

              See more
              Hogan.js logo

              Hogan.js

              323
              45
              3
              A compiler for the Mustache templating language
              323
              45
              + 1
              3
              PROS OF HOGAN.JS
              • 3
                Lightweight
              CONS OF HOGAN.JS
                Be the first to leave a con

                related Hogan.js posts