31–40 of 84 posts
A major caveat is, it's still JavaScript so the performance vary according to the browser apart from other variables. Benchmark on iPad Air 2 iOS 10.3.2 is close for both chrome and safari. Safari CPU: 6.110s ±1.9% GPU: 0.487s ±1.0% (12.55 times faster!) Chrome 59 CPU: 4.454s ±51.8% GPU: 0.483s ±0.9% (9.22 times faster!) Project looks promising though, congratulations to the team.
A major caveat is, it's still JavaScript so the performance vary according to the browser apart from other variables. Benchmark on iPad Air 2 iOS 10.3.2 is close for both chrome and safari. Safari CPU: 6.110s ±1.9% GPU: 0.487s ±1.0% (12.55 times faster!) Chrome 59 CPU: 4.454s ±51.8% GPU: 0.483s ±0.9% (9.22 times faster!) Project looks promising though, congratulations to the team.
If this example proves anything, it's that the GPU result is the same in both browsers.
A major caveat is, it's still JavaScript so the performance vary according to the browser apart from other variables. Benchmark on iPad Air 2 iOS 10.3.2 is close for both chrome and safari. Safari CPU: 6.110s ±1.9% GPU: 0.487s ±1.0% (12.55 times faster!) Chrome 59 CPU: 4.454s ±51.8% GPU: 0.483s ±0.9% (9.22 times faster!) Project looks promising though, congratulations to the team.
A major caveat is, it's still JavaScript so the performance vary according to the browser apart from other variables. Benchmark on iPad Air 2 iOS 10.3.2 is close for both chrome and safari. Safari CPU: 6.110s ±1.9% GPU: 0.487s ±1.0% (12.55 times faster!) Chrome 59 CPU: 4.454s ±51.8% GPU: 0.483s ±0.9% (9.22 times faster!) Project looks promising though, congratulations to the team.
A major caveat is, it's still JavaScript so the performance vary according to the browser apart from other variables. Benchmark on iPad Air 2 iOS 10.3.2 is close for both chrome and safari. Safari CPU: 6.110s ±1.9% GPU: 0.487s ±1.0% (12.55 times faster!) Chrome 59 CPU: 4.454s ±51.8% GPU: 0.483s ±0.9% (9.22 times faster!) Project looks promising though, congratulations to the team.
Apple does not allow for real Chrome on iOS, so Chrome on iOS is just a wrapper around Safari.
Earlier quoted context omitted.
I'd think pegging CPU/GPU at 99% would be even more of a turn off than banner ads. Especially on mobile where it'd drain your battery. Interesting thought though. I wonder if Windows or MacOS had some hidden process that did bitcoin mining at ~5% CPU, how much that would be worth worldwide.
Okay, Bill Gates alone is worth more than twice all the bitcoin ever mined. Apple is worth almost 20x that. So, per risk/reward, probably not a great strategy for either company. https://howmuch.net/articles/worlds-money-in-perspective .
Next steps: A computational graph based deep learning system with a Tensorflow like API on Javascript/Node lala-land. https://github.com/tqchen/tinyflow would be a great showcase (and useful) project to port for Gpu.js
Things like this make me fear banner ads mining bitcoins (not that they aren't already).
Fuck advertising.
What I learned: Not to make a compiler during a hackathon.
Is js via gpu (WebGL i assume) already efficient enough to make the concept of "computation time instead of banners" finally viable?