Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AngularJS 1.2.0: timely-delivery

blog.angularjs.org

Post reply on HN
Print view View original

31–40 of 64 posts

Re: AngularJS 1.2.0: timely-delivery

#31

Post by btford »

adamors wrote: post #18
jayhuang wrote: post #3

I'm really impressed with Angular. I've previously worked with Backbone.js, and found that many things in Backbone where I've had to manually develop are readily available in Angular. Moving from Backbone to Angular has made the code much cleaner, and smaller in size. Whereas in Backbone, the code slowly became a mess with all the event listening and event triggering (probably my fault), in Angular, that has all been…

I'm really impressed as well, especially how helpful and outreaching the developers/contributors are on sites like StackOverflow. Now if the documentation would improve in some of the grayer areas, I would be really happy. Wish I knew enough to contribute.

We've been steadily working on improving the docs, and rolling out significantly improvements on a regular basis. Is there any particular part of the docs that still ails you?

Re: AngularJS 1.2.0: timely-delivery

#32

Post by camus2 »

psgibbs wrote: post #22
binofbread wrote: post #21

Earlier quoted context omitted.

I'm running into a similar issue and fairly new to angular. In fact, the tutorial I followed even set up the server calls to use the _id field when looking at a specific model (ie leagues/{{ league._id }} ). What's the proper way to go about fixing this?

You can always create functions that refer to the private element: MyObject.prototype.id = function(){return this._id;}; Which gives you: leagues/{{ league.id() }}

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.

Re: AngularJS 1.2.0: timely-delivery

#33

Post by conradfr »

treeface wrote: post #29
mathrawka wrote: post #28

With Javascript disabled the page is completely blank. edit (bringing text from comment up a level): If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page. A typical banner that I make includes the following things: - Positioned at the top via CSS and sticks there - Includes a link to http://www.enable-javascript.com - Includes a trackin…

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

Well if the fallback is ng-cloak with the css I guess he got it :)

Re: AngularJS 1.2.0: timely-delivery

#34

Post by mathrawka »

treeface wrote: post #29
mathrawka wrote: post #28

With Javascript disabled the page is completely blank. edit (bringing text from comment up a level): If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page. A typical banner that I make includes the following things: - Positioned at the top via CSS and sticks there - Includes a link to http://www.enable-javascript.com - Includes a trackin…

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

If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page.

A typical banner that I make includes the following things:

- Positioned at the top via CSS and sticks there

- Includes a link to http://www.enable-javascript.com

- Includes a tracking image so I can see how many people are coming without JS enabled

If you have a white page like this blog does, people will think your site is broken and bounce... and may never come back.

Re: AngularJS 1.2.0: timely-delivery

#35

Post by crucialfelix »

btford wrote: post #31
adamors wrote: post #18

Earlier quoted context omitted.

I'm really impressed as well, especially how helpful and outreaching the developers/contributors are on sites like StackOverflow. Now if the documentation would improve in some of the grayer areas, I would be really happy. Wish I knew enough to contribute.

We've been steadily working on improving the docs, and rolling out significantly improvements on a regular basis. Is there any particular part of the docs that still ails you?

I like the new search bar a lot. it appears to be searching within the pages themselves. so all pages are already in memory ?

http://docs.angularjs.org/api/ng.directive:ngRepeat

I search "ng-val"...

Re: AngularJS 1.2.0: timely-delivery

#36

Post by e12e »

mathrawka wrote: post #28

With Javascript disabled the page is completely blank. edit (bringing text from comment up a level): If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page. A typical banner that I make includes the following things: - Positioned at the top via CSS and sticks there - Includes a link to http://www.enable-javascript.com - Includes a trackin…

Well, I just figured out that these "blogs" (edit: blogger.com blogs) at least provide rss -- doesn't really work in w3m (it downloads the xml, rather than doing som magic and try to render it) -- but at least for me this "design" is far superior to the bloated javascript mess that they try to get you to use:

http://blog.angularjs.org/feeds/posts/default?alt=rss

Re: AngularJS 1.2.0: timely-delivery

#37

Post by e12e »

treeface wrote: post #29
mathrawka wrote: post #28

With Javascript disabled the page is completely blank. edit (bringing text from comment up a level): If you are building apps for people other than yourself, then having a banner to notify them it won't work is better than a blank page. A typical banner that I make includes the following things: - Positioned at the top via CSS and sticks there - Includes a link to http://www.enable-javascript.com - Includes a trackin…

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 adding comments via javascript and a service, or for posting blog posts and doing admin stuff. But the other reasons (user tracking etc) for having this as "an app" only detracts from the readers experience.

Re: AngularJS 1.2.0: timely-delivery

#38

Post by btford »

camus2 wrote: post #32
psgibbs wrote: post #22

Earlier quoted context omitted.

You can always create functions that refer to the private element: MyObject.prototype.id = function(){return this._id;}; Which gives you: leagues/{{ league.id() }}

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.

Re: AngularJS 1.2.0: timely-delivery

#39

Post by camus2 »

btford wrote: post #38
camus2 wrote: 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.

why didnt you think about having this feature optional? class based controllers are optional yet,because of them you introduce a feature that affect function based controllers ?

Re: AngularJS 1.2.0: timely-delivery

#40

Post by btford »

camus2 wrote: post #39
btford wrote: post #38

Earlier quoted context omitted.

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

why didnt you think about having this feature optional? class based controllers are optional yet,because of them you introduce a feature that affect function based controllers ?

> why didnt you think about having this feature optional?

Opt-in security features aren't very useful.

> class based controllers are optional yet,because of them you introduce a feature that affect function based controllers ?

That's how competing constraints work out sometimes.

We're always looking to improve though. The code is open source, so feel free to submit a PR or fork it if you disagree. :)

Post reply on HN