# How Svelte and Elm compare?

**URL:** <https://discourse.elm-lang.org/t/how-svelte-and-elm-compare/8604>\
**Category:** Learn\
**Created:** [August 19, 2022, 4:53pm UTC](https://discourse.elm-lang.org/t/how-svelte-and-elm-compare/8604 "2022-08-19T16:53:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dta](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/dta/32/1917_2.png) [@dta](https://discourse.elm-lang.org/u/dta)\
**Post date:** [August 19, 2022, 7:45pm UTC](https://discourse.elm-lang.org/t/how-svelte-and-elm-compare/8604/3 "2022-08-19T19:45:04Z")

</div>

I think this is actually a reasonable question to ask since Elm is both a language and a framework, and the compiler output of Elm is in the same language Svelte uses.

There have already been two threads about this with lots of details:

> [@Could updating the DOM directly instead of the virtual dom get any advantage for elm? (the way it does for svelte)](https://discourse.elm-lang.org/t/could-updating-the-dom-directly-instead-of-the-virtual-dom-get-any-advantage-for-elm-the-way-it-does-for-svelte/3995):
>
> I am trying to understand more how that would work / why it won’t.

> [@Can the compiler skip virtual DOM?](https://discourse.elm-lang.org/t/can-the-compiler-skip-virtual-dom/6300):
>
> Since Elm is compile to js code, is it possible to go svelte’s approach to directly compile to raw dom manipulation, and no vdom?

---

_[View the full topic](https://discourse.elm-lang.org/t/how-svelte-and-elm-compare/8604)._
