During this meetup we discussed React Native. We are a group of developers in the midst of language changes. A few members of the group are hard-core Objective C developers. And the Swift developers are trying to get them to jump ship. Being able to talk about something other than the rift between objc and swift is nice.
To prepare for this talk I went through the tutorial on the React Native website. It was fairly straightforward except for 2 things:
- I broke my version of homebrew installed on my machine. Had to find an uninstall script. Uninstalled and reinstalled homebrew.
- Installed Node with Homebrew. Old symlinks persisted from the previous install. Googled and reset the symlinks properly.
- Installed React Native and got registration errors on Android build. iOS build worked fine.
After going through all this fixing to get set up. I just didn’t have the time or the steam to continue working on updating the starter project. I was happy to have the project installed, proving to myself that this was possible with my laptop and setup.
So I showed my progress with the group. Our brains instantly saw the benefits of working on one code base to export to multiple devices. However, as the dependencies streamed down the console as the project was building for iOS, we all came to the same conclusion.
In business work, React Native is just too brittle. Disagree with me? That’s fine.
This week we’re building a 2d boxcar with SKSpriteNode and physics. I was so eager to get started, I made my first car and posted it as a repo on the Hawaii iOS Developer Meetup Github org page.
If you’re interested in attending the meetup this week, please RSVP here.