arasmussen

Sounds like a good answer to "When have you most successfully hacked some (non-computer) system to your advantage?"

Did you try logging in?

Lyft gives drivers a larger portion of the ride's cost (80% instead of 70% IIRC). I never feel obligated to tip, but tip if the service was great.

#bandaidfix

I left Facebook almost a year ago so I can't speak about Today.

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.

> So degrade the experience just to make the product team happy?

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.

There are definitely parts of the Facebook app built in React Native. I built some of them. :)

The point of React Native isn't to create a delightful product experience.

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.

I totally would have used this last year when commuting from SF to Menlo Park. It's too bad I sold my car and quit my job, would have been fun to meet some cool people and make some extra money at the same time.

My friend is 7 feet tall and he mentioned to me that he fit better in my model S than almoat any other sedan.

Credit card worked for me for the S

Hi Sam,

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 think the term "self-driving" is preferable to "driverless" because it's not like there's no driver, the car is the driver. It's also less scary-sounding which could help speed up adoption. :)

I agree that this is something HN should build rather than be supported via a Chrome extension.

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 actually a good idea

Double taxation for C corps is on dividends but not salary so this isn't really as big a deal as you'd think.

> "so far we haven't seen nearly as much of an effect on early-stage fundraising as the level of press coverage would seem to indicate"

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.

> Better to have 93% of something worth 10MM+ than 100% of 100k.

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.

> 7% is a large amount of equity to give up for the money they're giving you

The value you get out of YC isn't really the money.

7% is a lot.

7%

Bringing up concerns regarding sexism are abruptly shut down and labeled "shit disturbing" by a man in charge.

Agree 100%.

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.

Big spenders do a lot of due diligence to make sure that the money they spend is actually giving them a positive return. It's not like businesses just throw millions down the drain and hope it gives them results. Facebook is working great for them and it is not a scam otherwise businesses wouldn't be spending billions on advertising there every quarter.

I just published a Medium post about this exact subject: Tech Innovation & Economic Inequality. https://medium.com/@a13n/tech-innovation-economic-inequality...

> With $80 billion, Google could buy Uber...

No it couldn't, Uber isn't for sale.

Why did this get downvoted? Ugh.

I work on a very relevant project called Product Pains.

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...

The most interesting part is that Apple seems to be cool with this:

> 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.