Given the discussion some of us in the CF community have been having lately about the affect alternative CFML engines have on CF as a whole, I thought this article about what's going on in the J2EE world these days was pretty interesting:Alternative Frameworks: Bad for J2EE ... or Good?On one front, the commoditization of things like app servers may lead to the big J2EE players to abandon their commercial offerings if they're no longer profitable. (I don't agree with this argument at all, but it's one that's frequently made.)On another front, many in the Java world are challenging the complexities of J2EE and coming up with alternative frameworks such as Spring (dev framework) and Hibernate (persistence framework). These alternatives are more lightweight and easier to use than their heavier counterparts, but some argue that it starts to water down the standards.On the CF side of the world, these arguments are very analogous to the situation with Macromedia's ColdFusion and New Atlanta's BlueDragon. Some think having alternative CFML engines makes CF less proprietary and strengthens CF overall, while others feel that it bifurcates CF and therefore weakens it. What are some of your thoughts?