Kendo UI vs Svelte

Overview

Kendo UI

Stacks297

Followers359

Votes33

GitHub Stars2.6K

Forks1.9K

Svelte

Stacks1.7K

Followers1.6K

Votes502

GitHub Stars84.6K

Forks4.7K

Kendo UI vs Svelte: What are the differences?

Kendo UI and Svelte are both popular frameworks used for developing web applications. While they have some similarities, they also have key differences that set them apart from each other. In this article, we will explore six of the main differences between Kendo UI and Svelte.

Language and Syntax: Kendo UI is based on JavaScript and primarily uses a declarative syntax with HTML-like markup, making it familiar to developers already comfortable with web development. On the other hand, Svelte is a compiler-based framework that uses an imperative approach with its own template language, allowing for more control and efficiency in rendering components.
Bundle Size: When it comes to bundle size, Svelte has a significant advantage over Kendo UI. Svelte compiles the framework code at build time, resulting in smaller bundle sizes and faster loading times for web applications. Kendo UI, on the other hand, requires a larger bundle size due to its extensive library of pre-built UI components and functionalities, which may impact the overall performance of the application.
Reactivity: Svelte is known for its reactive nature. With its built-in reactivity model, Svelte automatically updates and re-renders components when the underlying data changes. This allows for efficient state management and reduces the need for manual state updates. Kendo UI, however, requires manual state management and updating of components, which can be more time-consuming and error-prone.
Community Support and Ecosystem: Kendo UI has a vast and well-established community with extensive documentation, tutorials, and resources available. Additionally, it offers a wide range of UI components and integrations with other frameworks. Svelte, though relatively new compared to Kendo UI, has been gaining popularity and has an active community. However, its ecosystem is still developing, and it may not have the same level of community support and resources as Kendo UI.
Learning Curve: Kendo UI provides a more straightforward learning curve for developers already familiar with web development, as it follows a familiar syntax and uses widely-used technologies such as HTML, CSS, and JavaScript. Svelte, on the other hand, has a steeper learning curve due to its unique syntax and compiler-based approach. Developers may need to invest more time and effort to become proficient in Svelte.
Integration with Existing Projects: As Kendo UI is a library of UI components, it can be easily integrated into existing projects built with different frameworks or libraries, such as Angular, React, or Vue. Svelte, being a full-fledged framework, may require more effort to integrate into an existing project that uses a different framework or library.

In Summary, while both Kendo UI and Svelte are useful frameworks for web application development, they differ in terms of language and syntax, bundle size, reactivity, community support, learning curve, and integration with existing projects. Considering these differences can help developers choose the right framework for their specific needs and requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Kendo UI, Svelte

Máté

Senior developer at Self-employed

May 28, 2020

Decided

Svelte is everything a developer could ever want for flexible, scalable frontend development. I feel like React has reached a maturity level where there needs to be new syntactic sugar added (I'm looking at you, hooks!). I love how Svelte sets out to rebuild a new language to write interfaces in from the ground up.

311k views311k

Comments

Raj

Oct 10, 2020

Review

It purely depends on your app needs. Does it need to be scalable, do you have lots of features, OR it is a simple project with very simple needs - many of those parameters clarify which technologies will fit.

If you are looking for a quick solution, that reduces lot of development time, take a look at postgraphile (https://www.graphile.org/postgraphile/). You have to just define the schema and you get the entire graph-ql apis built for you and you can just focus on your frontend.

On frontend, React is good, but also need to remember that it is popular because it introduced one way data writes and in-built virtual dom + diffing to determine which dom to modify. Though personally I liked it, am recently more inclined to Svelte because its lightweightedness and absence of virtual dom and its simplicity compared to the huge ecosystem that React has surrounded itself with.

In all situations, frameworks keep changing over time. What is best today is not considered even good few years from now. What is important is to have the logic in a separate, clean manner void of too many framework related dependencies - that way you can switch one framework with another very easily.

3.76k views3.76k

Comments

Alex

Full-stack software engineer

Apr 25, 2020

Decided

Svelte 3 is exacly what I'm looking for that Vue is not made for.

It has a iterable dom just like angular but very low overhead.

This is going to be used with the application.

for old/ lite devices . ie.

android tv,
micro linux,
possibly text based web browser for ascci and/or linux framebuffer
android go devices
android One devices

125k views125k

Comments

Detailed Comparison

Kendo UI	Svelte
Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. AngularJS integration, Bootstrap support, mobile controls, offline data solution.	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.
Ultimate Performance with Minimum Resources;Mobile-Friendly and Responsive;Built-In, Customizable Themes ;Open Source Core	Write less code; No virtual DOM; Truly reactive
Statistics
GitHub Stars 2.6K	GitHub Stars 84.6K
GitHub Forks 1.9K	GitHub Forks 4.7K
Stacks 297	Stacks 1.7K
Followers 359	Followers 1.6K
Votes 33	Votes 502
Pros & Cons
Pros 15 Collection of controls 5 Speed 4 Multi-framework support 4 Mobile 2 Built-in router Cons 4 Massive footprint 3 Slow 1 Expensive 1 Awdawd 1 Poor customizability	Pros 59 Performance 41 Reactivity 36 Components 35 Simplicity 34 Javascript compiler (do that browsers don't have to) Cons 3 Event Listener Overload 2 Complex 2 Learning Curve 2 Hard to learn 2 Little to no libraries
Integrations
Bootstrap AngularJS	No integrations available

What are some alternatives to Kendo UI, Svelte?

jQuery

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

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.

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.

Vue.js

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

jQuery UI

Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.

Flux

Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.

Famo.us

Famo.us is a free and open source JavaScript platform for building mobile apps and desktop experiences. What makes Famo.us unique is its JavaScript rendering engine and 3D physics engine that gives developers the power and tools to build native quality apps and animations using pure JavaScript.

Riot

Riot brings custom tags to all browsers. Think React + Polymer but with enjoyable syntax and a small learning curve.

Marko

Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags.

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

Related Comparisons

Kendo UI vs Svelte: What are the differences?

Language and Syntax: Kendo UI is based on JavaScript and primarily uses a declarative syntax with HTML-like markup, making it familiar to developers already comfortable with web development. On the other hand, Svelte is a compiler-based framework that uses an imperative approach with its own template language, allowing for more control and efficiency in rendering components.
Bundle Size: When it comes to bundle size, Svelte has a significant advantage over Kendo UI. Svelte compiles the framework code at build time, resulting in smaller bundle sizes and faster loading times for web applications. Kendo UI, on the other hand, requires a larger bundle size due to its extensive library of pre-built UI components and functionalities, which may impact the overall performance of the application.
Reactivity: Svelte is known for its reactive nature. With its built-in reactivity model, Svelte automatically updates and re-renders components when the underlying data changes. This allows for efficient state management and reduces the need for manual state updates. Kendo UI, however, requires manual state management and updating of components, which can be more time-consuming and error-prone.
Community Support and Ecosystem: Kendo UI has a vast and well-established community with extensive documentation, tutorials, and resources available. Additionally, it offers a wide range of UI components and integrations with other frameworks. Svelte, though relatively new compared to Kendo UI, has been gaining popularity and has an active community. However, its ecosystem is still developing, and it may not have the same level of community support and resources as Kendo UI.
Learning Curve: Kendo UI provides a more straightforward learning curve for developers already familiar with web development, as it follows a familiar syntax and uses widely-used technologies such as HTML, CSS, and JavaScript. Svelte, on the other hand, has a steeper learning curve due to its unique syntax and compiler-based approach. Developers may need to invest more time and effort to become proficient in Svelte.
Integration with Existing Projects: As Kendo UI is a library of UI components, it can be easily integrated into existing projects built with different frameworks or libraries, such as Angular, React, or Vue. Svelte, being a full-fledged framework, may require more effort to integrate into an existing project that uses a different framework or library.

Kendo UI vs Svelte

Overview