robwormald

8 ms·

1.
by robwormald 6y ago
Ugh. Thanks for the kind words :)
2.
by robwormald 9y ago
Angular core team here - unfortunately, this post ignores Angular 2+ entirely (its @angular/core on npm) - the numbers are only for AngularJS (1.x). We’ve reached out to the NPM team to get this corrected. See https://npm-st
3.
by robwormald 9y ago
I did the Mars demo at a conference a while back - the first couple of minutes I was underwhelmed, but at some point, my brain "bought-in" - I noticed this when I crouched down to look under a virtual rock outcropping without a
4.
Improving ergonomics of events with Observable(github.com)
2 points by robwormald 9y ago|0 comments
5.
by robwormald 9y ago
Note this chart is actually showing AngularJS (1.x) only. NPM only started exposing stats for @scoped packages recently, so @angular/core (Angular 2+) only has a few months of history. See https://npm-stat.com/charts.ht
6.
by robwormald 9y ago
You'll be pleased to know that we're making Zones optional pretty soon here. This would mean taking control of change detection yourself, of course, but there's plenty of valid use cases where that's a reasonable idea.
7.
What Angular Is Doing with Bazel and Closure(medium.com)
2 points by robwormald 9y ago|0 comments
8.
by robwormald 9y ago
FWIW, Angular's release cycle is roughly based on the same cadence as React :)
9.
by robwormald 9y ago
Angular core team here, we're restructuring some of our docs at the moment and this is super useful feedback. Thanks!
10.
by robwormald 9y ago
It's unlikely we'll ever have developers write Custom Elements directly - that said, the View Engine rewrite we just did gives us the ability to (theoretically) have our compiler output Custom Elements. We're investigating so
11.
by robwormald 9y ago
This is what the AngularJS versioning scheme was, nearly exactly. Everybody hated it. Hence, semver :)
12.
by robwormald 9y ago
1) the core of Angular Universal "graduated" into @angular/platform-server with 4.0 - previously it was a more experimental project. We're officially supporting a "renderToString()" API that can be used however
13.
by robwormald 9y ago
absolutely. we're 100% invested in Rx, and more than anything else I'd like to see the Observable type standardized.
14.
by robwormald 9y ago
You can already use most simple web components in Angular without issues - as far as Angular is concerned, it's just another DOM element. We also support native (or emulated) Shadow DOM out of the box. It gets a little more interesting
15.
by robwormald 9y ago
This is good to know, cheers!
16.
by robwormald 9y ago
The first two are pretty well covered by our friends at Ionic and NativeScript. The last one, well, that's a bit more complicated. Let's just say that sort of thing is on the radar.
17.
by robwormald 9y ago
New release of CLI is running final checks in CI. Should release momentarily! Edit: it's released! npm install @angular/cli
18.
by robwormald 9y ago
We've got some really cool ideas to make Rx really first class in Angular. It's already pretty deeply integrated, but with a little work, it'll be awesome.
19.
by robwormald 9y ago
you'll find that generally, we refer to it as "Angular" or "Angular 4.0" - officially, AngularJS is 1.x. We'll see how it shakes out, but so far our community has been pretty awesome about it.
20.
by robwormald 9y ago
Most developers should be able to simply update their dependencies and rebuild. A few APIs have been deprecated, but they continue to exist and can be removed at a developer's leisure, per our versioning policy [0] http://an
21.
by robwormald 9y ago
That's discussed in the doc (and there's some metrics). Update speed takes a (minimal) performance hit, in exchange for code size reductions. We (and our colleagues at Google working on the web in general) find that the largest im
22.
by robwormald 9y ago
Major release every 6 months, 2 major version deprecation policy. There was definitely some initial pushback, but we hope to demonstrate with this release that it's a) not that scary and b) good for both developers and users. Most devs
23.
by robwormald 9y ago
Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're interested in front-end at all. Happy to answer any questions! [0] https:
24.
by robwormald 10y ago
i tried the Walk On Mars hololens demo at a conference last year. It seemed very clunky at first, but a couple of minutes into the demo, I entirely unconsciously crouched down to look under a virtual rock outcropping - that was the point I
25.
by robwormald 10y ago
You might be looking for Smart Folders - https://support.apple.com/kb/PH22188?locale=en_US
26.
by robwormald 10y ago
You might find https://developers.google.com/web/updates/2015/12/background... interesting?
27.
by robwormald 10y ago
the other thing to note is that a lot of new APIs (and older ones which are being updated) require HTTPS - geolocation, webBT, webUSB, service workers, etc, all require HTTPS (or will, soon).
28.
by robwormald 10y ago
https://developers.google.com/web/updates/2015/07/interact-w... is a good primer on the API, and a links to security explainer: https://medium.com/@jyasskin/the-web-bluetooth-securit
29.
by robwormald 10y ago
ng core team here, feel free to reach out to me on twitter if you need any help getting this done - @robwormald
30.
by robwormald 10y ago
ngrx creator (and ng core team member) here - you'd be surprised at the uptake on ngrx/redux in enterprise I think - a lot of the constraints / guarantees redux offers are really attractive to big teams, and pretty much every

More ›