Viewing profile — mrkcsc

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 C…

> I feel like virtualization is not the right way to handle things. How would you handle it?

Optimizing for the P95/99 case of performance typically makes everything better as a whole.

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 irrelev…

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.

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…

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 n…

Thank you for the kind words!

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. …

Thanks for the read, and the support!

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, howeve…

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 …

Thats true, I appreciate the discussion and the clarification.

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 o…

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…

Thank you! :)

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…

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 b…

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.

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 depend…

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'…

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.

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…

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…

* 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 proto…