> <i>Svelte is a language.</i><p>All Javascript frameworks may become implementations of SAT solvers, where rendering and state are scheduled constraints, i.e. tiny operating systems.<p><i>NPM uses CSS as a query language</i> -
<a href="https://news.ycombinator.com/item?id=33136843">https://news.ycombinator.com/item?id=33136843</a> - 9 months ago<p>Then apps may be instantiations of the framework.
The really exciting thing about svelte is getting rid of the virtual Dom. Having everything just be explicit JavaScript code that modifies the Dom manually makes for really readable code. If you have not tried it, got to the svelte tutorial and look at the output code. It's awesome.
Using the label and block syntax for this was a stroke of genius.<p>Two great things about this "thinking inside the box" approach are:<p>1. You're encouraged to use native APIs because they're highly unlikely to clash with the framework.<p>2. You can a legible stack trace. After all, the only thing the compiler does to your JavaScript is add some instrumentation here and there.
Svelte Kit is great for static is "classic"-like websites.<p>I've converted my company website to svelte-kit from first Angular, then Vue.<p>But for SPA it's bad. If you use oidc auth. There's only Auth.JS and it's a confidential client, for Svelte Kit.<p>If you're not using svelte-kit you can use vite to create a Svelte SPA. There you can use your PCKE client as usual and burden the load on the client.<p>I have yet to experiment with how well it works with a graphql client. Apollo has its own cache but I'm not sure there is a svelte version of it. There is for Vue. Does it even need one? The default is for React. Is Apollo even needed? Questions over questions.<p>Why Svelte? Performance. Performance matters, a lot.<p>Svelte being a "language".
First time using a template system?
I have to wonder.
Svelte is a major improvement on vuejs. It is a pleasure to work with. I can’t stand react / JSX. Highly recommend anyone who preferred vue over react to give svelte a try.
I love the idea of "thinking inside the box". It's a great encapsulation of the hacker mindset. A fun talk about it in another context (impro theater): <a href="https://www.youtube.com/watch?v=bz9mo4qW9bc">https://www.youtube.com/watch?v=bz9mo4qW9bc</a>
Give a quick glance to Svelte.
Help me understand, how this syntax
{#if expression}...{:else if expression}...{/if}
can be seriously invented in our... more civilized age?
Great insight. It feels like at some point reactivity as a language primitive should be built into js. Most frameworks start with this and then build out into a opinionated implementation, dissolving the ecosystem into framework fragments. Any known reasons why this is / was never implemented?
I wish people stopped calling websites as applications and I wish web site developers spent more time learning how the world has been building great desktop apps for years. It’s just beneficial to get out of the bubble once in awhile to validate certain ideas