If you are programming in Angular and haven’t tried Model Driven Forms yet, I’m assuming that is because you’ve not taken the time to try to learn it. In this article, I am going to try to convince you that the Model Driven Form based approach is superior to Template Driven Forms and that the only people that are still using Template Driven Forms are people who either have not been enlightened or lazy.
If you are using Angular(2+) and you are looking for an easy way to layout your components that gives you lots of flexibility and very few restrictions, you owe it to yourself to checkout Angular Flex Layout. While it is still in Beta, the framework is quite usable. I’ve been using it in one of my projects and I’ve been quite happy with the results.
I’ve spent the last week putting together a reference app for Angular 2. It is a great exercise to try to nail down the basics of how a new framework works. Next week I plan on doing a similar exercise for React.
Anyhow, I thought for this week’s post, I would try to relay some of my impressions, and some of the issues I see with this new framework.
Every week when I write, I try to think back on the past week and think, “What have I learned that might be useful to others.” Most weeks that is a pretty easy question to answer because I get most of my pleasure from learning new stuff. But this week was different. When I sat down to write today, I couldn’t come up with a subject that couldn’t be covered with a sentence. More of a tweet than a blog post. It was so bad that I decided to go run the errands that are on my list and come back to it once I got home.
Evidently, that was a good move because I think I have something that will be genuinely useful. Although I will admit that if you’ve been working with Angular for very long at all, you may have already learned what I’m about to explain.