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 I thought that putting them as a style/cultural custom could be a starting point for you to approach them. coming from a position where one has the luck of not being triggered by certain content, one can see them as taglines, or introductions, a way to expose posts to the timelines with elegance and tact instead of just dropping them. and they'll make all the difference for people who are instead triggered by specific things.
@lichen Nah, I still find them annoying. I want to see all content that isn't seriously graphic, e.g. detailed descriptions of rape or pictures of mutilated dead bodies. Of course people are free to use CWs however they want, but I'm also free to defect from their culture that makes me click a bunch of times instead of simply scrolling. I guess I'll probably end up unfollowing the people who use this style most heavily.
@sonya if this is your feeling I won't try further to change your mind, unfollow is the way to go I guess. also there are places in the fediverse where most users seem much more aligned to your perspective, and the software layer allows a wide range of tastes/flavours/customizations at this point.
@sonya yes this appears to be a feature which could be very valuable to converge to, for the different front ends. every tool that aims to minimize potential harms and protect vulnerable users is useful. much more would be needed but it seems like a good start.
@sonya unfortunately software features can help a lot but won't alone impede manifestations of abuse or nastiness. people who won't respect others will always find a way, this is something that can be only counter-acted at the community level, beyond the technology. and this is what ultimately makes the difference between platforms/instances which are otherwise equivalently valuable on the software level imo.
@lichen I agree with subsequent conversation that keyword-blocking would be a great feature to add, although obviously not a panacea.