- Anyone that tells you GWT is an option is a dirty liar.
- Angular.js. Meh… pass, even though it’s the new hotness.
- Polymer (pre-alpha) <== Go learn this now. It’s the future.
It’s great and I’ve used it for a couple years and it has served me well. It’s a bit convoluted, but it works, and for a while was the only solid choice.
IMO, the days of requirejs are over, and now we have browserify v2.
Browserify runs on node.js, which means you get all the fancy features of node — like mocha, headless browsers, DOM… oh, and you get the simple var module = require(‘module’) syntax. Yum.
Browserify requires a build step (requirejs doesn’t), but it’s only marginally annoying.
There is also yeoman, which is for “managing workflow” which doesn’t exactly compare, but it can get you to the same ends and includes a package manager. It’s a great place to start if you need to just-build-an-internal-html5-mobile-app.
I’ve used yeoman, but don’t use it anymore. I find it easier to just build my own workflow out since it almost certainly changes between projects anyway. Plus now that grunt doesn’t ship with since v1, I find it a bit cumbersome to set up…. maybe I’m crazy.
Yeoman also works well with angular. In fact — I’d say it’s the best way to get started with angular.
My favorite part of yeoman is it ships with livereload, but you can use livereload w/o yeoman.
Am I forgetting anything?
Oh yeah… a note about angular
I question whether there is too much automagic going on — or if it’s all necessary.