Cybernetically enhanced web apps.
A most interesting tagline for the Svelte framework since version 3. The Svelte team prides itself in aggressi...
For further actions, you may consider blocking this person and/or reporting abuse
I like the "empowerment" term. I feel like Svelte has the best of both worlds in regard to simplicity and full development power.
When I started using it more often, it quickly ruined my experience working with React. If it weren't for NextJS, I have would dropped React a long time ago.
And even to this date, whenever I want to build something custom, my go-to is Svelte right from the get-go. It's such a user-friendly technology that even web dev beginners can start using right away (I wrote about just that before).
Great review! Pretty thorough and well put together.
Believe it or not, I have heard the exact same sentiment from all of the React developers that I have introduced Svelte to. They always have that priceless look of shock and disbelief at the fact that front-end development can actually be beautiful. Then the conversation always leads to how they are so relieved to not worry about hooks anymore. It just never gets old!
Yooo that's it. "Not worry about hooks anymore". Perfect line.
Don't have to scour through docs to see what new "hooks" appeared or when to properly implement "useRef" or whatever else.
Web development can be as simple as HTML and CSS powered by Svelte's reactivity in ease of use with JS baked in.
Svelte is truly beautiful and magical ♥.
I think the only reason why most newbies choose React and bear the struggle, is because of the opportunities.
The fatal flaw of Svelte is that the REPL of Svelte.dev is not supported as an
embedon Dev.to, and that Dev.to's code blocks do not supportsvelte, so we have to write them inhtmlorjsx.I wouldn't consider these as "fatal flaw[s]", to be honest. Perhaps an "inconvenience" is a more appropriate description. The former example may simply be for security purposes, as the REPL does run arbitrary JavaScript. Meanwhile, the latter example will sort itself out over time as adoption increases.
I must concede, however, that there is no other way around the lack of Svelte-native syntax highlighting for now. But it is awesome that plain
htmlis sufficient to highlight the Svelte language, which is a testament to its commitment to extend the Web platform rather than to supplant it.Haha, this is a joke that is a compliment to Svelte
Job market is the only downside of svelte I think
That's mostly because a lot of applications have already gone too deep into other frameworks. It will be too costly to rewrite them completely. Nevertheless, I strongly believe that Svelte will be the future. In fact, it already is the present of new applications, where legacy is not a concern. It's really just a matter of time.
Micro-frontends.
Start re-writing UI projects with Module Federation or
single-spa. Then migrate progressively.If you are a minimalist such as myself then you might like Htmx framework.
No compiler needed just HTML, CSS and JS. You can use Vanillajs, Alpinejs and even JQuery if you want to depending on your needs.
I've used svelte since pre 1.0 and love it however I find Htmx very interesting in how they do things differently.
If your a rust fan svelte can be used with Tauri to create desktop apps for mac, windows and linux.
Happy Coding
Ah, yes. I'm well aware of HTMX and its hypermedia philosophy. Though I must mention that HTMX solves a completely different problem than SvelteKit's more general-purpose all-in-one SSR, CSR, and SSG solution.