These are chat archives for opal/opal
I just noticed that, in Chrome/v8, instantiation of Ruby objects is unable to be optimized by the VM because it uses the
arguments array (via
*args in Opal): https://github.com/opal/opal/blob/247d921f43e2fcdec47405c1c2a38472fc89ca71/opal/corelib/class.rb#L42
Safari doesn't seem to have any trouble with it (it renders Clearwater apps 3x as fast as Chrome when I don't use render caching), but in rendering a pretty large virtual DOM several times in Clearwater just now, I spent 13.24% of my CPU time in
Class#new. I haven't opened an issue yet because I don't know if there's any way around it. Anyone have any ideas?