Alternatives to Svelte logo

Alternatives to Svelte

React, Elm, Imba, Stencil, and Preact are the most popular alternatives and competitors to Svelte.
985
1.1K
+ 1
442

What is Svelte and what are its top alternatives?

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.
Svelte is a tool in the Javascript UI Libraries category of a tech stack.
Svelte is an open source tool with 60.3K GitHub stars and 2.9K GitHub forks. Here’s a link to Svelte's open source repository on GitHub

Top Alternatives to Svelte

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

  • Elm
    Elm

    Writing HTML apps is super easy with elm-lang/html. Not only does it render extremely fast, it also quietly guides you towards well-architected code. ...

  • Imba
    Imba

    Imba is a new programming language for the web that compiles to performant and readable JavaScript. It has language level support for defining, extending, subclassing, instantiating and rendering dom nodes. ...

  • Stencil
    Stencil

    Stencil combines some of the best features from traditional frameworks, but outputs 100% standards-compliant Custom Elements, part of the Web Component spec. ...

  • Preact
    Preact

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

  • Sapper
    Sapper

    Sapper focuses on easy of use. It is alpha now and only compiled with rust nightly. ...

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

Svelte alternatives & related posts

React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.9M 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 · | 27 upvotes · 1.2M 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
Elm logo

Elm

628
695
314
A type inferred, functional reactive language that compiles to HTML, CSS, and JavaScript
628
695
+ 1
314
PROS OF ELM
  • 44
    Code stays clean
  • 42
    Great type system
  • 40
    No Runtime Exceptions
  • 33
    Fun
  • 28
    Easy to understand
  • 22
    Type safety
  • 22
    Correctness
  • 16
    JS fatigue
  • 12
    Declarative
  • 12
    Ecosystem agrees on one Application Architecture
  • 10
    Friendly compiler messages
  • 8
    Fast rendering
  • 7
    Welcoming community
  • 7
    If it compiles, it runs
  • 5
    Stable ecosystem
  • 4
    'Batteries included'
  • 2
    Package.elm-lang.org
CONS OF ELM
  • 2
    No typeclasses -> repitition (i.e. map has 130versions)
  • 2
    JS interoperability a bit more involved
  • 1
    Backwards compability breaks between releases
  • 1
    More code is required
  • 1
    Main developer enforces "the correct" style hard
  • 1
    JS interop can not be async
  • 1
    No communication with users

related Elm posts

Shared insights
on
ReactReactReduxReduxElmElm

React is awesome, but is just a view library, when we need to manage state, there is Redux.js. The ecosystem of redux is big, complex and hard to integrate. That's why we choose to create hydux. Hydux is simple, the main idea is from Elm, a pure functional vdom-based framework for front-end. We seperate the whole app with state, actions and views. Which means not only our views are a tree, but also our state and actions. Reuse state and actions are just like reuse react components, no need to consider dependences.

See more
Imba logo

Imba

14
33
0
Take a whole lot of Ruby, a pinch of Python and some React, get Imba
14
33
+ 1
0
PROS OF IMBA
    Be the first to leave a pro
    CONS OF IMBA
      Be the first to leave a con

      related Imba posts

      Stencil logo

      Stencil

      75
      88
      0
      A reusable web component generator
      75
      88
      + 1
      0
      PROS OF STENCIL
        Be the first to leave a pro
        CONS OF STENCIL
          Be the first to leave a con

          related Stencil posts

          Michael Solati
          Developer Advocate at Typeform · | 4 upvotes · 36.2K views
          Shared insights
          on
          PolymerPolymerStencilStencil
          at

          As a #Frontend developer I'm used to using tools like #BootstrapCDN or some APIs/Library like #GoogleMaps to create or have styled elements with cool functionality. But this requires me remembering Bootstrap classes, or trying to get Google Maps to work in #Angular. 😢

          And that's just framework agnostic solutions... If you look at framework specific libraries you end up dealing with the fact you are pigeon holed into using framework specific libraries!

          Libraries like Polymer or Stencil for #WebComponents are definitely the way to go!

          See more
          Preact logo

          Preact

          383
          264
          24
          Fast 3kb alternative to React with the same ES6 API
          383
          264
          + 1
          24
          PROS OF PREACT
          • 13
            Lightweight
          • 4
            Drop-in replacement for React
          • 3
            Props/state passed to render
          • 3
            Performance
          • 1
            ES6 class components
          CONS OF PREACT
            Be the first to leave a con

            related Preact posts

            Dmitry Mukhin

            Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

            Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

            For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

            However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

            All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

            See more
            Riderman De Sousa Barbosa
            Shared insights
            on
            PreactPreactReactReact
            at

            The first and most important premise is that should be fast.. really fast. This premise was basically because this is an PWA project, and the main goal of this project are be more efficient on restaurant.

            So I ended up choosing Preact instead React .

            This made the app (PWA) more faster, not only when navigating but improve TTI and data usage.

            See more
            Sapper logo

            Sapper

            37
            57
            0
            A lightweight web framework written in Rust
            37
            57
            + 1
            0
            PROS OF SAPPER
            • 0
              Less bundle Size
            CONS OF SAPPER
              Be the first to leave a con

              related Sapper posts

              jQuery logo

              jQuery

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

              related jQuery posts

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

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

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

              #FrameworksFullStack #Languages

              See more
              Ganesa Vijayakumar
              Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M 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

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

              related AngularJS posts

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

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

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

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

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