News for hackers. Stuff that matters.
Re:How Discord achieves native iOS performance with React Na... by rsynnott on Friday November 08, 2019 @05:28AM (#21481118)
> I know that maintaining two separate code bases for iOS and Android is theoretically bad

I'm not sure _why_ this should be theoretically bad. It depends what you're going for, of course, but cross-platform GUIs are typically... not good. There's a lot to be said for separate GUIs with shared business logic IMO.

Re:How Discord achieves native iOS performance with React Na... by ericlewis on Friday November 08, 2019 @08:26AM (#21481941)
It’s theoretically bad because you’re theoretically wasting your time and resources. In practice that doesn’t have to be true. But I merged two teams together via react-native in hopes to make them more productive and it absolutely worked.

Android is no longer a laggard with features, which was also a big goal of ours.

That said, if I were to go back and time and know how much of my own time would be spent fixing bugs in react-native just to keep the team productive, I might have made a different choice.

Edit: should also be known that I’m no longer helping with fixing RN bugs, and the team still messages me on occasion to ask questions or for help to fix things. This was absolutely not the position I was trying to leave that team in.

Edit edit: my leaving the team wasn’t within my control and management didn’t realize the level of work to Keep the Lights On nor did the particularly care.