4 ms·
I think it much depends on how much work you're doing. If you're just viewing a static 3D model and doing some scaling or rotation, it's not so bad but if you'r
by cheez 16y ago
I think it much depends on how much work you're doing. If you're just viewing a static 3D model and doing some scaling or rotation, it's not so bad but if you're adding/removing/translating objects, it's going to be ass slow in JavaScript. One's best bet is probably to write your code procedurally and hope that V8 can compile it to machine code really well.
WebGL is really good and it's only going to get better as long as the creators of the browsers make enough money to subsidize the optimization.
It may be that Chrome/V8 need to start using LLVM.
- daeken 16y ago> It may be that Chrome/V8 need to start using LLVM. LLVM is far too heavy to be used in such a situation -- page load times would rise dramatically. Really, V8 just needs to start doing hot spot optimizations. Do a quick first pass like they're doing now, then incrementally optimize away the hot spots. If I had to take a guess, I'd say that'll be coming in the next year, in some form or another.
- riffraff 16y agoI believe, hot spot optimization is what the new crankshaft infrastructure was about, or are you thinking of something else?
- daeken 16y agoAh yes, I forgot all about that. Guess it's not a prediction if it's already come true. Anyway, more focus will be put on such things, as we're about as far along as we can get with the initial fast compilation.
- cheez 16y agoI'm used to it. I invented alphanumeric pagers in high school about 5 years after they were available (I had no idea they existed...)