News for hackers. Stuff that matters.

A comment on The web at maximum FPS: How WebRender gets rid of jank.

Re:The web at maximum FPS: How WebRender gets rid of jank by hasenj on Wednesday October 11, 2017 @05:10AM (#15448326)
This is great! I'm really impressed by the technical achievement, and hope everyone takes lessons from it to put performance and FPS at the forefront of their concerns when developing applications.

Sadly, seeing the state of the industry, people will just use this as an excuse to continue write more and more sloppy code that would perform terrible even on the newest and faster WebRender version.

In other words, this version might run current websites at 60 fps. But wait a few years, and it will become the norm that a lot of websites render at 10fps or less.

There should also be a way to punish developers who fail to run their sites at 60fps on WebRender, similar to how browsers will start to punish sites that run without https.

For example, if a site fails to run at 60fps for a few seconds, show some kind of alarm on the address bar that this site is very slow and might crash the browser.

[ Parent | on HN ]
Re:The web at maximum FPS: How WebRender gets rid of jank by critiqjo on Wednesday October 11, 2017 @12:20PM (#15450906)
No, not "crash the browser" (coz browsers are not supposed to crash no matter the site's content), but that "this site might drain your battery quickly" or something along those lines.
[ Parent | on HN ]