[Plone-conference] Food for thought on AngularJS and Plone

[Robert Niederreiter]

Hi,

Am 2014-11-03 um 13:04 schrieb Timo Stollenwerk:
> Hi JC,
>
> Angular 2.0 is much more a draft than a final implementation right now,
> and the current discussion about it in the JS community (and the blog
> post you mention) is not driven by people who are very professional in
> my opinion. This is something that we have to live with (in the
> Javascript community), but I don't think we should pick that up for our
> discussions.
I think it's not very fair to disqualify valid concerns by putting the 
qualification of it's source in question
>
> Angular is open source and currently the most widely used JS framework
> out there. I don't buy the argument that we all will soon be stuck on
> Angular 1.3 without any sane upgrade path. The core principles, even in
> the draft that is currently discussed, will stay.
Migration is almost always a matter of costs and effort. As one-man-show 
i would strictly avoid using angular in a bigger project right now, 
because of it's changing target nature. If i'd have a team with 30 
developers things might be different.

 From available resources POV in the plone world right now, i would at 
least defer a move in one or another direction at least until some more 
fundamental changes are production ready.

Another aspect is that angular experiences a big hype right now - which 
might or might not end up in it's dominance. Remember the last consensus 
about a JS lib in plone -> jquerytools -> which ended up in a 
non-maintained disaster (well, i think this will not happen with angular 
due to it's way more professional origins ;)).

> Am 03.11.2014 um 11:41 schrieb JC Brand:
>> Hi everyone
>>
>> Firstly, thanks to Netsight and everyone who had a hand in organising and hosting such a wonderful conference.
>>
>> There were some earnest discussions around the usage of Javascript frameworks with Plone and about bundling certain frameworks by default.
>>
>> For those who still might believe that bundling AngularJS with Plone is a good idea, here is some food for thought.
>>
>> The planned 2.0 release of Angular contains big backwards-incompatible changes in syntax and the reaction online has been strident,
>> including this Hacker News discussion:
>> https://news.ycombinator.com/item?id=8507632
>>
>> and this article:
>> http://blog.dantup.com/2014/10/have-the-angular-team-lost-their-marbles/
>>
>> Additionally, Angular 1.3 will be supported for just 18-24 months after the
>> release of 2.0.
With respect, but bringing forward the argument of backward 
incompatibility in conjunction with plone right now is at least 
adventuresome.
>>
>> Cheerio
>> JC
>>
>>
Cheers, Robert