I don't; I don't even use "git" at all.
I'm guessing you still use some sort of version control.

The one shim is a simple reworked implementation of a popular shim. I hate paying for stuff I don't need, and I refuse to automatically play anything.
Very interesting. Wish I could see the code. I agree with the paying sentiment. I usually get all my shims and libraries from github, and also try to help give back by putting my own solutions out there for free as well.

I know. I am indeed crazy, but I'm not doing the Canvas because I care about old browsers. I'm just playing around as part of my reeducation in Javascipt because until somewhat recently I haven't touched anything web development in a long time.
Crazy maybe, but I also like to build things from scratch... which I get nudged for at work. My boss is always saying to use a library first and program it only if there isn't one. Which I can agree he's probably right. Usually if a library does something I don't understand I really like to try to implement something myself so I can get a full grasp of the problem and what it took to solve it.

You seem to have quite a firm grasp on it for not touching it in years. You probably know more about JavaScript than 3/4 of our web developers at work (its still a small startup). Not too surprising though you have a solid understanding of programming concepts in general the rest just ends up being syntax differences.

Anyways if you start anything interesting for free time work I would be interested in collaborating. I have enjoyed this thread very much as about 2 1/2 years ago I moved from C++ to JavaScript as my main language and I just somehow fell in love with it.

As for the yield stuff I totally get how it works, but Its just one of those things.. I'm waiting until it occurs to me that I SHOULD use it in this situation. When it comes to coding at work I try to keep my spent innovation points to a minimum and just keep to clean testable code.

The experimental stuff I save for my free time and once I have a full grasp I'll bring the ideas back around into my workflow. Or decide the tech isn't ready yet and not use it at all.

I just recently went through this with polymer. I thought the library and web components concept in general was amazing, and for the most part it worked like it should. All my hopes fell apart when we started building polymer web components into hybrid (ios, and android) apps, and shadow dom selectors started to splat the entire application. I'll be keeping a close eye on the project though once it actually hits alpha or beta I'll try using it again. I think the future of web programming will change dramatically when web components and harmony are just the normal accepted releases.