umm...

I feel guilty for posting this, because these new devices have NO HealthKit integration. That's a deal breaker for me and a ton of others!

This place is way better designed and equipped than most startup cowering spaces!

This almost sounds like an oxymoron.

I agree. There is virtually no way you can smoothly upgrade an Angular 1 project to this. You'd have to redo most of it from scratch. There are a lot of huge projects that are built on Angular 1 -- many enterprise products too. And this is a huge blow to maintenance. It might be a reason for a lot of people dropping Angular and going for something that makes more business sense. Maybe it's React's time to shine.

The thing with React is that either Facebook's engineers are incredibly prescient or lucky. React very is really well designed and feels natural with ES6.

It's so incredibly designed, even without the ES6 optimizations of 0.12.0 (coming soon) you can code today in ES6 (I use 6to5 with JSX transformer harmony just in case).

Yeah I am betting on React. I am not a Web GUI developer and learned about Angular and now React just out of curiosity. Well I tried to learn Angular and got stuck at the termology soup of "directives", "digest cycles", "factories", "services", "dipendencies", "scopes". I understand all those English words but I still don't quite have an idea of how they are helping me.

With React somehow the whole data flow and how components work and even JSX make a lot more sense.

Facebook uses React in production (a lot) and has to migrate any code just like you would as a user of the library. Facebook is effectively always running React master.

Facebook also has members on TC39 and is quite involved with evolving the language.

Is he using TypeScript or ECMAScript 6? Also, is it just me, to does this seem like a completely different framework than Angular 1?

Typescript is ECMAScript6, with additional (typing) features.

I'd venture it's ecmascript 6 being used, as Google suffers NIH syndrome too..

I wouldn't call TypeScript an "ECMAScript 6 with types". It feels more like a superset of ECMAScript 5 as it introduces non-standard features such as static class properties and public/private scoping while major ES6 features such as proxies, symbols, generators, modules or block scoping are not supported.

Yeah, it definitely is EcmaScript 6. They've added the "class" and "constructor" keywords. Typescript is very mush modeled after EcmaScript 6 anyways, so technically it can be both. But I'm sure it's EcmaScript6, because that's what Angular 2 is written in.

See the post about Google's AtScript that was on HN yesterday.

So is this basically TypeScript with annotations and types available at runtime?

I think this is what he's trying to do with the Google Maps thing: http://www.html5rocks.com/en/tutorials/geolocation/trip_mete...

I think he's talking about the navigator.geolocation object.

It's an acqui-hire; they want to build the most talented team so that they can develop the best smart-home devices. They're going head-to-head against Apple, but with a very different strategy. Apple is trying to build the best mobile devices and the best SDK to create a huge market and a great dev environment for developers to build devices for HomeKit. Google's strategy seems to be to build their own great smart home devices.

That's a viable reason. But I think they're mainly doing that because Tony Fadell is in charge of Google's whole smart home operation, so Nest has to remain the overarching brand.

This is a lot like what @paulg was talking about on his "Frighteningly Ambitious Startup Ideas" essay when he talks about replacing email: http://www.paulgraham.com/ambitious.html