#react: Ok, so you probably don't just start with React. You want Next, or maybe Remix, for starters. After that, you're gonna want Tailwind, which means you'll probably want classnames or tailwind-merge...maybe both. Or you could just go with styledComponents. Anyway, be sure to have Redux, along with Redux toolkit, and React Query. After that, it's just a matter of micromanaging the framework for desired performance!
#svelte: Go with SvelteKit. It has everything you need. Have fun!
The new Dev Toolbar in @astro 4.0 is a great example of what makes open source so special.
🧡 #svelte has had built-in accessibility rules for ages. We adapted the audit logic from their compiler to provide the basis of Astro's in-browser tooling.
💚 @nuxt has their own awesome DevTools project! We took a different approach, but we've loved watching their feature evolve over the past year.
💛 @vite has an amazing /__open-in-editor feature that powers our click to open functionality.
🎉 New blog post! For a few months now I've been toying with an idea for a new #Svelte framework for #datavisualization -- heavily inspired by the great Observable Plot. Very curious to hear what you think about this.
I’ve spent the last few months crafting my own home on the Web, and I wanted to make sure it presented me as a human, not defined solely by my work as a #DesignEngineer / #WebDev.
This has also been a great opportunity to finally use #Svelte & #SvelteKit in a project. I love how easy it was to learn and how intuitive it is, as someone who started with vanilla HTML and CSS
It's where I experiment with all things web, like #html#css#javascript esp. #svelte and #svg most often in the context of #dataviz or similar forms of visual storytelling.
Thanks to Enrico Bertini for sharing this awesome read by Connor Rothschild about a 'framework-first' aproach to #datavisualization. I've never seen #Svelte and #D3 compared for visualization so clearly before. Really well done.
Du Bois Data Visualization Society Challenge - Week 6/10: My recreation of Du Bois' poster no. 54, done with D3, Svelte. Again I tried to recreate it as close to the original as possible and make it responsive.
Want to use view transitions in your #SvelteKit app?
v1.24 unlocks view transitions with a new lifecycle method. We’ve already added them to the #Svelte site - watch the blog titles slide into place! (note: it will fade instead of slide if reduced-motion is requested)
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!
I stayed up too late writing about how to get Svelte 5 pre-release alpha running so you can start building with Svelte Runes locally and discovered midway through a heaps easier way to do it. Aaaaaanyway here's how if you're interested. https://josh.is-cool.dev/running-runes-locally-with-svelte-5-pre-release-alpha/
#Svelte 5 with Runes changes the game. As app authors it requires us to be a bit more explicit with reactivity but for svelte framework authors this approach greatly reduces complexity and unlocks huge performance boost and way less reactivity pitfalls/ bugs
@jaredwhite’s personal thoughts on a great entry by @collinsworth into the growing body of work which details why greenfield #WebDev projects are better served by other frameworks…or none at all.
"This means that the design of the framework is largely settled, with no anticipated breaking changes between now and the stable release, and that the most egregious bugs have been stomped.
"It doesn't mean that it's ready for production, or that nothing will change between now and 5.0. But if you've held off on dabbling with Svelte 5 during the public beta phase, now is a great time to try it out."
Once again I get foiled by switching languages. :blobcatfacepalm2:
In Javascript, you have to compare strings with ===, not ==, or else you'll run into type coercion problems, because Javascript thinks 1 == "1" is a totally fine thing to be true. (it's not)
But in Kotlin, === compares identity not equality for strings. But in the JVM, string values are aggressively cached, so === actually does what you want most of the time. Unless your strings come from weird places, like JNI code. Then you get awful non-deterministic behavior that's incredibly hard to debug, but it totally goes away when you use the correct comparison operator == for strings.
sigh I'm not really as good at this whole programming thing as I should be by now.