Discord is just really crappily optimized, can't even do a voice call when I can do full video calls on hangouts instead... Let's also not forget how if your connection is even a tiny bit slow a loading screen pops up that deletes anything you were typing you didn't send and just leaves you stuck there, not even able to read messages, even though you can load other sites fine:/
I aggree. How is that possible that a shitty underpowered 3DS has no problem running a Discord client, yet an overpowered overclocked super expensive PC has problems trying to upload a simple image or just send a fucking four letter message in the next 30 seconds. This is getting out of hand, and will soon be worse than Skype if this goes on...
With Java having such amazing documentation in older books, it's pathetic to see people not knowing how to write proper code with it. Sure, sometimes it can be tricky, but what language doesn't do that? As for Javascript, I've mostly seen "competent"/"acceptable" bad, except in 2 cases where it was so bad loading a page instantly started memory leaks on the browser...
This is basically a rant of sorts since I use Discord way too much and don't like certain aspects of it, sorry for all the text but I didnt want to cut anything and character limits suck.
I was going to throw this in several messages but dear lord that would be so many messages, so have at you - https://hastebin.com/raw/yituyogobo (Copy paste into your favourite editor to see it in less cancerous font/display)
Actually, it's not WebSocket's fault; it's more like the frontend devs have no fucking idea how to design networking code. Same goes for the Android client, but it seems like recently the Android client has been getting some attention.
Neverthless, you're decompressing huge chunks of data in an interpreted VM, no wonder the CPU usage is shit.