That would be right if huge applications where created in a consistent and homogeneous way during all "development life". If the app is tiny there's more opportunities that experienced programers make a good work and code in the overall.
When the app, the team, the code grows over years, more difficult is to see something in that way. For example, we have a product started in Flex 4 alpha, back in 2009. We started with a framework and API that was not finished, we had less experience than we had today, experiment and learn lots of things in this 4/5 years. To get all this knowledge in our app, we need to invest time to upgrade different pieces at different time. Today we continue evolving the code base, to simplify old code, readapt, to new best practices incorporated, and so on, through all codebase, trying to not break things. This is a huge task not all people and companies want to perform...take into account that this is a project with 160+ projects (80+ flex), so changes and improvements in all code base could take a year to reach all modules. To rewrite this kind huge product in FlexJS...I think one day we could get it possible, but that implies we continue evolving and preparing our app, and converge with FlexJS some time in the future when flexJS would be more robust and finished, and event there it would be a monumental task since the product still continue growing.... So it's possible...yes, in theory, but I would love to see how many real cases we could get (huge real cases) 2013/7/17 OmPrakash Muppirala <bigosma...@gmail.com> > > About folks rewriting code...well, I certainly does not see people > > migrating old applications from Flex 4.x to FlexJS, Since there will be > > huge diferences that will make the task utopic. I expect flex developers > > start working in FlexJS right from the first day for new projects due to > > lots of similarities. But a global app rewrite...that's another > story...at > > least for huge codebases (maye tiny apps could be reach this scenary in > > time, money and developer effort). > > > > > > > Not necessarily. I try my best to keep the (application) Model and > Controller separate from my View classes as much as possible. The use of > frameworks like Parsley, Swiz etc. helps to keep this kind of separation. > > In projects where this is true, it will be an easier migration path from > Flex 4.x to FlexJS since we will be resusing the Model and Controller code > almost a 100% > > At least, this is what I am hoping for. Any reason to believe I am > mistaken? > > Thanks, > Om > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
