1,464 karma · joined August 28, 2012
Co-founder of https://productpains.com
But back then internal adoption of React Native was definitely accelerating rapidly and it was solving very real organizational and developer experience problems. The original motivation of the project internally was to solve developer experience pains, just like React but for mobile.
- With such a large app (Facebook), the compile cycle was becoming quite slow. RN has no compile cycle.
- You've got 3 teams (web, iOS, Android) per product (eg. Events, Groups, etc) and they don't really communicate or share any product code despite building effectively the same thing.
Take the Mobile Ads Manager app: Now one team (of web engineers) can ship an app on iOS and Android, while sharing 83% of the code between each app, in half the time the project had budgeted for just the iOS pure native app. Not to mention the team constantly loved their jobs because they didn't have to wait 5 minutes for the damn thing to compile every time they made a change.
Which part of "equivalent" did you miss?
You're entirely missing the point. This isn't about product experiences whatsoever. You can ship equivalently delightful experiences in React Native as you can in pure native apps. The point of React Native isn't to make your app more delightful.
The point is to develop it faster, in a more enjoyable manner, and enable one product team to develop for multiple platforms. This is an incredible win organizationally and for developer experience.
> Steve Jobs would have me fired
Check your ego.
The point is to create the equivalent experience of a native app with a delightful development and organizational experience.
- Instead of having separate teams develop your iOS, Android, and now OS X apps, one product team can make all three and share the majority of the code.
- Instead of a slow frustrating compile cycle you get live reloading.
What are some actions people like myself can take to push our community, nation, and world towards Basic Income?
This is particularly important to me because of how fast Uber/Tesla are rushing towards fully autonomous vehicles. Over 4 million jobs in US alone are as drivers. They're all gonna be laid off soon.
I work on a semi-relevant project called Product Pains where people can post and vote on product feedback publicly about any app or website. After seeing this thread, I posted this feedback about HN: https://productpains.com/post/hacker-news/make-comments-coll...
The idea is that a lot of votes on a piece of feedback creates a social responsibility for the team to respond and ideally implement the feature. We're still in early stages but consider voting on this and/or posting other feedback for HN. They could definitely use it. :)
This is pretty interesting to me. I wonder if the press is just blowing things out of proportion, or if there's some Big Money™ behind this so that investors can convince companies to agree to worse terms.
You're making an assumption that with YC your company would be worth $10m+ and without, $100k. That assumption isn't really valid to me.
The value you get out of YC isn't really the money.
7% is a lot.
Some are very sensitive to sexism and political incorrectness and some just don't care/notice.
Regardless, a leader should encourage community members to voice their legitimate concerns. Duncan's actions were simply immature and unwelcoming. I don't blame Oliver for leaving and hope we see a public apology from Duncan.
No it couldn't, Uber isn't for sale.
React Native, the open source project, is using Product Pains instead of GitHub issues for bug reports and feature requests. This is because there were thousands of open issues and, just as this document mentions, it's impossible to organize them. The comments are all "+1" and it's really hard to tell what's important and what's just noise.
If you take a look at https://productpains.com/product/react-native?tab=top you'll see the power of being able to vote on these issues.
So why's Product Pains relevant?
1. It's a temporary alternative to GitHub issues. I'm guessing GitHub will get to adding votes eventually. If you want to use Product Pains for organizing issues for your open source project, go for it. I'll even give it away to you for free.
2. It's a community dedicated to improving products. This document is chock-full of great, constructive, actionable feedback. Product Pains is a community built for posting exactly this. You can post feedback publicly, about any product, people can vote on it, and posts with a lot of votes create a social responsibility for the company to respond.
3. It's a way for your voice to be heard. Posting on Hacker News lasts a day and will get your voice heard. If you post actionable, constructive feedback on Product Pains, and 150 people vote on it, it lingers waiting for GitHub to do something about it. Around 600 users on Product Pains are also React Native developers. They'd probably be ecstatic to vote on constructive feedback for GitHub.
For example, go make an account and vote here: https://productpains.com/post/github/implement-voting-for-is...
> Does Apple permit this?
> Yes! Section 3.3.2 of the iOS Developer Program allows it "provided that such scripts and code do not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application."
I really, really hope this doesn't go away.
The world doesn't revolve around America. The Chinese government certainly cares a load more about its own economy doing great than how other economies are doing. They wouldn't sabotage their economy and destroy trillions of dollars in wealth to make a significantly lesser dent in our economy.