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

AngularJS 1.2.0-rc1 released

blog.angularjs.org

Post reply on HN
Print view View original

1–10 of 39 posts

Re: AngularJS 1.2.0-rc1 released

#2

Post by jacques_chester »

I know this is the wrong place to vent, but it would be nice if ngRepeat properly supported recursive data structures without having to write new directives.

Edit: and yes, I did actually crack open the source to see if I could make that change. In places it's ... pretty densely written. It seems to me that at least checking to see if an array has any elements and aborting if it's empty would go some of the way to stopping the locking-up problem, but I couldn't work out if that was so.

So like everyone else I have a frankenstein pair of directives to achieve the same thing.

Re: AngularJS 1.2.0-rc1 released

#3

Post by sergiotapia »

'spooky-giraffe'? :/

What happened to the cool release names such as Longhorn, Maverick, Feisty Fawn, et al? These days libraries have such funky names, kind of odd. There's a ruby gem out there that's called Steak. Yep, Steak.

Re: AngularJS 1.2.0-rc1 released

#4

Post by dchuk »

sergiotapia wrote: post #3

'spooky-giraffe'? :/ What happened to the cool release names such as Longhorn, Maverick, Feisty Fawn, et al? These days libraries have such funky names, kind of odd. There's a ruby gem out there that's called Steak. Yep, Steak.

I'm pretty sure Angular uses these funky release names sarcastically.

Re: AngularJS 1.2.0-rc1 released

#5

Post by phaedryx »

sergiotapia wrote: post #3

'spooky-giraffe'? :/ What happened to the cool release names such as Longhorn, Maverick, Feisty Fawn, et al? These days libraries have such funky names, kind of odd. There's a ruby gem out there that's called Steak. Yep, Steak.

In context, there are lots of acceptance test frameworks for ruby, e.g. cucumber, spinach, and turnip. Steak is great marketing. Why use cucumber when you could have steak?

Re: AngularJS 1.2.0-rc1 released

#6

Post by tyre »

Using Angular was a huge pleasure for developing a Chrome Packaged App in every way but one.

Documentation.

It isn't sexy to write docs; as a developer you don't get that feeling of 'shipping code', but it is one of the most important parts of an open source library.

Knowing that your question is always a google away (not a 'I hope someone asked this on StackOverflow' away) is important and I hope they improve in this arena.

Re: AngularJS 1.2.0-rc1 released

#8

Post by jacques_chester »

tyre wrote: post #6

Using Angular was a huge pleasure for developing a Chrome Packaged App in every way but one. Documentation. It isn't sexy to write docs; as a developer you don't get that feeling of 'shipping code', but it is one of the most important parts of an open source library. Knowing that your question is always a google away (not a 'I hope someone asked this on StackOverflow' away) is important and I hope they improve in thi…

I concur on the documentation. I spend as much time reading the code to understand the documentation as I do reading documentation to understand code. That seems perverse to me.

Re: AngularJS 1.2.0-rc1 released

#9

Post by leetrout »

I'm very happy to see this dropping. Specifically the rewrite of ngAnimate and changing to saner (IMO) class conventions `.foo.ng-enter` and `.foo.ng-enter-active` instead of the previous use of `.foo-enter-setup` and `.foo-enter-start`.

Re: AngularJS 1.2.0-rc1 released

#10

Post by saiko-chriskun »

tyre wrote: post #6

Using Angular was a huge pleasure for developing a Chrome Packaged App in every way but one. Documentation. It isn't sexy to write docs; as a developer you don't get that feeling of 'shipping code', but it is one of the most important parts of an open source library. Knowing that your question is always a google away (not a 'I hope someone asked this on StackOverflow' away) is important and I hope they improve in thi…

am I the only one that has never had an issue with angular's docs? :P
Post reply on HN