Working on Svelte is so rewarding as a long time vanilla JS developer. All the accumulated web knowledge over the years just instantly available to you, while enjoying the augmented DX.
I have to say that's the best thing happened to the web. Imagine you don't need to throw away everything in order to progress, instead just enjoy the compounding benefits of your existing web knowledge.
(Le 1er projet est en #Svelte, #SvelteKit, mais à partir du moment où la personne est senior, maîtrise un framework JS, et peut conseiller nos clients en termes d'architecture, c'est ok.)
I’m starting to fall in love with #svelte@sveltejs I finally have a change to work with Svelte within real production codebase and it's nothing but a pleasure. For a newbie with long React background this feels like - «OMG, it actually could be just that simple!»
It's still early days, and I'm only scratching the surface but so far it feels really good.
I've seen this article pass by a few times. Pretty good.
The one impression Tailwind has left me is that's it niche. A solution for a singular type of setup. Popular? Yes. How the web works? No. Will it stick? I don't see how. #css#DesignEngineering
Matthias Stahl started a beginner friendly video series, where he goes through nice little mini-projects and explains how to make responsive #dataviz with the perfect combo of svelte and d3 :)
If there was an #HTML element that changes it's content when users interact with other elements on the page, what name would it have?
PLEASE NOTE: I am not suggesting that this element needs to exist; I am only asking what it would be called. I'm building a CustomElement, I just want it to have a name that makes sense.
Vote and suggest others in replies. Please boost for reach!
Dear Dev Mastodon, I'm torn between Solid.js and Svelte for a small SPA project. I've done a lot of React dev so Solid seems familiar but I quite like the apparent simplicity of Svelte. Any opinions, advice, gotchas I should be aware of?
Searched the internet for tips on using #Django with #Svelte, hoping specifically for guidance on incorporating Svelte components into Django templates. The first result is an article telling me how to ignore Django templates completely, move all #frontend development to #JavaScript in the form of an SPA, and turn my #backend into a REST #API. Turns out, things can depress you even when they're not surprising.
New blog post: #SvelteKit 2.4 added a new read method that simplifies reading assets on the server. I did a quick writeup on how it simplifies retrieving raw font data in one of my old #Svelte social image demos.
TIL that @sveltejs/enhanced-img is subject to a preprocessing step to convert its src prop into an import.
As a consequence, you can't use <enhanced:img /> inside another component and pass in a src at runtime. This restriction seems to be inherited from vite-imagetools.
<enhanced:img /> is in its infancy, therefore lots of room for improvement.