3 ms·
As an ex-Actionscript, now-JS programmer a lot of this resonates with me. After the move, I missed a lot of things - mostly the productivity stuff like type-sa
by ender7 14y ago
As an ex-Actionscript, now-JS programmer a lot of this resonates with me.
After the move, I missed a lot of things - mostly the productivity stuff like type-safe renaming; intellisense; clickable function names. Also the presence of a real module system, and the fact that the compiler would catch my typos.
However, after comparing my two codebases (the original one in Actionscript and the new on in Javascript), I can't help but be amazed at all the damn boilerplate that's in my Actionscript. I ended up spending an enormous amount of time specifying interfaces and careful inheritance chains so that all of my type annotations would be compatible and safe. Did I need to do all that? Probably not, but the design of the language certainly encouraged me to do so. I can't help but wonder what I could have done with that time - especially considering the fact that my JS codebase doesn't seem to have more bugs or worse stability.
Would I switch back if I could? I'm not sure.
I can't help but think that there's a real opportunity for a Coffeescript-like language with a module system, clean class syntax, and some Go-like features such as Go interfaces and type inference, plus manual type annotations when necessary.
- georgemcbay 14y ago"I can't help but think that there's a real opportunity for a Coffeescript-like language with a module system, clean class syntax, and some Go-like features such as Go interfaces and type inference, plus manual type annotations when necessary." haxe meets a lot of these criteria and has been around for a while.
- jdonaldson 14y agoseconding this. Also, a new version of the haxe compiler was just released that is geared towards supporting new js features and cleaner integration: http://haxe.org/download http://haxe.org/download