Re:How Discord achieves native iOS performance with React Na...
by madeofpalk on Friday November 08, 2019 @08:46AM
(#21482073)
> no Electron bullshit
Electron is a UI 'framework', so bringing it up is kind of a non sequitur. Your approach of a C++ core is entirely compatible with an Electron UI.
I worked on a project that had its 'core logic' implemented in C++, which we then ran that on the web in Javascript, for the same portability reasons.
Re:How Discord achieves native iOS performance with React Na...
by bsaul on Friday November 08, 2019 @08:20AM
(#21481911)
how did the java interop work for you ? I used to work in a company that used that approach with gomobile (golang) , and frankly the dark magic required to have a decent java API to the shared library made me want to not touch that with a ten foot pole.
I believe it was due to JNI but my memories may be wrong.
Re:How Discord achieves native iOS performance with React Na...
by Aissen on Friday November 08, 2019 @01:04PM
(#21484952)
The answer is in the parent's comment. They used protobufs, so I guess there's no JNI, just a simple RPC over a local socket.
Re:How Discord achieves native iOS performance with React Na...
by bsaul on Friday November 08, 2019 @04:02PM
(#21486702)
Thanks, i completely missed that part. Very interesting solution...
Re:How Discord achieves native iOS performance with React Na...
by izacus on Friday November 08, 2019 @04:17PM
(#21486880)
We used Dropbox' Djinni for a long while and it was good for most cases, but there were performance limitations - we switched to protobuffs over byte[] arrays for complex data later.
Re:How Discord achieves native iOS performance with React Na...
by alien1993 on Friday November 08, 2019 @06:28AM
(#21481377)
How do you achieve this? Are you using some framework like Qt? Or is it custom?
Re:How Discord achieves native iOS performance with React Na...
by izacus on Friday November 08, 2019 @06:47AM
(#21481430)
As the previous poster mentioned, the UI is all native and written separately for each platform. To populate UI elements you call native calls so there's no UI framework like Qt needed.
We used C++14 which has a pretty good standard library and plugged the holes with some parts of Boost and then standalone libraries like SQLite, json11 and others to provide missing functionality.
- It forces you to think about your business logic vs. UI structure.
- It forces you to make your core logic library easily testable.
- Since you can deploy the core logic library anywhere, you get native, no Electron bullshit, support for pretty much all major operating systems at a cost of running a CI on all compilers to catch non-portable parts of C++ quickly.
- The users get UI that's built for their platform with it's own quirks and doesn't burn 500MB of RAM.
- Using a serializable and portable message standard (we opted for Protobufs) to communicate between logic library and UI part makes deployment to server easy as well.
Biggest issues?
- Getting inflexible people to learn anything other than JavaScript.
- Getting slow compile times under control.
- Getting CI coverage to the point where it catches developers accidentally adding Apple or Linux specific headers into codebase.
- Learning to be conservative enough to not trust the platform and ship our own libraries. Even basic ones like SQLite.