it's harder to make something interop, it's harder for users because they need to pick between things instead of just using the one same thing everyone else uses.

with the bluesky approach you have a form of decentralisation while also benefiting from centralisation.

i feel like at the end of the day centralised services provide the best most consistent experience for everyone involved.

for example, on mastodon, if you like a post that like will be stored on the instance you left the like on.

decentralisation is extra complexity for everyone involved.

casual

and they all complain about each other. it's so tribal and primal, it's really funny and sad to me.
i have literally no hope in social media.

100% agree. it feels so weird to me how no one sees that bluesky is a lot like twitter and mirrors some of the issues. i agree that bluesky is better as a platform itself but the actual users themselves are super annoying regardless of what you use lol. they're like sidegrades of each other

question: you say that it's like a progressive enhancement thing where the comments don't work without javascript. but why does it need client side javascript in the first place? can't it just get ssred without any client side javascript?

Jakiter eating trans ice cream that makes you trans:

i needed the font to make it be as accurate as possible. i ended up using garamond italic, rendering it at 15px, and then resizing it with near neighbour to get it to have that kind of pixely look, then i tilted it out a bit additionally with this result.
I know it's not the same font and that's sad

I really appreciate the commitment to pixel correctness.

Correct rendering doesn't seem to be the top priority for most rust gui libraries and it's really disappointing, someone needs to get them in front of a 1024x768 screen so they can see what they have done.

( Amazing release btw ❤️❤️❤️ )

Waiter! Waiter! More PS1 styled horror games!

besides that this looks really good, great job

apple liquid glass design system

[1] - web-frameworks-benchmark.netlify.app/result?f=fas...

I find it to be pretty hard to estimate just how good or fast swift is as a language considering all of this stuff.

Feel free to nitpick this thread because I'm not an expert but personally, I'd let it sit and cook in the oven for a bit.

I like the language itself but.. idk about everything else.

benchmarks show anything realistic (considering the fact the nodejs examples use node magic to run the frameworks in parallel on all cores which is usually not something people tend to do in javascript) but honestly I find it to be pretty dissapointing.

an empty space and also get out an id with a router, I would expect a language with "incredible performance" to perform a little bit better.

It's not that these numbers are bad or anything, and I have absolutely nothing against the developers of either framework, nor do I think that these

In addition to this i would like to complain that in synthetic benchmarks[1] all swift frameworks lose out to heck of a lot of other different frameworks even the ones using nodejs.

I understand that these numbers are still pretty good, but considering all this benchmark does is basically return

If we build the same project with release mode, thin lto and the static linux swift sdk we get a whopping 176 MB binary, (63MB stripped).