Angular 2.0

Post by ssmoot » Wed, Mar 19, 2014, 1:50 AM UTC

thatsar_ wrote: post #133

talmand wrote: post #86

Earlier quoted context omitted.

I agree with you that since your elements appear to not be a part of the HTML5 spec they must be custom and are directives, wouldn't it be a good idea to mark them as such in some way? Maybe prepend them with "an-" or something? The reason being, considering that HTML5 is an ever evolving spec that it might be possible for a new element to be introduced that could be using the same name as one of your examples. That…

Maybe prepend them with "an-" or something? Yes, this is actually the recommended practice from the documentation. Built-in Angular directives are typically prefixed with `ng-`, and they suggest that other projects/developers use their own prefixes to avoid conflict.

Post by nwmcsween » Wed, Mar 19, 2014, 2:35 AM UTC

stuaxo wrote: post #65

jeswin wrote: post #15

AngularJS has a J2EE mindset. Where libraries grow to become as hard to learn as programming languages themselves. It does not make semantic sense to me anymore. Here is an example from the site: Length (float): {{length}} This is not a valid float number! How semantic is ng-show="form.length.$error.float? smart-float sounds like C++. If programming languages worked like this, we wouldn't have built many apps. The pr…

This is true. AngularJS is much better than what we had before, it is kind of large and monolithic. The cycle probably goes thusly: Large monolithic framework comes and shows everyone a new way of doing things (Angular/Django). People think it is too large and monolithic, so make microframeworks (Flask/Whatever comes after Angular). The next step will be a kind of happy medium.

Post by iSnow » Wed, Mar 19, 2014, 8:54 AM UTC

donw wrote: post #48

iSnow wrote: post #23

Earlier quoted context omitted.

I only looked superficially at React, so maybe I got something wrong, but the HTML/XML intermingled with Javascript seems extremely off-putting to me, akin to ASP/JSP/PHP.

The thing that sold me on React was this statement: "Most people make the mistake that the DOM is a place you put things." The DOM is what the user sees. That's all. With React, you have a virtual DOM that can hold everything, not just what the user sees. It's a pure data structure, and can be manipulated as such. Because that DOM is a pure data structure, React can figure out for you what parts have changed, and re-…

Post by Cthulhu_ » Wed, Mar 19, 2014, 12:10 PM UTC

nateabele wrote: post #136

Kiro wrote: post #92

Earlier quoted context omitted.

I don't understand how that correlates to the current DI. How do I rewrite the following using the new DI system? function MyCtrl($http, Base64) { $http.get('http://www.example.com').success(function (data) { console.log(Base64.decode(data)); }); }

import {Http} from 'angularjs/http'; import {Base64} from './base64'; @Inject(Http) @Inject(Base64) export class MyCtrl { constructor(Http, Base64) { Http.get('http://www.example.com').success(function (data) { console.log(Base64.decode(data)); }); } } Not too bad, right?

Post by orandolabs » Wed, Mar 19, 2014, 6:31 PM UTC