They are already if you architect your service for the real purpose, which is to store and process ActivityPub data. Mastodon however is a CRUD application that has its ActivityPub bolted on a totally different data paradigm. It takes a lot of computing to make it run fast.

I created an ActivityPub service which (coincidentally) uses a similar storage idea as HN - raw files on disk - and it runs orders of magnitude faster than a similar sized Mastodon server would. Sadly it's not as fast as HN, but I'm getting it there. :D

I think the person you are replying to was being sarcastic.

they were, but the point was that mastadon is incredibly inefficient and this guy is making a more efficient version

I see your profile is full of a lot of the info about this, do you have a more detailed write-up expanding on how this all works together?

There is some documentation about various things[1], but I'm not entirely sure what you mean about "how it all works together".

[1] https://man.sr.ht/~mariusor/go-activitypub/