Aren't ASP.NET MVC (C#) and Play (Scala/Java) wildly popular examples of typesafe declarative views?
Personally, at this point I'd prefer just the opposite - views to become *more* declarative (and typesafe). I'm hoping that Angular2 (via TypeScript) and WebStorm will only improve in this regard (declarative views with IDE support and type safety). I presume angular2 views written in TS will get compiled similarly to ASP.NET MVC or Play views and hence enjoy similar benefits. On Friday, June 5, 2015 at 2:45:27 AM UTC-7, Gábor Farkas wrote: > > Hi there, > > The rise of TypeScript, closure compiler and facebook flow highlights that > even javascript developers sometimes miss static type checking. I'm > wondering if Angular developers miss type safety in their templates. I've > sumed up my point of view in this blogpost: > https://medium.com/doctusoft-coding-style/benefits-of-imperative-type-safe-views-d9ca4707a48a > To outline, I think creating views in an imperative way can have big > benefits over html templating: > > - template hierarchy is *discoverable, navigable*, easire to refactor. > - binding expressions can be *typesafe *and compile-time checked. > > What do you thing? Does anyone else miss these things? > I've already prototyped doing this with angular 1.x, but I'm wondering if > we can have first-class support to imperatively build views in major > frameworks. > > Cheers, Gábor > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
