After getting tired of scrolling (which reminded me of this <a href="http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.html" rel="nofollow">http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h...</a> where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings!<p>Unfortunately, the page outsmarted me and as I zoomed out, it somehow figured out I was doing this and increased the font size so it's the same size it was at 72 points when I was at 100% zoom.<p>Well, all right web designer. You "win". The amount of effort you put into defeating my efforts to read your content is astounding.
Alright so looking at the comments we've got one person complaining about the naming of the framework, one person complaining about the argument of sexism surrounding the use of the word "guys" in a gender-neutral context, one person complaining about the UI of the blog itself, and one meetup recommendation. (And now we have one comment complaining about the other comments, BINGO!) Nice work HN!<p>James, thanks for the informative talks - I hope we can continue to push the bounds of React Native and succeed in making it an obvious choice for developers in the future. For anyone who hasn't tried it, I highly recommend giving it a shot for any new app you work on. There's a lack of Android support at the moment (it is about 5 months from release I believe), but at the very least you'll speed up your iOS development significantly. It's hard to justify native development now (for me, as a non-iOS dev) when you can, for example, create a camera view in React Native with a single line of code.
For people in SF, running similar meetup in the city as well<p><a href="https://www.meetup.com/SF-React-Native-Meetup/" rel="nofollow">https://www.meetup.com/SF-React-Native-Meetup/</a>
I just wish people and companies would get over this "react(ive)" naming fetish. It reminds me of back in the late 90's when everything was Web-this and Web-that. It makes the distinctions really hard to google for. React, reactive, functional-reactive, etc. Overloading gets in the way of learning and progress.
Yesterday I read about NativeScript, which also seems to be a nice way to do this kind of stuff.<p>They also seem to support native libs.<p><a href="https://www.nativescript.org/" rel="nofollow">https://www.nativescript.org/</a>
> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people"<p>As a non-native speaker, isn't "guys" a correct term regardless of the gender?