Anyway, we're almost done with Angular. Markvi still lacks vi functionality, but I've already been using it regardless--turns out I found the perfect use-case, too: fixing the readmes for school projects. I may see about adding synchronized scrolling to help with that... it'd be hella nice. And I still intend to wrap the whole thing in Electron... just not until after the no-server project presentations. Turns out getting Angular to work without being served is a bitch and a half, and getting UI-Router to work at ALL is just totally pointless. Seriously, ditch that shit and go back to ngRoute. Save yourself the headache and just go back. UI-Router is buggy, weird, unstable, and pre-alpha (both in number and in quality). Its internals will be mostly rewritten before it reaches 1.0. Chances are its API will be the same (or similar), but why not stick with something that's fully functional well supported, has better compatibility, won't be breaking itself, and doesn't eat errors (seriously, try checking your console when routing seems to fail with UI-Router... you'll get nothing) while waiting for UI-Router to be ready for actual production use?
Anyway. Speaking of programming... I ought to go do that. I suppose I should build a directive and stick an 'about me' page in there or something. I'm hoping I can take some time today to play with Webpack, Grunt, Browserify, JSPM, SPM, Gulp, Duo, and Meteor just a tiny bit--trying to figure out some differences between build systems/task runners/bundlers/project-level package managers/what-have-yous/whoosey-whatsits... and maybe some thingamabobs as well.