Timeline of Slack’s Tech Stack Evolution • Hacker News Board

Re: Timeline of Slack’s Tech Stack Evolution

#51

Post by namelosw » Sat, Jun 22, 2019, 5:46 AM UTC

acemarke wrote: post #49

namelosw wrote: post #41

It's interesting to compare Slack's tech stack vs Discord. The tech stack of slack is pretty common, while the tech stack of Discord is very geeky: Elixir/Rust + Cassandra for crazy high concurrency, and React/React Native for fast developing and consistent experience. Like LAMP for Slack, Discord also used MongoDB prototyping in the first few years, but while they prototyping they prototype in a manner they can easi…

I'm an admin on Reactiflux (although at the time of the switch from Slack to Discord, I had just joined as a newbie). We got kicked off Slack because we got up towards 10K users signed up, and Slack locked us from having any more people join. Clearly, we weren't a good fit for their business model. Worked out well for us - we've loved Discord ever since we switched over!

This is So cool! Reatiflux is one of the most energetic community I have ever seen.

Every time I use Slack I found the business model is not as generous as Elixir - there are too many constraints for free users/organizations.

Re: Timeline of Slack’s Tech Stack Evolution

#52

Post by sercand » Sat, Jun 22, 2019, 6:05 AM UTC

sys_64738 wrote: post #45

The Slack client is a terrible memory hog in my experience. I can't believe they need to use Electron instead of the platform native FWs.

I hope they port their iOS app to Mac with Catalyst. It might solve the issue at least for the Mac users.

Re: Timeline of Slack’s Tech Stack Evolution

#53

Post by slezakattack » Mon, Jun 24, 2019, 9:29 PM UTC

skinnymuch wrote: post #48

slezakattack wrote: post #9

I'm curious if Slack ever considered using XMPP in their stack for core chat? As an outsider, it seems XMPP would fit like a glove (even signing in to a work "domain" screams XMPP).

What would be the advantages now that they already have the product built?

I'm simply curious if the protocol was ever brought up in discussion and if there was a conscious decision to not go that route due to product needs.

I'm not going to speculate on what the advantages/disadvantages would have been as I honestly have no idea. I suppose if a competing product comes out that is XMPP-based then maybe we'll have some good comparisons. ;-)