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.
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…
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.
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.
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.