mrkcsc

6 ms·

1.
by mrkcsc 4mo ago
OK but thats simply doesn't perform. You can't say "only rendering what is visible should be handled by the browser" and call that a solution unless you have a magic wand to make Chrome/other browsers do this. The b
2.
by mrkcsc 4mo ago
> I feel like virtualization is not the right way to handle things. How would you handle it?
3.
by mrkcsc 4mo ago
Optimizing for the P95/99 case of performance typically makes everything better as a whole.
4.
by mrkcsc 4mo ago
What are you even talking about, this post is about rendering code diffs in the context of the web. Whether or not it would be "trivial" in a native terminal application is irrelevant.
5.
by mrkcsc 6y ago
We called them servers because our early adopters were coming from Ventrillo and Teamspeak (eg: Vent server, Teamspeak server, etc) and we wanted to use familiar terminology.
6.
by mrkcsc 7y ago
Our core team - and indeed our original team - were native developers not React JS ones. We chose React Native because it was a pragmatic choice and the best tool for our situation. As our startup gained traction and we decided to build mo
7.
by mrkcsc 7y ago
Blog author here - this is correct (mostly Kotlin :) This is primarily an artifact of history for us. When we first set out to build the mobile apps, React Native for Android had not yet been open sourced so we had no choice but to build i
8.
by mrkcsc 7y ago
Thank you for the kind words!
9.
by mrkcsc 7y ago
The strongest RN teams and engineers I've seen tend to be those that either already have or are willing to acquire knowledge about how native app development works under the hood. It greatly augments your ability to write elegant solut
10.
by mrkcsc 7y ago
Thanks for the read, and the support!
11.
by mrkcsc 7y ago
I've made many native apps (including our own native Android app) and performance issues are definitely still a thing with native code :P The amount of work was non-trivial, however, in absolute time it was a few weeks of work that we
12.
by mrkcsc 7y ago
Blog author here. As a native app developer, I would say that the trade off is similar to developing an app on native Android vs. native iOS. You inevitably must solve problems on Android that iOS has not yet solved (or are trivially easy
13.
by mrkcsc 8y ago
Thats true, I appreciate the discussion and the clarification.
14.
by mrkcsc 8y ago
Well it’s been three years so far - we shall see :P I know this comment is a joke but in all seriousness even if we did move away I think it would still mean we got several years of great utility out of the framework. No tech lasts forever
15.
by mrkcsc 8y ago
Based on our experience yes I would certainly consider doing the Android side in React Native starting today. While the performance footprint is mostly the same - the ecosystem and feature set around it has improved a ton to the point where
16.
by mrkcsc 8y ago
Thank you! :)
17.
by mrkcsc 8y ago
It's been discussed a lot internally - I would love to gift Nitro to folks myself ala Reddit Gold :) I believe it's something we may eventually take on - just not currently planned - there are a lot of ways we could make the nitro
18.
by mrkcsc 8y ago
It's a valid point :) that probably wasn't the best example - although it would likely be quite a journey to somehow ship the forked support library. Native iOS would have been a better example as that code is not open source at a
19.
by mrkcsc 8y ago
Thats really cool :D I think getting it to the point where it's not just occasionally synced is really helpful for upstreaming contributions and bug fixes.
20.
by mrkcsc 8y ago
It's not about cost, it's about impact. The team - myself included - works normal eight hour days and there is no "crunch time" (other than very rarely when we have external dependencies like when we launched our Spotify
21.
by mrkcsc 8y ago
Not an expect but as I understand it the Windows API for idle tracking is sometimes wonky. Certain programs can keep your computer in a non-idle state indefinitely even if you don't move the mouse.
22.
by mrkcsc 8y ago
We are actually starting work on allowing pasting images from the clipboard this week :D So stay tuned! Thanks for the kind words, the team really appreciates it.
23.
by mrkcsc 8y ago
To be fair though this exists in Native land too :P but it's sometimes even worse. EG: In Android in the past there have been bugs in core components like the `RecyclerView` (thing that renders lists) that forced us to downgrade and un
24.
by mrkcsc 8y ago
The iOS application can safely pull data and perform actions from just about every Store (we don't use redux but the idea is the same https://redux.js.org/api-reference/store ) and Action Handler ( https:/&#x2
25.
by mrkcsc 8y ago
* Mentioned in another comment, but generally the performance of animations was poor with mixed in with any other kind of UI rendering - particularly on older phones (when we prototyped iOS we really only focused on the latest two generatio
26.
by mrkcsc 8y ago
I'd suggest reaching out to our CX team (support@discordapp.com) - we really do care and you will get a reply :) I'm not an expect on voice but iirc we do use a different codec than Skype so the audio is not going to be identical
27.
by mrkcsc 8y ago
It's less that it's bad (in my opinion) and more that on Android you have a much wider range of hardware to support ranging from quite new and recent, to basically ancient almost flip phone level. I am hoping that in the future
28.
by mrkcsc 8y ago
The core Android team is four engineers so about double in size. This makes some sense since on Android we have to re-write most of the stores/business logic and not just UI. We have modeled the architecture similarly to things on the
29.
by mrkcsc 8y ago
Sure, When we originally got it running on Android (without the chat view since that component is native in the iOS app) we found that it performed quite poorly due to most of our pages being heavy on data and UI - as well as being very rea
30.
by mrkcsc 8y ago
Hi all, Discord engineer here! If anyone has any questions about the post or our experience using React/React Native the team would be happy to answer them!

More ›