Comments on: Framework Overload http://arielsommeria.com/blog/2009/02/10/framework-overload/ Web Applications and Open Source Wed, 01 Feb 2012 15:17:46 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Rounding up Last Week One Day Later http://arielsommeria.com/blog/2009/02/10/framework-overload/comment-page-1/#comment-38 Rounding up Last Week One Day Later Tue, 17 Feb 2009 15:06:36 +0000 http://arielsommeria.com/blog/?p=61#comment-38 [...] Application development with Adobe Flex”, and now loves it. Ariel, on the other hand, feels overloaded by all these [...] [...] Application development with Adobe Flex”, and now loves it. Ariel, on the other hand, feels overloaded by all these [...]

]]> By: admin http://arielsommeria.com/blog/2009/02/10/framework-overload/comment-page-1/#comment-31 admin Fri, 13 Feb 2009 21:04:20 +0000 http://arielsommeria.com/blog/?p=61#comment-31 Hi Sekhar, I see what you mean. From a developer's point of view it's a bit of an annoying trend, but from a job hunter's point of view it's another keyword the HR folks can add to their list. The trend does have an advantage, though: for those who like frameworks there's a lot of competition so the quality should go up. Hi Sekhar,
I see what you mean. From a developer’s point of view it’s a bit of an annoying trend, but from a job hunter’s point of view it’s another keyword the HR folks can add to their list. The trend does have an advantage, though: for those who like frameworks there’s a lot of competition so the quality should go up.

]]> By: Sekhar Ravinutala http://arielsommeria.com/blog/2009/02/10/framework-overload/comment-page-1/#comment-30 Sekhar Ravinutala Fri, 13 Feb 2009 18:41:11 +0000 http://arielsommeria.com/blog/?p=61#comment-30 I think a lot of folks are turning to Cairngorm because it's the hot thing and they'll likely need it to land the next job/gig. Plus, it doesn't hurt that Adobe is aggressively pushing it. I.e., it's more of a business attraction than a technical one. BTW, it's not like you have to learn a lot of frameworks - it's down to mainly Cairngorm and PureMVC for all practical purposes AFAIK. I think a lot of folks are turning to Cairngorm because it’s the hot thing and they’ll likely need it to land the next job/gig. Plus, it doesn’t hurt that Adobe is aggressively pushing it. I.e., it’s more of a business attraction than a technical one. BTW, it’s not like you have to learn a lot of frameworks – it’s down to mainly Cairngorm and PureMVC for all practical purposes AFAIK.

]]> By: admin http://arielsommeria.com/blog/2009/02/10/framework-overload/comment-page-1/#comment-29 admin Fri, 13 Feb 2009 09:01:00 +0000 http://arielsommeria.com/blog/?p=61#comment-29 Hi Darren, thanks for answering. I'm working on a big project at the moment, I wouldn't know how many lines of code, but we're talking 3 developers full time for six months. We have an 'application manager' for all our centralised needs, that does a bit of what you mention with cairngorm. I wouldn't say we've reinvented the wheel, because one thing we don't do is impose MVC everywhere for everyone as the ultimate design pattern that kills like it seems all of the above mentioned trendy frameworks. An article I like on the question : http://www.nooranch.com/synaesmedia/wiki/wiki.cgi?ModelViewController So I guess we get a more supple approach, but less standardised. I pity the developer that would have to dive in at the deep end of our code, though, so standardisation would be nice. Hi Darren,
thanks for answering.
I’m working on a big project at the moment, I wouldn’t know how many lines of code, but we’re talking 3 developers full time for six months. We have an ‘application manager’ for all our centralised needs, that does a bit of what you mention with cairngorm. I wouldn’t say we’ve reinvented the wheel, because one thing we don’t do is impose MVC everywhere for everyone as the ultimate design pattern that kills like it seems all of the above mentioned trendy frameworks. An article I like on the question : http://www.nooranch.com/synaesmedia/wiki/wiki.cgi?ModelViewController
So I guess we get a more supple approach, but less standardised. I pity the developer that would have to dive in at the deep end of our code, though, so standardisation would be nice.

]]> By: Darren http://arielsommeria.com/blog/2009/02/10/framework-overload/comment-page-1/#comment-28 Darren Fri, 13 Feb 2009 00:10:49 +0000 http://arielsommeria.com/blog/?p=61#comment-28 How big are your projects? A few thousand lines, ten thousand lines, a hundred thousand lines? I'm probably in the middle and there is no way I would ever consider developing a project without Cairngorm but I admit that in some cases a custom one would do just as well. There's two advantages that I see: 1. Code organisation. Cairngorm uses many common J2EE patterns. If you're a new developer on a project, you don't need to know Cairngorm to know where you might find a bug. Commands are in the command folder, events are in the event folder, etc. I also add a folder for responders to separate them out. 2. I use Cairngorm for its simple event management system. You want something to happen, say initiate a database call, from *any* component in your app. You fire off the appropriate Cairngorm event, the FrontController grabs it and passes it to the appropriate command. Too easy and (reasonably) loosely-coupled. Plus, if you add the Universal Mind extensions to Cairngorm, you get a solid view notification system and command sequencing to boot. Sure I could write a custom framework that does all of the above but personally I'd end up with something like Cairngorm anyway (with the addition of DI) so why bother? If you don't use all of the above in every project like I do, then maybe a framework isn't appropriate or necessary for you. How big are your projects? A few thousand lines, ten thousand lines, a hundred thousand lines? I’m probably in the middle and there is no way I would ever consider developing a project without Cairngorm but I admit that in some cases a custom one would do just as well. There’s two advantages that I see:

1. Code organisation. Cairngorm uses many common J2EE patterns. If you’re a new developer on a project, you don’t need to know Cairngorm to know where you might find a bug. Commands are in the command folder, events are in the event folder, etc. I also add a folder for responders to separate them out.

2. I use Cairngorm for its simple event management system. You want something to happen, say initiate a database call, from *any* component in your app. You fire off the appropriate Cairngorm event, the FrontController grabs it and passes it to the appropriate command. Too easy and (reasonably) loosely-coupled. Plus, if you add the Universal Mind extensions to Cairngorm, you get a solid view notification system and command sequencing to boot.

Sure I could write a custom framework that does all of the above but personally I’d end up with something like Cairngorm anyway (with the addition of DI) so why bother? If you don’t use all of the above in every project like I do, then maybe a framework isn’t appropriate or necessary for you.

]]>