That doesn't help. What is Sapper? This is defining web tech in terms of other web tech.

See Svelte as a JavaScript library like React or Angular, which allows you to develop web applications easily.

Now, SvelteKit is bringing the library to the _framework_ level (big big emphasis on "framework", we all have different definitions for what a framework is), which adds easy routing, server-side rendering, optimized JavaScript bundles per page for the client, etc.

Bit of a nitpick, but wouldn't the comparison be SvelteKit as similar to Angular, and Svelte similar to React?

> It's an application framework for Svelte

Doesn't that ring a bell?

Not another framework please. What's wrong with developing libraries and releasing them separately?

Because to start a project you have to spend days and even months researching libraries, the current best practices, etc. and then glue them all together with some monster build system (webpack, etc.) and pray that one library doesn't update to be incompatible, or that the library maintainer loses interest and maintenance, etc. And then if you look at another project you have to learn everything again because they took an entirely different approach of glueing together libraries.

These frameworks are an opinionated take on project structure meant to save time and effort. Can they build anything and everything with JS? No, and they don't make such promises. Can they build most apps and things people want to build, and with a much faster and simpler setup? Absolutely, yes.

But honestly this isn't the thread to fight the framework vs. library fight. That ship sailed _years_ ago after create-react-app got popular.

Isn't that exactly what's happening? Svelte is a library and SvelteKit is a framework built on top of it? I think.

That's pretty much it, yeah. But on HN, you will always find framework = bad comments.