@thisismissem @fedify Yeah, I saw that post and fedify's response (with the benchmarks). Those figures look better. Not using a queue is basically like sending someone a message, then doing nothing until they respond, and going on with your day only after they did (if I understand it correctly)... But still I'm not too fond of writing backends in JS. But you are right, these things aren't computationally intensive, so maybe peformance doesn't matter as much.
Posts
-
This article on Web Components by @leaverou nicely encapsulates a fair few of my feelings about where we are at with ActivityPub / ActivityStreams in the standards process: -
This article on Web Components by @leaverou nicely encapsulates a fair few of my feelings about where we are at with ActivityPub / ActivityStreams in the standards process:@thisismissem Yeah I think if ActivityPub was less of a hassle people would code for and thus eventually use more fedi apps. Which is why I think @fedify is a good thing but I am currently turned off by their performance, as happens with JS. But let's be real, Ruby on Rails is no performance powerhouse either...