Alternatives to Preact logo

Alternatives to Preact

React, Inferno, Glimmer, Mithril, and act are the most popular alternatives and competitors to Preact.
343
241
+ 1
24

What is Preact and what are its top alternatives?

Preact is an attempt to recreate the core value proposition of React (or similar libraries like Mithril) using as little code as possible, with first-class support for ES2015. Currently the library is around 3kb (minified & gzipped).
Preact is a tool in the Javascript UI Libraries category of a tech stack.
Preact is an open source tool with 30.4K GitHub stars and 1.7K GitHub forks. Here’s a link to Preact's open source repository on GitHub

Top Alternatives to Preact

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

  • Inferno

    Inferno

    Inferno is an isomorphic library for building high-performance user interfaces, which is crucial when targeting mobile devices. Unlike typical virtual DOM libraries like React, Mithril, Virtual-dom, Snabbdom and Om, Inferno uses techniques to separate static and dynamic content. This allows Inferno to only "diff" renders that have dynamic values. ...

  • Glimmer

    Glimmer

    Glimmer is one of the fastest DOM rendering engines, delivering exceptional performance for initial renders as well as updates. ...

  • Mithril

    Mithril

    Mithril is around 12kb gzipped thanks to its small, focused, API. It provides a templating engine with a virtual DOM diff implementation for performant rendering, utilities for high-level modelling via functional composition, as well as support for routing and componentization. ...

  • act

    act

    Rather than having to commit/push every time you want test out the changes you are making to your .github/workflows/ files (or for any changes to embedded GitHub actions), you can use this tool to run the actions locally. The environment variables and filesystem are all configured to match what GitHub provides. ...

  • Svelte

    Svelte

    If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads. ...

  • jQuery

    jQuery

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

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

Preact alternatives & related posts

React logo

React

113.5K
91.1K
3.8K
A JavaScript library for building user interfaces
113.5K
91.1K
+ 1
3.8K
PROS OF REACT
  • 760
    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 · 785.5K 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
Inferno logo

Inferno

23
55
19
A fast, React-like JavaScript library for building UIs
23
55
+ 1
19
PROS OF INFERNO
  • 4
    React-like api
  • 4
    Faster than React
  • 3
    Smaller bundles
  • 3
    Faster than Angular
  • 3
    Faster than Vue
  • 2
    Compatibility package for existing React apps
CONS OF INFERNO
    Be the first to leave a con

    related Inferno posts

    Glimmer logo

    Glimmer

    7
    15
    0
    Fast and light-weight UI components for the web
    7
    15
    + 1
    0
    PROS OF GLIMMER
      Be the first to leave a pro
      CONS OF GLIMMER
        Be the first to leave a con

        related Glimmer posts

        Mithril logo

        Mithril

        73
        71
        81
        Client-side MVC framework - a tool to organize code in a way that is easy to think about...
        73
        71
        + 1
        81
        PROS OF MITHRIL
        • 16
          Lightweight
        • 11
          Faster than React
        • 10
          Pure JavaScript
        • 9
          Virtual Dom
        • 8
          Robust
        • 7
          Works with ES6
        • 7
          Unopinionated
        • 5
          Very active development
        • 4
          Intelligent auto-redrawing system
        • 3
          Flux compatible
        • 1
          Small Learning Curve
        CONS OF MITHRIL
        • 1
          Virtual Dom

        related Mithril posts

        act logo

        act

        5
        19
        0
        Run your GitHub Actions locally
        5
        19
        + 1
        0
        PROS OF ACT
          Be the first to leave a pro
          CONS OF ACT
            Be the first to leave a con

            related act posts

            Svelte logo

            Svelte

            728
            827
            412
            A UI framework that compiles into tiny standalone JavaScript modules
            728
            827
            + 1
            412
            PROS OF SVELTE
            • 41
              Performance
            • 32
              Reactivity
            • 29
              Javascript compiler (do that browsers don't have to)
            • 29
              Components
            • 28
              Simplicity
            • 26
              Lightweight
            • 24
              Real Reactivity
            • 23
              Fast as vanilajs
            • 22
              Near to no learning curve
            • 16
              Compiler based
            • 16
              All in one
            • 15
              Scalable
            • 15
              Use existing js libraries
            • 13
              SSR
            • 13
              Very easy for beginners
            • 12
              Composable
            • 11
              Ease of use
            • 11
              No runtime overhead
            • 9
              Built in store
            • 7
              Typescript
            • 6
              Start with pure html + css
            • 6
              Best Developer Experience
            • 5
              Templates
            • 3
              Speed
            CONS OF SVELTE
            • 2
              Complex
            • 2
              Learning Curve
            • 2
              Hard to learn
            • 2
              Event Listener Overload
            • 1
              Little to no libraries

            related Svelte posts

            Sarmad Chaudhary
            Founder & CEO at Ebiz Ltd. · | 9 upvotes · 435.2K 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
            jQuery logo

            jQuery

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

            related jQuery posts

            Kir Shatrov
            Engineering Lead at Shopify · | 20 upvotes · 562.7K 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 | Module Lead · | 19 upvotes · 2.5M 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
            AngularJS logo

            AngularJS

            45.4K
            32.8K
            5.2K
            Superheroic JavaScript MVW Framework
            45.4K
            32.8K
            + 1
            5.2K
            PROS OF ANGULARJS
            • 887
              Quick to develop
            • 586
              Great mvc
            • 570
              Powerful
            • 521
              Restful
            • 503
              Backed by google
            • 348
              Two-way data binding
            • 343
              Javascript
            • 328
              Open source
            • 305
              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
            • 17
              Light weight
            • 17
              Awesome
            • 14
              Angular 2.0
            • 14
              Javascript mvw framework
            • 13
              Efficient
            • 13
              Great extensions
            • 10
              Easy to prototype with
            • 8
              Coffeescript
            • 8
              High performance
            • 7
              Lots of community modules
            • 7
              Mvc
            • 7
              Two-way binding
            • 6
              Clean and keeps code readable
            • 6
              Easy to e2e
            • 5
              Easy for small applications
            • 5
              One of the best frameworks
            • 4
              Works great with jquery
            • 4
              Fast development
            • 2
              Hierarchical Data Structure
            • 2
              Community
            • 2
              The two-way Data Binding is awesome
            • 2
              Typescript
            • 2
              Dart
            • 2
              I do not touch DOM
            • 2
              Be a developer, not a plumber.
            • 2
              Declarative programming
            • 1
              Amazing community support
            • 1
              Readable code
            • 1
              Fkin awesome
            • 1
              Acoperișul
            • 1
              The powerful of binding, routing and controlling routes
            • 1
              Opinionated in the right areas
            • 1
              Supports api , easy development
            • 1
              Common Place
            • 1
              Great
            • 1
              Very very useful and fast framework for development
            • 1
              Linear learning curve
            • 1
              Scopes
            • 1
              Programming fun again
            • 0
              Acoperișul 0757604335
            • 0
              Httpș//Acoperișul 0757604335
            • 0
              Shvzjn
            • 0
              Oautho loc
            • 0
              Js
            • 0
              Angular js
            • 0
              Bot Ionescu
            • 0
              Google.com
            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 · | 25 upvotes · 2.1M 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 · | 20 upvotes · 804.8K 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