NGConf Theme: Angular has Yo’ Back

Conference T-Shirt and Lanyard

I was fortunate to attend NGConf in my home town: Salt Lake City. It wrapped up Friday night.  I can’t add much to all the resources that will be available at their site. Check out the videos on YouTube.

I’ll report my sense of the conference and some personal highlights.

Don’t Fear Angular 2

The recurring message of the conference was that Angular is going to support you. This started with details about the overlapping support plan for angular 1 and 2. The theme continued throughout the conference as people talked about animations, i18n, material, and mobile support.

Conferences are so good at recording the details and making the slides available. I just takes note of what stands out. This is a URL here, a concept there.  It’s mostly a soup.  Your mileage may vary. Again, see their official site and recordings above for the full scoop. Here we go…

  • Async Q&A at http://www.reddit.com/r/ngconf
  • twitter: #ngconf
  • The new router looks very promising. Many new features and serious approach to catching all use cases. Written for Angular 2 and back-ported to Angular 1.4
    • Watch ng-europe angular router design video.
    • Note to self: Replace bbq with angular router.
    • Speakers recommend using new router instead of UI-Router.
  • Angularjs.org – 1.0. angular.io is the 2.0 site.
    • They will release angular 1 until majority move to angular 2.0. They will publish the metrics they use for making this decision.
    • They will support a big bang migration path and both inside-out and outside-in migration paths. Will publish a migration guide.
  • Angular Material: responsive design. Built for mobile and accessibility.
  • AtScript is now TypeScript. Intriguing talk of Dart and TypeScript. Should play with these things.  Noticeable buzz.
  • PluralSight is looking for authors. Good to support community. Good way to build career. Could make money sense.  My wife is published, have several friends that are, too. Often not very lucrative. PluralSight’s pitch is intriguing. Reward authors. Win win.
  • Interesting use of scripts during prototyping to pull data from a google doc into a prototype.  See script.google.com. See ng-prototype (link?).
  • McGraw Hill sponsored the children’s track for the conference. Very cool. Book publishing company.
  • Bench Press — for running benchmarks.
    • Compare with BenchMarkJS for running micro-benchmarks.
    • BenchPress is for larger interactions — macro benchmarks.
    • Built on protractor, WebDriver.
    • Can set up own performance bench marks.
  • ngTasty — common angular components at twitter.
  • See github.com/DanWhalin for more info on Angular and TypeScript.
    • Check out TypeScript 1.5 (soon to release) with angular 1.4 (soon to release) and angular 2.0 (who knows when).
    • Play with typescriptlang.org/playground
    • Personal note: CoffeeScript has been painful experience on large team. Didn’t go whole hog and the partial dabbling just led to a lot of pain over time.  Can TypeScript be better? Am I ruined for types in my JS? I know Tom Valetta is. This came up several times in breaks.
  • Accessibility testing.  Protractor plus tools to audit accessibility. Google Marcy Sutton for videos.
  • Angular Fire — Fire-base with stronger integration with angular
  • Ionic – Mobile Real time apps.
  • Web Worker Angular Digest.  NOTE: Angular doesn’t run in a web worker, but pieces of it can.
  • Try makingamobileappwithng-cordova.
    • Guy behind me, “I don’t care what they say, I still think that if you aren’t doing native then you’re doing it wrong. On the web that’s HTML, CSS, and JS. On mobile thats Swift or Java.” Other guy, “What about Dart? Is Google doing it wrong?” First guy hesitates, “Uh… yeah.” With growing conviction. “Yeah, They’re doing it wrong.”
    • My experience is that a hybrid app contest with native development lost out. The hybrid thing had too many special cases and felt like, “The worst of all worlds” to our developers.  I’d love to be a believer in hybrid.  Need more cuddles to get over past woes.

Day 2:

  • Idea to self: write my personal tools in bleeding edge so that I can feel out these things. For example, hapi, ng 2, etc.
  • Binding moves data from parents to children. To go the other way use events.
  • Falcour –async models.
    • Very similar to work I did a few years ago in Flex.  Had  a complicated system where the bindings on a proxy allowed me to compute the smallest amount of data to fetch.  Slick with a price. Can be complicated to optimize. Difficult to debug when it gets it wrong.
  • github.org/microsoft/typscript and ngconf2015demo
  • nganimate — yearofmoo.com
  • Note to self: ng2 is so compatible with web components we must remember to use the principle of least power. If the reusable bit can be just a component then perhaps that is better than bringing in angular.  Must play with this. Still, the principle is sound. … Can something as big as the pedigree on FamilySearch.org/tree be a component? Or is that an app since it has such deep hooks into data?
  • Google uses screen shot comparison. This is a moment of validation for me.  I was just suggesting this as work earlier in the week.  So many problems are obvious when rendered and terribly difficult to catch otherwise.  I’ve met lots of resistance to this in the past because it can give you lots of false negatives.  But that just means keep the human validation on rails and the total number of shots manageable. Still worth looking into.
  • LotsofenergybehindRxJS observables. Allows stream processing.  In lunchlinechattedwithTomValetta about this.  Good for things that would be a promise, but you also might want to update it.  For example, perhaps you have acentralviewwithmanyancilary. Each view can ask, “what are we looking at?” A promise can only answer that question once. An observable can update the answer with, “Oh yeah, now we’re looking at this.”
    • Note to observables fans: you need better demos.  Text following a cursor is just too abstract to get me going.
  • KendoUI from Telerik. Try out their free widgets.
  • Check out ngHammer
  • Check out ESLint style checker
  • jpapa.me/style guide (link?)
  • i18n –pseudotranslation tool — very useful,we’vehadtoimplementthisover and over again as we move through technologies.
    • ng 1.4 will support gender and plurals
    • message format support
    • pascalprecht.github.io
    • IDEA: i18n torture test: make it possible to translate the sentence, “Your grandfather was hungry so you gave him 2 hotdogs.” But be able to vary “grandfather” with both maternal and paternal grandfathers and grandmothers (hint: it’s different in some languages like Swedish. Farfar and morfar both mean grandfather.); be able to vary the pronount “him” to “her”; be able to vary the number of hotdogs.
  • Maker of plunker was an accountant with no training. Did scary things in the early days.  Book recommendation: Adapt: Why success always starts with failure.
  • Victor Sarkin — dense change detection stuff.
  • Book recommendation: Nurtured by love. Talent is made, not born.

The Swag

Seems that the leaders of the Angular community are very interested in creating a growing population of developers with warm fuzzy feelings about the whole project. On stage they estimated that one in four attendees would win a prize.  I won a year subscription to Audible which is worth about $130. Many people won gifts of similar or greater value.  The
mood in the room was very positive.

If it was all prizes then that wouldn’t be very inspiring. The core message of the conference reinforced the generous prizes: the leaders of the community will stand by its members. Sitting in the room with these folks you felt that they were genuinely concerning themselves with the most important issues they could identify, and they want our help keeping them on track.

Animated gif of angular team has yo back.

Published
Categorized as news Tagged

By Tyler Peterson

Web Developer and a hiring manager at an established technology company on Utah's Silicon Slopes in Lehi.