ECMA's a good choice, considering web developers should already be familiar with it, and (I think it's safe to say) it's a far better language than PHP.
A different language running on a different backend means making a clean break with all your old code. But anyone developing PHP has already made a decision to not make a clean break, otherwise he'd be using rails, node.js, django, clojure, catalyst, you name it.
What I'd like (and maybe I'll have to write if it doesn't already exist) is an ECMAScript-to-PHP5 compiler. Targeting the JVM is fine I suppose, but targeting mod_php5.c would mean PHP developers could dip their toes in more easily.
A different language running on a different backend means making a clean break with all your old code. But anyone developing PHP has already made a decision to not make a clean break, otherwise he'd be using rails, node.js, django, clojure, catalyst, you name it.
What I'd like (and maybe I'll have to write if it doesn't already exist) is an ECMAScript-to-PHP5 compiler. Targeting the JVM is fine I suppose, but targeting mod_php5.c would mean PHP developers could dip their toes in more easily.