HN user

dj_doh

47 karma
Posts0
Comments51
View on HN
No posts found.

I do not entirely disagree. I don't hate winter but icy sidewalks are scary:) I also agree with your assessment that "...most people are living in generic developments and driving to generic office parks..."

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?

Different Strokes. This was my primary reason to choose between New York city and the Bay Area some 6 years ago. The 250 miles radius around the bay area has lot to offer. That said, I do feel there's a deprecation at play. You can only make so many trips to Tahoe and Santa Cruz.

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.

Thought provoking. I read it earlier today, dropping in to add my two cents. I've been toggling between roles that either fits into 'product manager' or 'product developer'. That included a short stint as a startup founder.

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

Yes, it's the employees.

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

Probably too late in the conversation. I'm a Pittsburgh product, as in I did my grad schooling from there. I've always found pgh vibrant! I was residing in the Oakland area. I liked everything about it. To this day I call it one of my favorite places to live or visit.

Circa: 2008-09

Party true. But don't be surprised when Tesla revamp their user inputs with Siri-like interface. It's easier to go from touchscreen to voice then nobs-&-bolts to voice. The later is few layers closer to the traditional interfaces.

I second these comments. It feels like they want to put A-grade designers for electric cars. Same can be said for BMW i3 and (NotSo)SmartFor2. They are joke to say the least.

My undergrad advisor gave one of the best advices about why diploma is important. A college education is a social institution where you work with dozens of students, teachers and staffs across disciplines. Ideally, culminating with a diploma. That diploma doesn't tell others how good you are or you can be. It tells others that you can be part of a social institution and get some things done.

Greatness is independent of school or diploma. Some of the best minds of the world never set foot in a school campus.

I can get behind this idea. Elementary homework, more like childhood stress pill. Just replace them with more do-it-yourself type of projects.

I agree with most comments here. App market maturing, user behavior maturing. It was always going to happen. Fart apps could only sustain so long:)

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.

Okay how about one very, very simple question - Can I replace my all of my Swift and iOS+tvOS+watchOS APIs with React Native? To make it easy for you. Can I do that within next 1 year? What will happen when Apple will introduce a slew of new APIs will be introduced in Sept?

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/

I've dabbled with this JavaScript for native code since 2010-11. Appcelerator Titanium SDK (now Appcelerator), Telerik, RubyMotion, Xamarin and of course PhoneGap (including PhoneGap Build). I've not used Xamarin, but putting it there to give a broader picture.

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.

Longevity and robustness of jQuery is hard to match. 10+ years for a software project is amazing. Hopefully, in next few years pure ES6 (and later ES7) will give us that joy that's been missing.

Good luck sir getting web stack to work with native that's at par with Swift/Obj-C perf. Also, do share some non-trivial apps that you/your team has built using web stack on iOS.

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.

The biggest barrier to high fidelity ECMAScript apps on native platform is simple economics. Apple is guaranteed a $99 bounty when you push something on the appstore. Making Safari or WebView compatible with their native APIs and performance is a risk for AppStore.

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.