News

Angular Q&A: Components, Getting-Started Tips (and that 'Total Rewrite' Thing)

Noted database expert and author Ted Neward explains his favorite features of Angular and how to get started with the popular database.

Ted Neward, director of Developer Relations at Smartsheet.com, is well-known as a presenter at Visual Studio Live! and Live! 360 events. He has long served as a columnist for MSDN Magazine as the "Working Programmer," where he's noted for investigating and explaining new database technologies and techniques, signing off with a cheerful, "Happy coding!" We caught up with to ask some questions about Angular in advance of an upcoming presentation in Orlando.

What were the special challenges developers faced when moving from Angular 1 to Angular 2?
Well, one of the challenges is inherent in your question itself: The Angular team chose to rename the framework from "AngularJS" to "Angular," meaning that "Angular 1" should actually be "AngularJS," and "Angular 2" should actually be just plain ol' "Angular." That raises no end of confusion when speaking about the two frameworks, to be sure.

"Component-based design is like object design, but with "thicker skin", meaning we treat components in a more opaque fashion, making them more accessible and usable for reuse purposes, among other things."

Ted Neward, director, Developer Relations, Smartsheet.com,

But the naming change was appropriate, because in many ways Angular was a near-total rewrite of AngularJS, meaning that any AngularJS code will not be silently upgradable to Angular. They kept many of the same concepts, but sought to strengthen those concepts and make them more apparent and clear. So moving from AngularJS to Angular means making a slight conceptual shift, but a near-total rewrite of anything that isn't pure business logic in the code.

What is your favorite improvement in Angular 2?
The new emphasis on "components." Component-based design is like object design, but with "thicker skin", meaning we treat components in a more opaque fashion, making them more accessible and usable for reuse purposes, among other things. Components were what enabled the Golden Age of GUI Builders (the days of VisualBasic, Delphi, PowerBuilder and the like), and there's solid reasons to imagine that something similar will emerge out of this approach for the Web -- which in turn means that developers can deliver useful and powerful applications for the Web so much faster than before.

What are your top 3 tips for anyone getting started with Angular?

  • Bookmark the Angular CheatSheet on the Angular Web site.
  • Learn and master the TypeScript language.
  • Come to the Hands-on-Labs in Orlando. ;-)

What do you think is the most helpful section of your full-day hands-on lab at VS Live?
We spend as little time as possible talking -- the emphasis is on the "hands-on" part of the title. Programmers often learn best by doing, so we'll talk only enough to get the concepts in front of people, then turn them loose to learn by doing.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube