Gotta say I really enjoy SvelteJS and the promise of "disappearing frameworks." https://toot.cafe/@peter/100243209978458086 (via @peter)
@rich_harris did a great job explaining the concepts behind SvelteJS at JSConf EU (https://www.youtube.com/watch?v=qqt6YxAZoOc).
I saw the same Jed Schmidt talk he mentions, and it really was enlightening to realize that a web app is conceptually a directed graph but the DOM is a tree, and this is why it's so hard for JS frameworks to get the abstraction right. But if your JS framework is a compiler, then that means you can describe your app as a graph and the framework can generate the tree.
As for the user experience of Svelte, I really enjoyed it even beyond the perf benefits or the space-age feeling of having a framework compile my code for me. It's similar to Vue in that you have computations and watchers, and that you write single-file components.
I also found that Svelte "got out of my way" and let me write vanilla JS code whenever I wanted to. Compared to something like React, I found Svelte was both 1) easier to learn, and 2) felt less like I was writing "framework code."
@nolan question is this the kind of tech talk you could maybe CW?
I've been a lot more mindful about CWs lately, and who I generally don't ask for CWs.. I'm trying to break the mold to help others be a bit more mindful too.
@maloki Yeah I'm trying to figure out recently how to balance this. Thanks for the feedback!
@sonya I say this to try introducing the perspective of why they appear to be so valuable and interesting for many people, myself included. when I switched to mastodon from twitter at first it sounded weird to me too to see cw used widely, even for things entirely innocent, or even for good puns and jokes. it took some time to understand why they are important and appreciate their use beyond the strict scope of universally agreed-upon cws.
@sonya a thread on the use of cws I can suggest (with clearer explanation than mine) is this one https://hex.bz/@beezyal/99965592592952742