Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - The Evolution of Web Development for Mobile Devices->

Submitted by
CowboyRobot writes "Nicholas Zakas (author of "Maintainable JavaScript" O'Reilly, 2012 among others) has an article at the ACM describing how Web development for mobile devices has improved over the years and also why it still kind of stinks. He focuses on the latency between request and response that is built in to the model of the mobile Web as well as on how to improve performance by reducing http requests and redirects. He also gets into detail about how JavaScript is so slow on mobile. "Another aspect of JavaScript on mobile devices is the associated performance cost. Unlike desktop computers, mobile devices have batteries that can get drained by radios (cellular, Wi-Fi, Bluetooth), network access, and executing code such as JavaScript. Any time code is executed, the CPU uses power; therefore, more time spent executing code means more power used. Running JavaScript drains batteries more quickly.""
Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

The Evolution of Web Development for Mobile Devices

Comments Filter:

"I may kid around about drugs, but really, I take them seriously." - Doctor Graper