- Drip feed of API's
- Deprecate and Break. Recent events were a stark reminder that empathy is key.
- Time for a change.
- On one hand people don't like Apple's model of ship twice a year with an OS update, on the other Chrome is pushing too quickly. Alex Komoroske talked about elastic band and tension and stretch too far it snaps.
- Have we reached that points
- web.dev - appears Chrome only.
- too much change.
- too quickly.
- Refernce - too fast, can't keep up. Other's shouldn't have to work because of our lack of support.
- How can we slow down, but keep pace? Maybe batch more. The general population of developers don't need to know about all new API's on the day they launch.
- On one hand people don't like Apple's model of ship twice a year with an OS update, on the other Chrome is pushing too quickly. Alex Komoroske talked about elastic band and tension and stretch too far it snaps.
1 min read
Developer Clarity
Paul Kinlan
Lead of Chrome DevRel
Disclaimer. This article is a draft.
This article might look complete but it is completely un-developed and is a snapshot of my thoughts at the time (which might also be a long time ago). It will be refined over time with research, education and conversations with people in the industry.
There are many errors including and not limited to: spelling, grammatical, lack of ecosystem awareness understanding and plain ignorance.
I am making it public to get feedback. You might completely disagree, you might agree violently. Either way, teach me. I want to hear from you: (Email, @paul_kinlan.)
See Also
Tags
Stay in the loop.
I'm trialing a newsletter. Join for monthly insights into web dev, Chrome, and the open web.