>you may find after the re-write your framework of choice moves on without you and you're back to square one A simple guideline might be to only roll a new fra

>you may find after the re-write your framework of choice moves on without you and you're back to square one A simple guideline might be to only roll a new framework if it's significantly advancing the state of the art WRT modern frameworks. That is, addressing conceptual weaknesses or the like. OTOH, if it only offers incremental improvement and/or could easily be adapted by a current framework, then probably not worth the effort. So, we're talking paradigm shifts here. For instance, we probably don't need any more HTML template-driven, reactive frameworks.