Bla, nobody reads this. I like cheese. Walruses are sea vampires.

1. MIND THE GAP
CHRIS HEILMANN (﴾@CODEPO8)﴿, STATE OF THE BROWSER, LONDON, SEPTEMBER 2015

2. WEB DEVELOPMENT
WAS A LOT ABOUT
GAPS…

3. CONSIDER THIS
SIMPLE, SENSIBLE
MARKUP…

4. …AND THE MESS
THAT INTERNET
EXPLORER 6 AND 7
MADE OF IT.

8. FIXES WERE
PLENTIFUL…

9. AND VERY SPECIFIC
TO THE BROWSER’S
ISSUES…

10. ALL OF THESE WERE
SOLUTIONS.
BUT THEY FELT BAD.

11. WRITE EXTRA MARKUP TO
WORK AROUND THE ISSUES
OF THE PARSER?

12. RELY ON HACKS THAT
EXPLOIT KNOWN PROBLEMS
IN THE CSS PARSER OF THE
OFFENDING BROWSER?

13. RELY ON KNOWN BUGS IN
THE CSS PARSER?

14. CREATE A DEDICATED STYLE
SHEET WITH ALL THE QUIRKS
IN THEM -‐ ONE FOR EACH
OFFENDING BROWSER

15. FIND A SOLUTION AND
ENSURE THAT ONLY THE
PROBLEMATIC BROWSERS
GET IT?

16. STOP TRYING TO SOLVE THE
PROBLEM OF BROWSER
CREATORS AND FEED BACK
ISSUES SO THAT BROWSERS
CAN IMPROVE?

17. EXCEPT, BACK THEN
THERE WERE NO
FEEDBACK CHANNELS.

18. SO WE DID THE NEXT
BEST THING.
WE WROTE
ABSTRACTIONS TO
FIX BROWSER ISSUES
FOR US.

19. NO WAITING FOR
BROWSERS -‐ LET’S
INNOVATE AND BUILD
THE THINGS WE WANT!

20. BROWSERS WILL CATCH
UP AND WE CAN REMOVE
OUR ABSTRACTIONS…

21. …EXCEPT, WE NEVER DO.

22. AT EVENTS, WE TALK
ABOUT AMAZING
SOLUTIONS BUT
SOMEHOW, IT FEELS
WE’RE NOT HAVING
AN EFFECT…

23. A LOT IS NOT
WORKING THE WAY
IT SHOULD…

24. 🕗15 SECONDS

25. 🕗15 SECONDS
http://www.webperformancetoday.com/2015/09/08/deja-vu-all-over-again/
THE TIME THE MEDIAN
ECOMMERCE SITE
NEEDS TO FULLY
LOAD…

26. http://www.webperformancetoday.com/2015/09/08/deja-vu-all-over-again/
THAT’S A PRETTY
TERRIBLE STATE OF
THE WEB.
• The median page’s time to interact
is 5.5 seconds, and fully loads in just
over 15 seconds.
• The median page is 2MB in size and
contains 170 resources
• Most sites fail to take advantage of
core image optimisation techniques

27. AND SO NOT UNCOMMON…

28. WELL, I AGREE…

29. HUGE, INDEED…
http://www.apple.com/ipad-‐air/

30. HUGE, INDEED…
http://www.apple.com/ipad-‐pro/

31. WHOSE FAULT IS
THIS?

32. PRETTY MUCH
OURS…
• Web development is still governed
by looks alone
• Clients still expect web sites to work
the same on every browser and
platform
• Quick delivery trumps quality and
release processes
• We’re asked to make things work
and fix them later -‐ but there never
is a later.

33. A LOT OF OUR
INNOVATION AND
EASY TO USE
SOLUTIONS FEEL LIKE
PURE ESCAPISM…

34. I’M NOT SAYING
THERE SHOULD BE
NO INNOVATION…

35. IT IS JUST NOT
EVERYBODY’S
RESPONSIBILITY.
SOME OF US COULD
CONCENTRATE ON
KEEPING THE WEB A SOLID
FOUNDATION.

36. WE GET HIGH ON
TECHNICAL
SOLUTIONS THAT
GET INCREASINGLY
COMPLEX.
http://ashleynolan.co.uk/blog/frontend-‐tooling-‐survey-‐2015-‐results

37. THIS IS NOT AN OLD
MAN OF THE WEB
RANTING…
(﴾WELL, NOT EXCLUSIVELY)﴿

38. LATELY I WORKED
EXCLUSIVELY IN
FIXING ONE MASSIVE
ISSUE OF THE WEB…

39. WE REMOVED ALL
THE THINGS THE
WEB SUFFERED
FROM…
✘ VML
✘ attachEvent(﴾)﴿
✘ currentStyle
✘ X-‐UA-‐Compatible (﴾render modes)﴿
✘ IE Layout Quirks
✘ VBScript
✘ Conditional Comments
✘ MS-‐Prefixed Events

40. WE REALISED YOU
CAN’T BREAK THE
WEB OVER NIGHT… :(﴾

41. WE LEARNED THAT THERE ARE MANY WEBS…

42. before
after
before
after
-webkit-appearance: none -webkit-gradient
…AND THAT EXPERIMENTAL FEATURES DON’T DIE

43. EDUCATING IS A
TOUGH JOB…
http://dev.modern.ie/tools/staticscan/
https://github.com/MicrosoftEdge/static-‐code-‐scan

44. THE BIGGEST
CULPRITS WE
FOUND…
✘ Aggressive browser sniffing
independent of version number
✘ Outdated libraries and polyfills -‐
some of them clashing with new
language features
✘ A lack of packaging and
dependency loading solutions -‐
dozens of JS files = no inlining
possible
✘ If it works on Safari iOS, that’s
what matters -‐ no matter what
the spec says…

45. FIXING THE BROWSER SHOWED US HOW BROKEN THE WEB IS

46. WE HAVE WORKING COMMUNICATION
CHANNELS BETWEEN BROWSER MAKERS AND
DEVELOPERS…

47. LET’S USE THEM
PROPERLY.
HERE’S WHAT I LEARNED
WORKING FOR BROWSER
CREATORS
✓ It is a constant race not to break the
web -‐ every mistake web developers
make needs to get catered for.
✓ The pressure is immense. Instead of
pushing for an interoperable web,
browsers are constantly compared and
expected to be different.
✓ When implementing standards, we
find a lot of problems and feed them
back. That’s why a score of 100% in
feature tests makes no sense.
✓ Most speed increases are based on
analysing and fixing developer
mistakes/sloppiness.

48. SO HERE IS MY PLEA
TO HELP WITH
BETTER SOLUTIONS
FOR EVERYONE…

49. STOP TELLING
PEOPLE ON THE
WEB THAT THERE
ARE DOZENS OF
SOLUTIONS THAT
MAGICALLY FIX ALL
THEIR ISSUES…

50. STOP CATERING TO
OLD BROWSERS.
GIVE THEM BASIC, WORKING
SOLUTIONS AND ENHANCE
USING FEATURE DETECTION.

51. EXPLAIN, DON’T
MAKE IT FASTER AND
EASIER!

52. SHOW THE DANGERS
OF QUICK SOLUTIONS.

53. KEEP THINGS ACCESSIBLE
FOR EVERYONE.
THERE IS NO TECHNICAL
BASELINE!

54. SIMPLY BECAUSE YOU CAN FIX ANYTHING WITH
JAVASCRIPT DOES NOT MEAN YOU SHOULD!

55. LET’S COLLECTIVELY
CALM DOWN!

56. WE’RE NOT IN A
HEALTHY STATE
RIGHT NOW AS A
COMMUNITY…
✘ We build to impress each other -‐ the
people who need our solutions never
see them.
✘ We feel rushed and not good enough
-‐ all the time.
✘ We feel innovation is going too slow
whilst not recognising when something
got fixed we wanted oh so much when
it was the hot thing to demand.

57. THE FIRST STEP TO
HAPPINESS IS TO
MAKE IT HAPPEN…

58. THE FIRST STEP TO
HAPPINESS IS TO
MAKE IT HAPPEN…
✓ Improve your basic skills, catch up on
what’s possible. caniuse.com is a
riveting read!
✓ Start helping people who are not here
and don’t follow hackernews. You start
teaching and you end up learning.
✓ Report problems, demand support for
basic features, not only for the hot,
new (﴾half-‐baked)﴿ ones.
✓ Reach out beyond our echo chamber
if you want to reach people who need
the knowledge you have.

59. THANK YOU!
CHRIS HEILMANN
@CODEPO8