#Swift can be so much cleaner and more concise than #ObjectiveC. Really digging the new concurrency syntax with #ASync and #await for working with #CloudKit. Now if only I could convert my entire project to this. But 16 years of development has lots of legacy code. But I am slowly modernizing some of it and writing new stuff in Swift and SwiftUI.
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.
I like that you chose Sveltekit, and the project structure seems pretty good. But there's a lot to fix. The page load takes way too long (you should be using #await whenever possible), and the design is very messy.
If I may suggest, I think you should be using a better UI framework. I feel like Carbon is a good match for this sort of app. But If you don't like it, Skeleton also seems like a good choice.
Also, imho you should be using display: flex a lot more! (or grid). And use tab 2 or 4, not 8!! :)
Either way, I like the initiative. I might be able to help out a little bit here and there, but I can't make any promises.
My coding style has always been to get out the core functionality then fix everything up, definitely not for everyone. Might be something I need to reconsider when working with others.
I love carbon, but I chose Ionic is because its very suited for mobile development. On the other hand it seems to have very severe limitations for mobile so it seems I have to pull in something else in as well.
The page load takes way too long (you should be using #await whenever possible)
I will, though part of the reason its slow is because its hitting lemmys backend over the network, as opposed to just a local network in a normal setup.
Kev Quirk, one of the admins of Fosstodon (a Mastodon instance), destroys Meta in an email exchange. (fosstodon.org)
The exchange is about Meta's upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!
Just an idea (lemmy.world)