4 ms·

I hate a lot of Electron and React Native based software, but Discord manages to avoid performance, stability, and quality issues that most seem to encounter. I

by jrsj 4y ago

I hate a lot of Electron and React Native based software, but Discord manages to avoid performance, stability, and quality issues that most seem to encounter. I don't know what they do or how they do it, but I think it's very impressive.

deleted 4y ago
[deleted]
deleted 4y ago
[deleted]
volumetric 4y ago
We used it a lot over the pandemic and random crashes and having to restart because it started using way too many system resources was extremely common. Nobody left it open when not in active use, because it was such a resource hog. Using it on battery would take a macbook from full to 0% in like two hours flat. This was with a couple very small private groups only, no use of large public channels or anything.
- nabakin 4y ago
  Strange, I've never had that happen and I've used discord for years. A good portion of that time was spent using it on my 2015 MacBook Pro.
  - tazard 4y ago
    I had lots of issues on my M1 Mac, mostly it was solved by running their beta version though. No issues on any other platforms
baisq 4y ago
The desktop client is, to me, not as performant as it should be. Many actions take several hundred milliseconds when it's obvious that they could be much faster.
bravetraveler 4y ago
I have to assume it's partly because they never update Electron -- I've not been able to run it under Wayland for a few months now
- RobbieGM 4y ago
  --ozone-platform=WAYLAND ?
  - bravetraveler 4y ago
    That is indeed how I would enable it, but it stopped working! I get this: interface 'wl_output' has no event 4
DanielHB 4y ago
it is because they are not afraid to drop to native when it makes sense, see: https://discord.com/blog/why-discord-is-sticking-with-react-native https://discord.com/blog/why-discord-is-sticking-with-react-... react-native is NOT a total replacement for native code, you still need native devs. It is more like instead of 5 ios and 5 android devs you need 4 JS, 1 android and 1 ios devs (but the ios and android persons also need to know JS)

by jrsj 4y ago

deleted 4y ago

[deleted]

deleted 4y ago

[deleted]

volumetric 4y ago

We used it a lot over the pandemic and random crashes and having to restart because it started using way too many system resources was extremely common. Nobody left it open when not in active use, because it was such a resource hog. Using it on battery would take a macbook from full to 0% in like two hours flat. This was with a couple very small private groups only, no use of large public channels or anything.

nabakin 4y ago
Strange, I've never had that happen and I've used discord for years. A good portion of that time was spent using it on my 2015 MacBook Pro.
- tazard 4y ago
  I had lots of issues on my M1 Mac, mostly it was solved by running their beta version though. No issues on any other platforms

baisq 4y ago

The desktop client is, to me, not as performant as it should be. Many actions take several hundred milliseconds when it's obvious that they could be much faster.

bravetraveler 4y ago

I have to assume it's partly because they never update Electron -- I've not been able to run it under Wayland for a few months now

RobbieGM 4y ago
--ozone-platform=WAYLAND ?
- bravetraveler 4y ago
  That is indeed how I would enable it, but it stopped working! I get this: interface 'wl_output' has no event 4

DanielHB 4y ago

it is because they are not afraid to drop to native when it makes sense, see: https://discord.com/blog/why-discord-is-sticking-with-react-native https://discord.com/blog/why-discord-is-sticking-with-react-... react-native is NOT a total replacement for native code, you still need native devs. It is more like instead of 5 ios and 5 android devs you need 4 JS, 1 android and 1 ios devs (but the ios and android persons also need to know JS)