Comments on: I’m Cairngorm!

 http://flexblog.faratasystems.com/2009/11/17/i%e2%80%99m-cairngorm%e2%80%a8%e2%80%a8 A blog about our experience with Adobe Flex Sun, 15 Jan 2012 16:29:29 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: shant adam http://flexblog.faratasystems.com/2009/11/17/i%e2%80%99m-cairngorm%e2%80%a8%e2%80%a8/comment-page-1#comment-92154 shant adam Mon, 21 Mar 2011 16:03:19 +0000 http://flexblog.faratasystems.com/?p=488#comment-92154 Hold your horses Gents, You have a choice! I am with disagreement with the comments written in this blog for the following reasons: 1- Cairngorm 2 is here to stay. But there will be no further support for it. Version 2.2 will be the last release version. 2- Cairngorm 3 is where Adobe will put their focus on instead. Creating a library of Utils that help you resolve many patterns that are redundant from one Flex project to next by introducing best practice methods. 3- Cairngorm 3 does not impose on anyone to use Parsley by force. Instead it compliments your open sourceMVC architecture of choice -i.e. Cairngorm 2, Parsley, Sprint ActionScript, Swiz, PureMVC. I invite you to visit the link below to better get informed: http://opensource.adobe.com/wiki/display/cairngorm/CairngormTools Hold your horses Gents,

You have a choice!

I am with disagreement with the comments written in this blog for the following reasons:
1- Cairngorm 2 is here to stay. But there will be no further support for it. Version 2.2 will be the last release version.
2- Cairngorm 3 is where Adobe will put their focus on instead. Creating a library of Utils that help you resolve many patterns that are redundant from one Flex project to next by introducing best practice methods.
3- Cairngorm 3 does not impose on anyone to use Parsley by force. Instead it compliments your open sourceMVC architecture of choice -i.e. Cairngorm 2, Parsley, Sprint ActionScript, Swiz, PureMVC.

I invite you to visit the link below to better get informed:
http://opensource.adobe.com/wiki/display/cairngorm/CairngormTools

]]> By: Yakov Fain http://flexblog.faratasystems.com/2009/11/17/i%e2%80%99m-cairngorm%e2%80%a8%e2%80%a8/comment-page-1#comment-50402 Yakov Fain Fri, 15 Jan 2010 02:42:41 +0000 http://flexblog.faratasystems.com/?p=488#comment-50402 Thomas, You jump right into technical details of what specific framework has been included into a foggy notion "Cairngorm 3". If what was known as Cairngorm framework is/was a worthwhile product, why not investing some money and releasing a new version of it? When was the last new release of the Cairngorm 2? If, for any reason, Adobe Consulting decided to discontinue it, why not explaining people the reasons so they don't repeat mistakes? They don't have guts to admit that using Cairngorm 2 adds very little value to any project and actually makes development of the enterprise projects more expensive. As to selection of Parsely as opposed to Swiz or Mate... Be positive! At least they didn't select PureMVC, which would be a lot more damaging and costly! Thomas,

You jump right into technical details of what specific framework has been included into a foggy notion “Cairngorm 3″. If what was known as Cairngorm framework is/was a worthwhile product, why not investing some money and releasing a new version of it? When was the last new release of the Cairngorm 2?

If, for any reason, Adobe Consulting decided to discontinue it, why not explaining people the reasons so they don’t repeat mistakes? They don’t have guts to admit that using Cairngorm 2 adds very little value to any project and actually makes development of the enterprise projects more expensive.

As to selection of Parsely as opposed to Swiz or Mate… Be positive! At least they didn’t select PureMVC, which would be a lot more damaging and costly!

]]> By: Thomas Burleson http://flexblog.faratasystems.com/2009/11/17/i%e2%80%99m-cairngorm%e2%80%a8%e2%80%a8/comment-page-1#comment-50049 Thomas Burleson Wed, 13 Jan 2010 03:43:42 +0000 http://flexblog.faratasystems.com/?p=488#comment-50049 Yakov, I was completely stunned when I read that Cairngorm 3 advanced features required the Parsely framework. Have you seen the Parsley framework. Talk about a learning curve. Good lord. When Swiz is rapidly becoming the defacto standard for Flex IOC solutions and future releases of Cairngorm should consider integration of SWIZ and Cairngorm/Cairngorm Extensions as a migration to Cairngorm 3... instead Parsley is now required. Who the hell has heard of Parsely. And the Parsley docs and code have a HUGE learning curve. Oh yeah... I can convince flex newbies to learn Parsley and Cairngorm. Right... what a brain fart! The Adobe Consulting team did a truly abysmal job of including the Cairngorm community experts in the "next generation" process. Instead - behind closed doors - they collaborated without most of the experts (that I know of) and presented a decision to use Parsley and propose best practices based on their experience ONLY. This was a proverbial "flip the middle finger" to all of us in the field. I consider this a poor attempt by the Adobe Consulting Group to promote their own solutions without regard to the community. I am completely disgusted. The politics suck. I am now considering using SWIZ as my MVC/IOC framework of choice. And that is extreme for me when my peers know that I have been a Cairngorm evangelist since Cairngorm .99. Yakov,
I was completely stunned when I read that Cairngorm 3 advanced features required the Parsely framework. Have you seen the Parsley framework. Talk about a learning curve. Good lord.

When Swiz is rapidly becoming the defacto standard for Flex IOC solutions and future releases of Cairngorm should consider integration of SWIZ and Cairngorm/Cairngorm Extensions as a migration to Cairngorm 3… instead Parsley is now required. Who the hell has heard of Parsely. And the Parsley docs and code have a HUGE learning curve. Oh yeah… I can convince flex newbies to learn Parsley and Cairngorm. Right… what a brain fart!

The Adobe Consulting team did a truly abysmal job of including the Cairngorm community experts in the “next generation” process. Instead – behind closed doors – they collaborated without most of the experts (that I know of) and presented a decision to use Parsley and propose best practices based on their experience ONLY. This was a proverbial “flip the middle finger” to all of us in the field.
I consider this a poor attempt by the Adobe Consulting Group to promote their own solutions without regard to the community.

I am completely disgusted. The politics suck. I am now considering using SWIZ as my MVC/IOC framework of choice. And that is extreme for me when my peers know that I have been a Cairngorm evangelist since Cairngorm .99.

]]>