Would you care to write an "Experience Report" for benefit of the Go community and development future? Pretty, pretty please! The rationale and idea is descri

Would you care to write an "Experience Report" for benefit of the Go community and development future? Pretty, pretty please! The rationale and idea is described on https://blog.golang.org/toward-go2#TOC_5.3 https://blog.golang.org/toward-go2#TOC_5.3. and https://blog.golang.org/toward-go2#TOC_8 https://blog.golang.org/toward-go2#TOC_8. , with an important note to later "publish it" (i.e. just link) on https://golang.org/wiki/ExperienceReports https://golang.org/wiki/ExperienceReports. Yours seems to be an awesomely perfect case — a real-world situation, with additional case study of how a new language helps you solve the pain points!