This document summarizes a presentation about improving efficiency and performance on the web. It discusses Moore's Law, which states that computers get faster every two years, and May's Law, which says software efficiency halves every 18 months to compensate. However, web development has focused too much on innovation and new technologies rather than optimization. As a result, median page load times are over 5 seconds. The document calls for developers to focus on fixing existing issues, improving efficiency, and testing new standards like ES6 before adopting them widely. It argues for less hype and more focus on users, technical limitations, and fixing broken aspects of the current web.
11. BROWSER DO AN
INCREDIBLE AMOUNT
OF WORK FOR US…
• Display of all kind of media content
• Fix minor mistakes in our code
• Optimise our code to run smoothly
• Provide us with developer tools
• Provide us with deep insights what
our code does to the computer
• Allow us to automate testing in
them and debug remotely on
devices we don’t even own (﴾using
3rd party services)﴿
12. So how come we
made the web all
about May’s law?
20. TIME TO GET REAL…
US
OUR
ASSUMED
AUDIENCE
OUR
AUDIENCE
TECHNICAL PROFICIENCY,
INTEREST IN CHANGE AND UPGRADES,
INTEREST IN SPENDING MONEY ON THE WEB FOR WEB SERVICES…
21. AS DEVELOPERS, WE
ARE ASKED TO DO
THE IMPOSSIBLE…
• Make it work the same in every
browser
• Make it easy to maintain and we
want to control everything
• Make sure it is also accessible -‐ I
think there’s a law we need to
follow
• Don’t spent too much time on it -‐
let’s release it now and fix it later!
• Use this analytics code you have
no clue about -‐ we need to know
how people use our products
25. I CURRENTLY WORK
WITH A CLEANUP
CREW…
http://dev.modern.ie/tools/staticscan/
https://github.com/MicrosoftEdge/static-‐code-‐scan
26. A simple way to detect how old
a part of our massive site is
checking which version of
jQuery was used in that part
of it. It’s like rings in a tree trunk.
https://www.flickr.com/photos/91183364@N08/13916636762
“
27. WE BREAK THE WEB
FOR THE SAKE OF
DEVELOPER
CONVENIENCE…
29. COST FOR
DEVELOPERS…
• Learning new frameworks
• Re-‐learning frameworks
• Debugging frameworks
• Setting up developer
environments
• Cutting down on possible hires/
adding to onboarding time
31. THE REAL
IMPORTANT BIT IS
THE COST FOR OUR
USERS…
• Time to load / execute
• Bandwidth used
• CPU usage
• Frame rate (﴾60 fps)﴿
• Memory usage
• Battery
32. THE JAVASCRIPT
LEARNING PROCESS
HAS ALWAYS BEEN
INTERESTING…
• Use view source to see what
others are doing…
• Copy and paste the bits that
look like they are responsible
for some things
• Change some numbers around
• Run into errors
• Blame Internet Explorer
33. THIS, OF COURSE,
WAS WRONG AND
WE GOT MORE
PROFESSIONAL…
• Search for a solution on
Stackoverflow
• Copy and paste the bits that
look like they are responsible
for some things
• Change some numbers around
• Run into errors
• Blame JavaScript for being
terrible and not a real language
• For good measure, blame
Internet Explorer.