47 karma · joined June 3, 2015
But that begets another questions - is it more about finding a passion that keeps you high spirited 24x7 anywhere or finding a place that is stimulating everytime?
If Los Angeles had 1/3rd the tech scene that you've here in the Bay Area. I'd move there in a heartbeat. By tech scene I mean a good mix of big tech co., an unicorn or two, and buzzing startups.
IMHO (and experience) an A1 CEO/product/sales/business-guy can't be an A1 CTO/tech lead/research-guy and vice-versa. My operating keyword in this argument is 'A1'. This is counterintuitive to our natural inclinations.
Edit: Typo
Have you ever noticed that working on an ultra-cool product that goes bust won't cut you any slack. You get more credits for minor contributions to known brands than massive contributions to busted products.
Your skills are tied to your product's PR (apparently).
Circa: 2008-09
Greatness is independent of school or diploma. Some of the best minds of the world never set foot in a school campus.
Here's my 2 cents - Apple could introduce an Indie category/sub-categories. Community could come up with a distinctive micro-icon that represents something as an indie app. Sort of like the tiny Zynga dog icon you see in their apps. Once again, Apple could introduce apps to be flagged as indie by its users. Refine search results by this flag.
I think Apple does their job of promoting really cool indie apps and games. But it has to be outstanding or novel enough for them to pitch it forward.
1. Salary-based auction, 2. Do not bind employee to employer after 1 year, and 3. GoTo #1.
Let's say I don't have any real world examples. I'm not seeing any engineering marvel in React Showcase. https://facebook.github.io/react-native/showcase.html pales in comparison to http://phonegap.com/app/
Please don't get me wrong, I'd love to use ECMAScript(, CSS and markup) to do all web, native and server side development. Unfortunately they are marred by poor API support, performance and customization. Last two are extremely critical for non-trivial apps.
If you are building run of the mill simple apps like - news feed, photo, video and reading etc. You'll be okay with anyone of the above 'web stack'.
Here's the litmus test. Ask the Reactive Native team to port their non-trivial paper app or mission critical messenger app or main app to Reactive Native. They are using Reactive Native for a lame duck Groups and some ad manager app.
JavaScriptCore is one layer deeper than wrapping a UIWebView, but it's several layers from true native.
p.s. I've explored JavaScriptCore the first day it was available to developers.
p.p.s. I noticed you are a "React fanboy," so that's normal.
Having built 3 non-trivial iOS apps using phonegap and JavaScript. I have come to the conclusion that I'm never going to build native apps using web stack. I have struggled with API support, DOM limitations and performance.
Disclaimer: I have not tried react native.
I think it'll fail for mission critical and non-trivial apps. If you just want an AppStore presence for your browser app or your app is trivial like one in the post. You are probably going to be fine.