AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Discord vs slack company9/26/2023 Discord's sound quality is also much better, and there are all kinds of options Slack lacks. It's important for audio chats to have very little lag in that context, and Discord delivers-Slack, meanwhile, is lacking on that front. Gamers left the service running in the background on their computers, so they could talk to each other while playing online games. Audio channels are what Discord built its reputation around. How much more do I really need to say? Audio and video calls simply aren't Slack's strengths.ĭiscord, however, excels on the AV front. Slack just has more polish, and that gives it an edge in this category. This isn't to say that Discord is unusable. There's just more attention to detail on Slack when it comes to text chat. ![]() One of my most read articles is about how to bold on Discord because Discord doesn't do anything to help people learn how its formatting works. Slack has all kinds of little chat touches that Discord lacks. Slack, in this way, works better for quickly sharing files. Slack's free version limits users to 5 gigabytes (GB) of free storage overall, with no limit on individual file size. Discord users can't upload files larger than 8 megabytes (MB) on the free version (or 100MB if they're paid users). Slack users can upload an unlimited number of custom emoji, even on the free version Discord servers are limited to 50 custom emoji.Īnd it's not just text-this extends to other features. Slack lets you organize your sidebar using folders Discord only allows this to happen at the server level, so individual users can't customize their own sidebars. Slack offers a Mentions & reactions view, allowing you to see conversations that mention you and emoji reactions to your posts in one place Discord offers an Inbox with mentions, but no way to monitor emoji reactions. Slack lets users privately save posts for future reference Discord doesn't. But there are still a lot of small quality-of-life things that Slack does just a little bit better. Both Slack and Discord clearly have this in mind, but Slack seems just a bit more focused on keeping things organized-particularly if you're working on a large team.ĭiscord has been catching up on this lately-adding threads is a big step. And that's true, but put a bunch of people in a chat room, and things get disorganized quickly. You type something, you press enter, then your team can see it. Slack does text chat better, especially for work Let's break those down and talk about what makes sense to use in which contexts. They have different strengths and weaknesses, which reflect their designers' priorities. There is overlap.īut these apps aren't entirely interchangeable. There are plenty of online communities that happen on Slack, and some people use Discord for business. The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.So, I understand why people might think these apps are interchangeable-to an extent, they are. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over. All this happens automatically and makes it really easy for developers to get code onto servers quickly. An upgrade-operator process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). Helm plays a central role when deploying our staging apps into the cluster. This allows our engineering team to iterate quickly and safely test code in a full production environment. ![]() We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. ![]() We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. I will dive into the history and reasons for this in a future blog post. However, as our team grew and our product matured, our needs have outgrown Heroku. We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc.
0 Comments
Read More
Leave a Reply. |