News for hackers. Stuff that matters.
Re:Our best practices are killing mobile web performance by JustSomeNobody on Saturday May 21, 2016 @07:03AM (#11744239)
> This is and should always be the default. It's the heavy content experiences that should be explicitly initiated by the user.

This is the correct solution. Wanting the phones to send speed and cap info is just ... looking for a bandage.

Re:Our best practices are killing mobile web performance by blowski on Saturday May 21, 2016 @08:19AM (#11744432)
With my unlimited fibre connection on my MacBook Pro, I'd prefer to have a web experience that looks amazing - even if it's 5MB per page. Saying 'the smallest amount of data possible' is a truism, but it's not particularly helpful.
Re:Our best practices are killing mobile web performance by douche on Saturday May 21, 2016 @08:26AM (#11744443)
I'd still like unadulterated HTML with some images sprinkled in. Content > presentation
Re:Our best practices are killing mobile web performance by firasd on Saturday May 21, 2016 @08:35AM (#11744471)
Yes but the resolution of those "some images" depends on what kind of connection/device you're on. It's not adequate to say 'just send the lowest bandwidth experience', because then every desktop browser on a 5mbps connection would get blurry low-res images and Arial/Times New Roman text intended for iPhone 4 on a 2G connection.
Re:Our best practices are killing mobile web performance by stan_rogers on Saturday May 21, 2016 @01:34PM (#11745433)
I would always like to have locally-installed fonts in preference to web fonts, regardless of connection speed (Arial and Times New Roman are hardly the only options), and right-sized, well-compressed images (in the appropriate format for the image type) are essentially a solved problem.
Re:Our best practices are killing mobile web performance by Dylan16807 on Saturday May 21, 2016 @04:02PM (#11745955)
> right-sized, well-compressed images (in the appropriate format for the image type) are essentially a solved problem.

An image with retina resolution is going to be pretty bulky if you want it to look crisp, even if you're doing a good job of optimizing.

If you're on a bad connection you probably want non-retina and aggressive compression, even though it can introduce blurs and artifacts. That can give you a file over ten times smaller.

One size does not fit all.

Re:Our best practices are killing mobile web performance by wwweston on Saturday May 21, 2016 @10:26AM (#11744775)
Good luck with that.

You'll fit in better in 2016 if you have leprosy but are killing it with a photo-heavy bootstrap theme + Angular SPA (with, of course, a healthy number of bower modules brought in).