Live data from Hacker News

AngularJS 1.2.0: timely-delivery

blog.angularjs.org

41–50 of 64 posts

Re: AngularJS 1.2.0: timely-delivery

#41
post #30
post #26

Earlier quoted context omitted.

A good example is where I have a list of items which is filtered by a select[1]. I have the select wired up to the controller with a two-way binding and the controller watches for changes to the binding and filters the list accordingly. Maybe this isn't an idiomatic way to do it? [1] http://plnkr.co/edit/ykfblPHlwkBJyMeObFyV?p=preview

Here's your example without a watch: http://plnkr.co/edit/GCv7bQALiOTgJ0npavwi?p=preview

That looks interesting, so does the filter reevaluate automatically when any of the variables used in the expression change?

edit: and thanks a lot for taking the time to look at it!

Re: AngularJS 1.2.0: timely-delivery

#42
post #38
post #32

Earlier quoted context omitted.

so what the point of introducing a "private" access modifier that doesnt exist in javascript since one can still access privates? looks like pure politics within google. A breaking change like that shoved at the latest minute? you bet it is.

> shoved at the latest minute The pull request was opened 3 weeks ago with plenty of discussion.

3 weeks of discussion for a breaking change is "last minute" in my book

Re: AngularJS 1.2.0: timely-delivery

#43
post #9

I've done one project with ember and was very happy with it but I'm now working on a project where I only need parts of the page to be controlled by the framework. So far I'm loving the way angular integrates with the dom but once you get back to the controllers/directives it suddenly feels like I have to do a whole lot more work than with ember. The main difference seems to be that you have to manage updates yoursel…

From my vague understanding, I've heard knockout described as similar to your desired "embular"

Re: AngularJS 1.2.0: timely-delivery

#44
post #9

I've done one project with ember and was very happy with it but I'm now working on a project where I only need parts of the page to be controlled by the framework. So far I'm loving the way angular integrates with the dom but once you get back to the controllers/directives it suddenly feels like I have to do a whole lot more work than with ember. The main difference seems to be that you have to manage updates yoursel…

From my vague understanding, I've heard knockout described as similar to your desired "embular"

I've actually just inherited a giant mess of knockoutthat i was looking to replace with angular. I have to admit that I was actually expecting angular to handle this kind of stuff so I'm a little disappointed in that respect. Angular does seem to have plenty of benefits but I thin i'll give knockout a full review before(maybe it just needs to be structured better).

Re: AngularJS 1.2.0: timely-delivery

#45
post #37

Earlier quoted context omitted.

Not sure what you were expecting. AngularJS apps aren't usually built with a noJS fallback in mind.

Well, from the url: http://blog.angularjs.org/2013/11/angularjs-120-timely-deliv... I was expecting a) a blog post, and b) from the .html-ending a hypertext document, maybe with text and images? What possible reason could there be for this to be "an app"? It's a blog, it's for reading -- and you already need a reader to access it -- why would you implement a (new) rendering engine? Ok, I can see an argument for addin…

Its Blogger -- doing it this way allows them to cache the viewer across their thousands of blogs, and load only the content.

Re: AngularJS 1.2.0: timely-delivery

#46
post #37

Earlier quoted context omitted.

Well, from the url: http://blog.angularjs.org/2013/11/angularjs-120-timely-deliv... I was expecting a) a blog post, and b) from the .html-ending a hypertext document, maybe with text and images? What possible reason could there be for this to be "an app"? It's a blog, it's for reading -- and you already need a reader to access it -- why would you implement a (new) rendering engine? Ok, I can see an argument for addin…

Its Blogger -- doing it this way allows them to cache the viewer across their thousands of blogs, and load only the content.

Well, if they just served html, they'd still only need to serve the content (and the viewer, the web browser, would indeed be cached in the form of an installed application on the end user's system).

Re: AngularJS 1.2.0: timely-delivery

#47
post #7

"This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions." I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field. I blame myself though.

This change was discussed: https://github.com/angular/angular.js/pull/4509 It is also clear from the discussion that there are dissenting opinions -- we are constantly iterating and welcome issues and pull requests to make features work even better. The best way to influence AngularJS is to send a pull request.

You are right it was. But most people do not track all issues of all projects they depend on. While I'd love to do that, there's simply not much time.

I belive this should have been in an earlier RC or Beta. This way, more people would have tested ot, ir got a chance to read changelog (I follow the blog and check each beta release). If that window was missed, it should have gone for the next major release.

What I see is that Google announced AngularDart (http://news.dartlang.org/2013/11/angular-announces-angularda...). Dart has _ prefix for private fields. Then AngularJS team goes ahead and forces the same on the JS implementation.

Seems that there is always some political reason to mess with things at Google.

Re: AngularJS 1.2.0: timely-delivery

#48
post #7

"This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions." I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field. I blame myself though.

Never send DB output directly to frontend, send object, filled by only necessary values from DB output. Otherwise you'll meet security issues and these "_" prefixes will be smalles part of your problems.

Re: AngularJS 1.2.0: timely-delivery

#49
post #7

"This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions." I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field. I blame myself though.

Never send DB output directly to frontend, send object, filled by only necessary values from DB output. Otherwise you'll meet security issues and these "_" prefixes will be smalles part of your problems.

I do that. It's not about sending them directly. It's the underlying field name. I just keep _id fields as _id fields when I prepare data for output.

Re: AngularJS 1.2.0: timely-delivery

#50
post #7

"This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions." I wish they'd discuss stuff like this and I wish that MongoDB did not store primary keys on _id field. I blame myself though.

Never send DB output directly to frontend, send object, filled by only necessary values from DB output. Otherwise you'll meet security issues and these "_" prefixes will be smalles part of your problems.

And how are you supposed to do that using Mongolab, MongoHQ or Firebase?
Post reply on HN