HACKER Q&A
📣 rcarr

Given its tech stack, why Mastodon?


So I spent the evening looking at what super simple blog applications were out there now (e.g Blot, Bear, if you know any similar give me a shout) and also started looking at all the microblogging options available (micro.blog, mastodon, pleroma etc). This lined up quite nicely given tonight's events and decided that running my own single user mastodon instance might be a good idea. I then started reading up on a comparison of mastodon and pleroma and how lightweight the latter is in comparison to mastodon which made me read up on mastodon's architecture some more. So my questions are as follows:

- How does Pleroma's language and architecture achieve feature parity with Mastodon without the resource consumption? Are tradeoffs being made or is the Phoenix and Erlang language and tools just that much better than Ruby on Rails?

- Why was Ruby on Rails selected for Mastodon and how has Mastodon become the most popular fediverse offering whilst running on 'old' web tech given that the early adopters were presumably very tech orientated people? Should we not be pushing for the 'next big thing' to be in Rust or Go or something else that's fast and performant?


  👤 al2o3cr Accepted Answer ✓

    Why was Ruby on Rails selected for Mastodon
Perhaps the _one person_ who did the initial development back in 2016 preferred it? Not all technical decisions have deep foundations.

    how has Mastodon become the most popular fediverse
    offering whilst running on 'old' web tech
Imagine how utterly fucked it would be if it had been built using one of 2016's "new" web techs - maybe a Backbone + Mongo setup :P

👤 gregjor
Because "tech stack" has almost nothing to do with the utility or popularity of a tool or product. It could have COBOL at the core, if people find it useful they won't care.

👤 __d
For a lightweight self-hosted instance, I like https://codeberg.org/grunfink/snac2 -- far simpler than most (all?) other options.