Right, but as of May 2018: 130 million unique users. Billions of messages sent every month. That doesn't sound like easy peasy. You are not looking at the big picture.
Even a billion messages per day is a mere 11k requests per second and keep in mind that WebSockets is far lighter weight than HTTP. Any server that can't handle 11k requests per second shouldn't be called a server.
And if you read the article, they did weigh the option of compression, but they weren't terribly concerned. Compression can reduce the size of messages by a factor of ten.
As far as Discord is concerned, I believe they use a mix of Go, C++, Elixir, Erlang, Python, C and JavaScript. There are probably more I missed, they use a lot of languages, they have some pretty good developers.
The reason Facebook has a ridiculous number of servers is because of PHP (getting phased out) and machine learning. They love feeding your data through their algorithms to see what they can find, they would never settle for being a mere intermediary.
I wouldn't sneeze at Discord's budget for servers, but it's nowhere as bad as you think it is.
Adding more programmers isn't really a solution, programmers are expensive and existing programmers would have to bring them up to speed.
That said, Discord seems fairly unconcerned about performance, it takes many, many months before they really deal with performance problems staring them in the face.