Impressions on Svelte from a non pro
Tags: react, frontenddev, javascript, svelte
Published: 2019-10-06 20:18:18

---
title: Impressions on Svelte from a non pro
published: true
date: 2019-10-03 17:14:29 UTC
tags: react,front-end-developmen,javascript,svelte
canonical_url: 
---

### Impressions on Svelte (non pro)

I guess i’m vulnerable to the _new shiny thing syndrome_. I wasn’t looking for any kind of web framework (as usual), as i was clicking [Svelte is the most beautiful web framework I’ve ever seen](https://dev.to/jesseskinner/svelte-is-the-most-beautiful-web-framework-i-ve-ever-seen-325f) (as usual).

### Background

Building the backends, frontend development seemed pretty chaotic to me for a long time. [React](https://reactjs.org) paved the way. First time i felt comfortable structuring JavaScript.   
With many available component libraries, it was easy enough to get my first web apps ([https://pdf2md.morethan.io](https://pdf2md.morethan.io), [https://jmh.morethan.io](https://jmh.morethan.io)) up and running even though my knowledge of JavaScript, HTML and CSS was lacking.

### Fast forward to Svelte

Documentation of [Svelte](https://svelte.dev) is pretty good. It has a neat [tutorial](https://svelte.dev/tutorial/), a simple but helpful [API documentation](https://svelte.dev/docs) and a [examples section](https://svelte.dev/examples) (which is more or less an replication of the tutorial).  
Getting started is really simple. Bootstrap a running hello world app up with these 3 commands:

```
npx degit sveltejs/template
npm install
npm run dev
```

To get into Svelte, I decided to build a simple numerology calculator for names ([Nanuca](https://nanuca.morethan.io)). I found it pretty straight forward to get up to speed, and looking back at the [API documentation](https://svelte.dev/docs) after the first evening, i was amazed that there isn’t so much stuff to learn anyway.

### Impressions and thoughts

- Easy to start, cushy learning curve.
- Less concepts to master, less boilerplate then [React](https://reactjs.org).
- It forced me to learn more CSS and JS basics (which was a good thing to me at this point in time)
- — [React](https://reactjs.org) has an amazing ecosystem. Lots of predefined components available. You don’t have to master HTML/CSS to build something great.
- — Every once in a while however i run into a simple problem which took annoyingly long to solve without that basic knowledge.
- Even something fairly complex like animations and transitions are pretty simple to master.
- There is a out-of-the-box [store implementation](https://svelte.dev/docs#svelte_store) which takes some time to get used to, but probably less then the [Redux](https://redux.js.org) and co thing.
- With so many amazing component-based frameworks out there, it seems beneficial to build JavaScript libraries which are not tight to one framework in particular.

Simply said… i’m just enjoying working _in_ [Svelte](https://svelte.dev). It’s simple, it’s powerful, it never stepped in my way so far! So this time, i’m pretty happy i fell pray to [Svelte is the most beautiful web framework I’ve ever seen](https://dev.to/jesseskinner/svelte-is-the-most-beautiful-web-framework-i-ve-ever-seen-325f).

### More

There is probably a lot of more to say about what [Svelte](https://svelte.dev) is and how it works… but i leave that to the masters of JavaScript. [This small writeup](https://gist.github.com/Rich-Harris/0f910048478c2a6505d1c32185b61934) might be a good starting point for going into the theoretical background.

Find the code of the example project here: [[https://nanuca.morethan.io](https://nanuca.morethan.io)]

* * *