Running their 3D walkthrough demo and then comparing it to the JavaScript
original shows just how much overhead Brython introduces. Dragging an entire
meta-layer along just so you can write a bit of code in a familiar setting
sounds like a poor choice to me.

Running their 3D walkthrough demo and then comparing it to the JavaScript original shows just how much overhead Brython introduces. Dragging an entire meta-layer along just so you can write a bit of code in a familiar setting sounds like a poor choice to me.

Hmm ... does aIEeee still support client-side vbscript?

Yes, it is. I am glad they could settle on a "standard", but if you want to write for aIEeee, you might be pushing too far with that Q-Tip and be damaging your brain (and not thinking the traction behind the folks that optimize Brython have not overcome quite a few optimization hurdles before. They are thinking bigger than most die on the vine projects that I have seen in that space recently. They have fixed many performance killers and have optimized the code on the old side via the tickets. Not sure why they moved to BitBucket recently, but there used to be quite an active group list. Much can be done when many folks have shovels.