+1 for both (classes via optional flag for now)
I was actually considering dropping ie8 support altogether because writing 2 versions of some implementations and rewriting things that should really be there for free (JSON.stringify) is a distraction to improving RapydScript in other areas. However, after checking
http://www.theie8countdown.com and being shocked by the 10% figure (that isn't adding up btw, isn't total IE usage under 20% now?), I figured I wouldn't be cutting the cord yet. However, the more I'm thinking about, the more I think a project like ours could get away with dropping IE support if it means cleaner generated code and better compatibility between Pythonic design patterns and generated JS. Perhaps dropping IE8 support altogether makes sense.
Unfortunately between my regular work and side startup I'm not able to tackle all of this soon enough. I'll get to it eventually, but if someone else wants to tackle this sooner, I'm all for it.