Nevermind about that
Previously, I wrote about my adventures in Angular.dart and Polymer.dart and my reasoning of why I am using one over the other. Go ahead and read that first to make sense of the rest of this. Well, shortly after, I decided I disagreed and moved back to Polymer with generally happy results.
My final straw with Angular came when I was trying to dynamically add a component to the DOM. It’s not nearly as easy as it is in Polymer where it’s as simple as creating any other HTML element. For Angular, what one would think would be a simple…
Great, for the most part
Over the course of the past couple years of using Dart, it has quickly risen to be my language of choice. For the web, it is an easy choice compared to Javascript. Outside of the web, it is more about familiarity. Sure I could be writing in Java or Python, but Java isn’t very sexy, and duck-typed Python can be difficult to grok. Of course, I imagine I could write readable Python…but I’d just rather not go there. Dart is just as easy. Write a main function like good ol’ C, hand it off to the Dart interpreter, and you…
Angular and Polymer
I am an avid fan of Dart and the modern web. For the past week I have been sinking more and more time into both Angular.dart and Polymer.dart as a sort of duel to see which one serves my everyday needs best. My web apps usually are not huge enough to necessitate the majority of Angular’s features and for this reason, I am simply focused on these libraries’ takes on web components. Specifically I am looking at ease of use and testability. …
