Over at iTunesConnect, Apple is using Angular v1.4. Few thoughts:

  1. Interesting that unlike Facebook and Google, Apple doesn’t feel the need to create its own JavaScript framework. It is a beneficiary of Google’s open-source pioneering as much as any of the rest of us. This actually makes sense — we already have very excellent JavaScript frameworks and libraries out there. It would be hard to out-do those and an attempt would be misdirected energy.
  2. iTunesConnect’s front-end build system is interesting. It is minifying its own code but none of its vendor code. This causes me to wonder if it is minifying its code for security instead of for performance. If that were the case then I find that to be superfluous, given how easy it is to un-minify JavaScript.1
  3. I adore the fact that the view-source DOM is 1 line of code. Eventually, the vast majority of the web will be built this way. It’s the future.
  4. The homepage console is full of errors. Why this oversight? It wouldn’t get by with this if it was using TrackJS.

I wonder how long the site will be on Angular 1.x. Angular 2 is in beta still but it’s getting closer to production every day.

Update 2016-06-15: The Apple Developer portal is also built in Angular v1.4. This company really likes Angular.

  1. Minifying JavaScript is a great idea for performance benefits. Obfuscating JavaScript, however, is a generally unwise idea. It negatively impacts performance and doesn’t truly protect the code. If a server sends a client a file containing executable code in a language that’s interpreted (as opposed to compiled), it can’t really secure that code. Why bother? ↩︎