I think a more accurate title might have been, “It’s possible to use Angular 2 in a way that I do…
Jake Adams

Thanks, Jake!


Yes, I can use CoffeeScript with ng2. However, CoffeeScript did not work well with the style guide for ng1 — I hope this improves for ng2. Also I would love to use the “recommended” flavor of language (TypeScript in this case), since that makes life so much easier (documentation, reading code of others, sharing my code with others).

HTML Template Syntax

I didn’t know about the bind-someproperty notation. Thanks for the hint! This looks more natural to me and comes close to the way think aurelia does it.

Are these special charactes (like the braces in [someproperty]) really in line with the HTML standard? To my eye it doesn’t look like pure HTML attributes to me anymore — but it might just be my lacking knowledge of the HTML standard.


Yeah, I will take a look at the annotation-less way of doing it. I don’t think, annotations are bad; I just think, that annotations as used in ng2 are a code smell covering up deeper problems. I also fear using ng2 in a non-mainstream way for the same reasons I stated for using CoffeeScript instead of TypeScript.


Definitely, an IDE is totally optional (at least right now). My only concern are all those people flocking to IDEs right now and the impact an IDE might have on their coding style. The worst nightmare where an IDE totally messed up newbies was Visual Basic back in the days — they all thought, coding was more like clicking around and scattering random code blocks ;). With Xcode I see people not being able to remember method signatures, not being capable of compiling their code without IDE dialogs or creating bad code design due to just clicking and pasting code.

Again, IDEs are not bad per se, I only saw them covering up underlying problems all to often in the past. If you can use a framework or language just as well with or without an IDE, it’s fine.

You made clear that I could use ng2 with different languages and coding styles, that better suit my taste. I think, that these various options are NOT a good thing. We had that problem with ng1, when there where so many different coding styles out there, that a newbie — even a decent developer — was easily lost. Coming from a Ruby on Rails world, I love “convention over configuration”. The ng2 approach sounds more like “you can configure your own ng2 flavor” than “this is the convention everyone will stick to”. I feel ng2 is making a mistake trying to offer everyone his individual flavor.

Thanks again for your comments and hints!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.