State Of The Gopher Nation - Golang UK 2017

I am at GolangUK in London, having just finished giving the opening keynote.

I was a bit more nervous than usual, in part, due to the length of time since my last talk, and in part I was representing the entire Go project for the first time in a keynote.

This talk is an overview of the entire Go project. It covers “what we’ve done”, “why we did it” and “where we are going” as a project. It highlights our accomplishments, challenges and how the Go Project is working on our challenges.

Slides

Transcript

State of the Gopher Nation - Golang - August 2017

  1. G O P H E R N A T I O N S T A T E O F T H E A U G 2 0 1 7
  2. WHERE WE’VE BEEN
  3. MAJOR GO MILESTONES
  4. GO’S TIMELINE 2007 2009 2012 Open SourceBirth 1.0
  5. launch 2014 2016 20172015 2015 WWG & GOB SSAGopherCon Go In Go Go 2 annc.
  6. ACCOMPLISHMENTS
  7. GO’S GARBAGE COLLECTION : A STORY IN TWEETS
  8. Go #5 most loved, #3 most wanted on Stack Overflow https://insights.stackoverflow.com/survey/2017#technology
  9. • Reliability • Scalability • Durability • Simplicity • Performance Go is go to language for:
  10. CHALLENGES
  11. Go’s Dependency Management story isn’t good (yet). We realized our deficiencies in this space later than we should have. Dependency Management
  12. New User Experience Image via https://twitter.com/golangar/status/796000999844577284
  13. Community Culture
  14. Single Perspective
  15. It’s too hard and too intimidating for many in the community to contribute to the Go project. Project Participation
  16. T O D A Y
  17. WORLDWIDE ADOPTION
  18. hello.
  19. Go breaks into the Tiobe Top 10
  20. Go #9 on GitHub usage & 2nd fastest growing https://octoverse.github.com/
  21. Go #9 on IEEE rankings http://spectrum.ieee.org/static/interactive-the-top-programming-languages-2017
  22. Go #14 on Stack Overflow Survey (usage) https://insights.stackoverflow.com/survey/2017#technology
  23. 500k – 1M Go Users
  24. WORLDWIDE COMMUNITY
  25. 100’s of Go meetups all around the world
  26. 20+ Women Who Go chapters around the world
  27. Conferences Across the World
  28. GO ADOPTION – BANKING / COMMERCE
  29. GO ADOPTION – GAMING / MEDIA
  30. GO ADOPTION – TECH
  31. GO ADOPTION – GENERAL
  32. GO ADOPTION – GLOBAL COMPANIES
  33. ADDRESSING OUR CHALLENGES
  34. Go’s Dependency Management story isn’t good (yet). We realized our deficiencies in this space later than we should have. Dependency Management
  35. Managing Dependencies 3 1 2
  36. New User Experience Image via https://twitter.com/golangar/status/796000999844577284
  37. Improving New User Experience 3 1 2
  38. Community Culture
  39. Improving Culture 3 1 2 https://twitter.com/jboursiquot/status/885933489513738245https://twitter.com/kirtenz/status/885499675079462912
  40. Single Perspective
  41. Increasing User Feedback 3 1 2
  42. It’s too hard and too intimidating for many in the community to contribute to the Go project. Project Participation
  43. Expanding Go Team & Contributors 3 1 2 https://twitter.com/joshroppo/status/886358586468687872
  44. MAKING AN IMPACT
  45. In roughly a week’s time, I went from initial commit to shipping replacement backends. “ - Matt Robenolt @
  46. You can write in Go as easily as Python, but it can save you a lot of machine resources. “ - Alexander Ponomarev @ (translated from Russian)
  47. Dropbox & Go
  48. WHERE WE’RE GOING
  49. GO – THE LANGUAGE OF THE CLOUD
  50. THE CLOUD IS BUILT IN GO
  51. We’ve had great experiences with tools written in Go and now we are adopting it for our next project “ - Cloud Users in 2018
  52. GO 2
  53. First and foremost, Go 2’s main goal will be to fix the most significant ways Go 1.x fails at scale. “ - Russ Cox
  54. Maybe we can do two or three [changes], certainly not more than five. “ - Russ Cox
  55. Experience Reports We need your help! We need people to write experience reports to clearly define and communicate real issues they are experiencing using Go.
  56. NEW CHALLENGES OPPORTUNITIES
  57. Go’s Messaging Problem Go’s value isn’t in one key feature. People that use Go love it but struggle to communicate why to others “Try it and you’ll love it” has limited success in communicating the value Go brings to organizations
  58. Go’s Accessibility Issue Go’s docs have an implicit audience of systems programmers having a formal CS education. The work to define personas is the first of many steps to meeting Go’s audience where they are.
  59. The Go project will never reach its potential without contributions from people like you The Go project will never reach its potential without contributions from people like you WE NEED YOUR HELP WE NEED YOUR HELP