this post was submitted on 23 Jun 2023
856 points (100.0% liked)

Technology

37801 readers
268 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

The exchange is about Meta's upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!

you are viewing a single comment's thread
view the rest of the comments
[–] zimzat@kbin.social 1 points 2 years ago

The reactivity of Svelte leaves a lot to be desired. The only difference between a computed property and a mutable property is let x = and $: x =, both of which are declared in the same top-level scope and doesn't provide much to distinguish them. The lack of reactivity on arrays and objects is a major foot-gun by default. The number of places they say "this looks weird, but don't worry it'll soon become second nature" in the docs shows that they acknowledge it's bad design to create code that is misleading or goes against the grain/standard for what behavior developers should expect (makes it confusing to work with and then use anything else, or vice versa).

The #await template directive is interesting; I'm not sure I agree it should be handled in the template instead of the script but if combined it would remove some boilerplate loading = true/false and error = 'message' variables from script scope.