ctrl+f "ads" ctrl+f "monetization" ctrl+f "moderation" ctrl+f "existing infrastructure" ctrl+f "personalization" etc etc Yeah about what I expect from a "we rebuilt twitter for cheap" post. There's no point to the comparisons with the Twitter codebase size/cost. It completely distracts from what is probably a perfectly fine project.
We reduced the cost of building Mastodon at Twitter-scale by 100x
101–110 of 376 posts
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#102Earlier quoted context omitted.
We're actually not asking anyone to give up anything. First off, it has a simple integration API (which you'll be able to see the details of next week) that allows it to seamlessly integrate with any other backend tool (databases, monitoring systems, queues, etc.). So Rama can be incrementally introduced into any existing architecture. Second, Rama has a pure Java API and is not a bespoke language. So no new language…
So Rama-powered apps need to be written in Java? Or will any JVM language work? And the Rama core will remain closed-source? That part seems like the toughest sell of all, at a time when the vast majority of developer tooling and backends are open source or at the very least source-available.
We're keeping it closed-source for now.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#103Earlier quoted context omitted.
> Second, Rama has a pure Java API and is not a bespoke language. So no new language needs to be learned. Isn't Mastodon a Ruby On Rails application?
The article says they re-wrote Mastodon from scratch (probably the backend piece). I'm guessing in Java.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#104I would argue that this is not "a Mastodon instance", since it is not running Mastodon - other than that, very very neat work! I'm excited for that "Source Code" link to be live :)
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#105Noticeably missing are any details about concurrency control and replication or recovery protocols. A Twitter clone is one thing but any sort of application needing ACID Transactions is a whole other beast.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#106"We spent nine person-months building our scalable Mastodon instance. " Nono, you can't say that when later on you say it's built on top of Rama. You literally spent 10 years building the framework to even make this. And yes, you built this in 10k lines of code but how many lines of code is Rama? This seems disingenuous.
They had to invent the computer first, and before that they had to create a universe capable of sustaining both life and computers.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#107> The instance has 100M bots posting 3,500 times per second at 403 average fanout to demonstrate its scale. Mastodon has to send messages to each instance with a recipient. That server can then fan out to all it's subscribers. The way this point is worded makes me think all the bits are on just a single instance, meaning all the fan out can be dealt with internally without having to do any server-to-server at all. Th…
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#108It's not so much that I think the comment is wrong or anything, but rather that it seems so similar to what I have heard in the past from power-lisp (or Clojure in this case) super-smart engineers.
I feel like we have reached a point in software development where "better" paradigms don't necessarily gain much adoption. But if Rama wins in the marketplace, that will be interesting. And I am quite excited to see what a smart tech leader and good team have been able to grind out given a years-long timeframe in this programming platform space . . .
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#109Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#110Their big reveal after 10 years is "keep waiting". Move along, nothing to see here.