When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following:<p>1. Functional operators like map/filter/reduce - all of these would be optional but would save SO many lines of code.<p>2. Add simple conveniences - e.g. "contains" to check if a key is present in a map. Again those who don't want to use these, don't have to.<p>3. Error handling boilerplate - something to the tune of "?" operator in Rust
The rats are leaving the sinking ship, is what comes to mind.
Go has become so mainstream and the talent has moved on.
I see it in so many cases.
Established packages only do dep upgrades and rarely add any innovation anymore.
Many of the original writers have abandoned the projects. Skeleton crews remain which lack the talent to be creative.<p>Gin for instance has a broken streaming api. No one is going to fix it. It would mean rewriting it from the ground up. Their contrib packages are mostly outdated and not functional.
Gorilla is also in maintenance mode.<p>The talent is leaving Go.
Go is also missing "the one true framework", e.g. what Spring is for Java. Or rails for Ruby or dotnet for C#.
I've been with Go since mid 2013. I loved the Go+ community on Google+. I loved the language because it removed a lot of mental burden and allowed me to focus on problem solving instead of listening to people telling me "what's proper" when I had done it my way for 13 years before the new hype, successfully.<p>I loved the bright minds using and developing Go.<p>But now it feels like it's dying or stagnating.<p>I thought spf13 was a company, not a pseudonyme of a Google employee. I use cobra in 99% of my projects, but cobra and viper leave much to be desired especially the interoperability out of the box and documentation.
> You may know me from building the Go Language, Docker, MongoDB, Hugo, Cobra, Drupal and spf13-vim<p>Actually this is the first time i heard from this guy, but this is an impressive list of projects to be involved in, wow!
About 10 years ago, spf13-vim showed me what vim could be and changed my coding life forever. I finally ejected it and spun my own .vimrc a few years ago, but I wouldn't be where I am today without it.<p>Thanks a bunch!
> Over the past 6 years Go’s user base has grown ~10x and Go users have increased their frequency from occasional to daily usage.<p>Impressive. How accurate is this?
> I led the team that designed MongoDB’s pioneering user experience<p>As someone who has used mongo, genuinely curious about which part of the user experience is being highlighted here.<p>Thanks for all your work with the Go community and good luck with the new team!
I started learning Go maybe 2 months ago, and we're now using it at work in production for small-scale projects, with plans to make it our default server-side language. The onboarding experience has been quite easy and effective I must say.<p>I have only written javascript for the past ~5 years and while I've never gone bored of writing code in a ~15y career, Go has brought some pleasant freshness to my work.<p>All that to say that this guy and the whole Go team have done some good work.
A bit off topic, but does anyone else find a data/financial company name "two sigma" to be...either troubling (how often two sigma events happen randomly and their lack of meaning beyond random fluctuation), or really on the nose?
All this time I thought spf13 was just Some Guy that did a pair of libraries for CLIs in Go, I didn't realize they were such a big contributor to the Go community. Thank you for helping the language escape its "this is a tool by Google for Google to fix Google-scale problems at Google" reputation; I've used it at a previous project for 2.5 years, it has its issues of course but overall I would use it again, in big part thanks to the community and resources available.
This article made me _really_ curious what manner of awesomeness is going on at Two Sigma, but couldn't figure it out from the website. @spf13, any pointers on where to find a good article on why TS is cool?
#1 Continue working with exceptional people.<p>This is what I miss the most nowadays. Being the number one item is proper placement IMO.<p>Go is fantastic and makes it easy to build. Hugo is great too - I'm currently using the Docsy template to avoid/replace multiple software products for a crypto/blockchain project.<p>Cheers
Wow, thanks for all those great contributions.<p>Looks like you have a good eye for picking good tech & teams to join and work with.<p>Any insights or things you saw in common?
spf13, congratulations on your move and thank you for what you’ve already done. Was a really cool experience watching your live interview during the recent HugoConf 2022 event.