4 ms·
JavaScript relative performance is still a bit meaningless right now, because market share still counts for more. If you were to write a web app that required
by makecheck 17y ago
JavaScript relative performance is still a bit meaningless right now, because market share still counts for more. If you were to write a web app that required the speed of Chrome, it would still suck for most visitors.
This performance mainly showcases Google's platforms (e.g. some netbook with Chrome OS?). Google can write bleeding-edge, speed-dependent web apps, since the whole user experience is based on Chrome.
For everyone else, this doesn't help much yet, but it does mean that the future is bright. Historically Apple and Mozilla have responded well to friendly jabs in benchmarks, so they'll surely work hard to make the next one look much better. And that's when the real fun begins. :)
- megaduck 17y agoActually, these numbers are quite significant to anybody doing mobile web development. Android, iPhone, and WebOS all use Webkit-based browsers. Javascript performance is particularly relevant for Palm, since all of their applications are JS based. There's also certain audiences (like HN), where IE is a fractional minority. IE is still keeping us back in the overall market, but there are certain emerging niches where these benchmarks really matter.