Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> It uses 156 megabytes of memory even on this high-volume scenario, so I would say that while baseline performance is low, it doesn't get slower, which is good.

no ! it's not good ! this mindset is why everything sucks :( at no point one should have to accept that "baseline performance is low" for a software developed by a multi-hundred-million-dollar company that was almost bought by MS for a few billions



I agree in principle, but I find the program extremely useful and the performance is totally acceptable for my use-case.

I want a chat program that is: - Tolerable to use - Does not require, incessant fiddling to get to work right (it's OK if it could allow so to get it to work even better) - Has some sort of rich-text formatting - Good, low-latency voice - Tolerable video or screen sharing - I can onboard people easily - Is group-oriented, not 1-to-1-oriented - Bonus points if it has reasonable moderation tools for guests or similar

If not for Discord, I would be using something like Slack (which somehow manages to have concurrency issues when typing and some jank occurs, uses 3x the memory, and does not scale nearly as well for multiple workspaces), TeamSpeak (which has very obscure UX, requires self-hosting, and doesn't provide a reasonable rich-text-chat), Matrix (I have to either pick an equally-bloated Electron client or one of the many incomplete native clients), or something else.

The fact is that raw performance itself is rather low in my list of priorities, as long as it a) doesn't stop my train of thought and b) does not overburden my system unnecessarily when idle.

As you can see all of that is very much subjective, I'm not saying you are wrong to demand utmost performance. I also try to strive for it in the programs I write, but when consuming I prioritize stability and features.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: