after a long hiatus back to talk about frameworks

Frameworks exist because they help solve problems - typically problems that are common and many people have experienced in the past. These problems are not going to go away. Yes, a particular framework X may go away, but learning it will not be a waste of time as you will gain the experience of how it can help you solve those problems. Personally I think you are making a mistake if you just ignore them. To be clear, I'm not saying every project needs a framework. Heck no. You want to ensure you actually have problems before you go trying to solve them. ;) But focusing on 'which framework is more popular' and 'which framework may go away' seems a bit silly. As it stands - the "big boys" in our world have been around for years: Model-Glue, Mach II, ColdBox. Even FW/1 is a bit old now. I don't think you have to worry about them going away anytime soon. > > But my approach to frameworks has been to 'wait and see'. Because I don't like wasting my time. I need to do something on a daily basis other wise it wont stick. > > I delayed learning any Framework and then just learned fusebox at a job/contract. > > I was going to ask, "which frameworks are the most popular" in terms of actual employment statistics but even then, it might all be a waste of time if my next contract doesn't use ( framework x,y, or z ). So I think I'll continue conserving my energy and just focus on CF. Maybe checkout FW/1 for my own projects from what a few here have said about it. didn't find the documention all that great though. > > > > >