With two jam-packed days in the books, only one day remained. The format for the final day of ng-conf was another single room, all day series of sessions. Much like the first day, the range of topics was both broad as they were relevant and informative. Day 3 had a few major themes expressed in the speakers’ presentations.
Brad Green and Rob Wormald presented the keynote presentation. They talked about how Angular fits in at Google. And by fit in, it is more like Google runs on Angular. Google has hundreds of its major systems running on top of Angular including data center allocations, release management, product launch approvals, and bug tracking. Google demonstrates its commitment to Angular as well as its commitment to the ecosystem around Angular.
Day 2 of ng-conf was a fair day. Multiple talks and activities took place all day long. Not being able to clone myself and see all of the discussions, I set my focus on a particular path for the day. So let’s take a look at the path I chose.
Unfortunately, the time slot for the RxJS presentation cut into this talk. I was able to catch half of the speakers, and even then, it was very informative. The format for this presentation was a series of lightning talks from representatives of multiple companies talking about how they squeeze the most out of their Angular apps. … Read more
April 5-7th 2017 marks the 4th year of the Angular conference ng-conf. This year’s ng-conf marks my first year attending, w00t w00t to that. From the first day’s rapid-fire talks, the tone of the conference, and I think for Angular in general, is set for the year. Some of the major takeaways from the first day I’ve highlighted below.
Before the keynote took place, Aaron Frost, one of the organizers took a moment to go over the code of conduct for the conference. The organizers wanted to stress the importance of creating a conducive environment for sharing and learning over the next few days. This point speaks to the overall message that the Angular community wants to convey, which is “Build with Us.” And, by providing an inviting and open ecosystem to current and new developers, they hope to grow the community.
With that theme in mind, a talk by Justin Searls focused on getting the creative juices flowing. He discussed his personal philosophy around what sparks his creativity. Justin then provided some insight into what could help others be more creative, which translates into building apps. The key takeaway from his talk was that it is okay to build software that interests individuals, reflect on one’s feelings, and finally find your outlet, whatever it may be.… Read more
Angular is a massive user interface framework. It is a highly opinionated and comprehensive solution to many of the challenges of constructing modern user interfaces, particularly within a web browser.… Read more
Brad Green spent some time discussing how Google as a company is fully embracing Angular as an application development framework. In fact, the goal is to have all web application development within Google to be using Angular by the end of 2017. He also explained that it makes sense for them to invest so many resources into Angular as an open-source project because of the additional benefits to Google itself. The primary benefit is the large ecosystem that has grown around Angular. Libraries and tools would probably not exist if Angular was simply an internal Google project. In addition, Google has built several tools internally that have been reproduced in other open-source projects. It makes sense that there is benefit to sharing these efforts with the community. It also helps with hiring within Google, where proprietary in-house tools require additional training and ramp-up for new hires. And, of course, the overall quality of the source code is improved by the great feedback received from the community through PRs, documentation, and training.
Day Two changes things up from the Day One and Day Three single-track format. There are breakout sessions focused on a specific topic as well as chances to sit down and ask questions of others who have expertise in Angular, including members of the Angular team themselves. It’s a good chance to listen to how others are approaching their development challenges and opportunity to discuss lots of interesting details in depth.
The first session of the day had a few large organizations talk about the things they are doing within their organization to manage Angular projects, how they approach analyzing the performance of these applications, and what kinds of things might help them improve these operations.
In terms of analysis, there was a great emphasis on metrics (“plan and measure”). This included low level tracking of “time to first paint”, “time to meaningful content”, and “time to interactive”. But it also included higher-level tracking of things like “perceived performance” (obtaining feedback about how the user perceives the performance of the application).
Tools were mentioned that help in this analysis. The primary tool, of course, is the Developer Tools within the browser (there was a lot of praise for the capabilities of Chrome Developer tools particularly).… Read more
I’m glad to be back again at ng-conf in Salt Lake City. I’ve used Angular since the very beginning and it continues to get better. Here are some of the highlights that stood out to me from the first day of the conference.
During the keynote, there was discussion about gauging the success of Angular. They estimated that the community is around 1.3 million users of AngularJS (version 1 of the framework) and 810 thousand users of Angular (versions 2 and 4 of the framework, they skipped version 3). Of all the applications out there, about 90% of them are internal applications (ones we can’t see because they are behind the corporate firewall). 17% of the public Angular applications are already on version 4 of the framework.
There are over 200 applications internal to Google that are using the framework. These applications serve as an initial test bed for all updates of the framework, helping to ensure smooth updates to new versions.
Version 4, released a short time ago, has some great improvements in performance and the size of payloads. The team worked hard to ensure that upgrades went smoothly and there were no breaking changes in the framework APIs.… Read more
Eric covered the differences between Angular 1 and 2 as well as a live coding session for the essentials of building components, building templates, data binding and handling events.
The last day of ng-conf 2016 continued with lots of great information. Some highlights:
ng-transcludedirective now supports a name property and directives can specify multiple transclusion slots that correspond to these names. This allows Angular1 to come closer to how
ng-contenttags work in Angular2.
Some highlights of day two of ng-conf 2016:
angular2/coreis now referenced as
@angular/core. This change allows for better use of the ES2015 modules and better optimization when using the offline compiler.