realize you're still caught in the hamster wheel of capitalism and all you did is moot
38 karma · joined August 22, 2012
Having said that, Mario Kart 8 is really a good choice (despite it being 3D): * it almost drives itself in 50cc cups * it has 4 types of cups, which gradually get harder * it's great fun alone and in coop * it has great challenges: win the cup/ win all races
if it's not about co-op, but about letting your kid drive and _you_ sitting in the passenger seat, i can highly recommend the titles from https://www.humongous.com/games They are like interactive cartoons with some mini games thrown in. Basically old school point and click adventures for kids.
how does react provide an interface for ajax? react does literally no calls at all...
I feel like 50% of the people complaining in this thread have never touched react or their last interaction with frontend code was jquery 15 years ago and they're still carrying those learned paradigms around and applying them to every new framework/ frontend lib they come across
Would be nice to know where you get your information from, that RN isn't core to Meta
> - In the end, RN code is only something like 20% of our Android app. They weren't able to just "write once" and run on both.
That has nothing to do with RN, that's on your company
> - Instead of having 2 teams, an iOS and Android, now we have 3 teams, iOS native, Android native, and RN. And the RN team is split between iOS and Android. All sorts of additional complexity now.
Again, your company/ mgmt. We shared code between iOS and Android and had zero native module maintenance.
> - We still need a fully staffed Android specific team for everything that couldn't be done in RN.
which was what exactly?
> - The performance difference vs. a native app is blatantly obvious.
The majority of apps within the app store could've been written in RN and you wouldn't know/ notice. Discords iOS App is written in RN and I bet a huge amount of commenters here wouldn't have know without reading the article.