4 ms·
> "Does it make a difference though?" Yes, a million times yes. > "I think oit's plenty fast enough to run most non-game apps." Right, and that's the same ar
by potatolicious 17y ago
> "Does it make a difference though?"
Yes, a million times yes.
> "I think oit's plenty fast enough to run most non-game apps."
Right, and that's the same argument used by a bajillion people before someone else came and ate their lunch (including Apple!). Nokia had a functional, but slow, sluggish, and substandard user experience on their phones. Apple came in and stomped all over that with their slick, super-fast, snappy UI.
IE was functional - sites worked and all - but was slow and bloated when Firefox came along and blew it out of the water in every way that mattered.
Performance always matters. When you're making the "meh, good enough" argument, you're in a prime position to be taken out spectacularly by a competitor who cares.
The complexity of JS-based webapps is going to get higher, not lower. A web-browsing device that performs JavaScript badly is a BFD.
- mechanical_fish 17y agoThe complexity of JS-based webapps is going to get higher, not lower. Only if that's the winning tradeoff. If, in fact, "ability to run well on a mobile device that is desperate to conserve battery power" turns out to be a more valuable trait in a particular segment of the market than "has lots and lots of complex JS logic that takes power to run" then software will evolve accordingly.
- ugh 17y agoIt certainly matters but it might just be the right trade-off in this situation. Or not. I think nobody would argue that performance doesn’t matter, it’s just that you can’t always have everything and then you better pick the right stuff. Apple probably thinks that JS performance is good enough. For now. And that’s a attitude I would have no problems with.
- potatolicious 17y ago> "It certainly matters but it might just be the right trade-off in this situation. Or not." In principle, yes, but if you're marketing a device that is some kind of ultimate web-browsing machine, and you have to crank down JS performance to hit battery life... then the technology for your device isn't there yet. Apple has made the claim forever that they don't execute until the right technologies are there (an argument they repeated for iPad) - and have frequently accused competitors of launching something before it's ready (IMHO, a valid point). This would seem to fit into that case - assuming JS performance is deliberately low as a trade for battery life.