Timeline for Did the gradual shift in methodology of writing code affect system performance? And Should I care?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2014 at 16:11 | comment | added | gbjbaanb | There's more to performance than raw CPU benchmarks. My Android phone works fine, except when the AV is scanning an update and then it appears to just hang for longer than I like, and its a quad-core 2Gb RAM model! Today bandwidth (whether network or memory) is probably the main bottleneck. Your superfast CPU is probably twiddling its thumbs 99% of the time and the overall experience is still poor. | |
| Mar 4, 2014 at 7:20 | comment | added | Jan Hudec | @JeffO: For what it's worth, the virtual machine used on Android is pretty bad. According to benchmarks it might be an order of magnitude slower than native code (while the best of breed is usually just a bit slower). Guess what, nobody cares. Writing the application is fast and the CPU sits there twiddling it's thumbs and waiting for user input 90% of time anyway. | |
| Feb 26, 2014 at 23:47 | comment | added | mattnz | @JeffO : I disagree - Mobile devices with quad core processors is now normal, performance (especially as it impacts battery life), while a concern, is less important than stability. A slow mobile phone or tablet gets poor reviews, one that is unstable gets slaughtered. Mobile apps are very dynamic, changing almost daily - the source has to keep up. | |
| Feb 26, 2014 at 16:05 | comment | added | JeffO | I agree, but mobile device are becoming so popular that I think they are a large exception. Although the processing power is increasing, you can't build an iPhone app and expect to be able to add memory like you can on a webserver. | |
| Feb 26, 2014 at 10:48 | history | answered | Rory Hunter | CC BY-SA 3.0 |