While Dep was the official experiment, developers new to Go are encouraged to use Go modules instead since they are part of the official toolchain now.

I think it's time we stop recommending Dep to new developers and stick with the official standard.

Not sure how to contribute or if the topics are already covered.

Noting them down in case some one is interested.

• Web : Gorilla toolkit
• DB: bolt DB
• DB Migration
• CLI tools: Cobra
• CLI Tools: cli
• Cache: LRU Map
• Mocking: counterfeiter
• Monitoring: prometheus

Fiber is a great framework, simple, good documentation, good team, blazing fast (tested in local environment, production havent yet)

https://github.com/gofiber/fiber

Hi, really like this project :) Recommend to several projects we years already use in prod:

1. Config management: viper
2. WebServer - simple and very fast, on fasthttp base: atreugo
3. Distributed cache: aerospike
4. Log management system: graylog
5. Task scheduling: cron

Thank you!

The logging topic structure shown in the diagram does not match what is in the readme. I believe it should start at the Logging node and not at the Log Frameworks node.

For example, Staffjoy is an awesome project based on golang. Maybe we can add it to a node ‘Project’

Just like this:

16. Project

• Staffjoy

What do you think of it?

1. update zh-TW version in i18n folder
2. update other md file's link
3. in order to distinguish zh-CN and zh-TW, so change zh-CN name from "中文版" to "简体中文版"

go-zero is a web and rpc framework written in Go. It's born to ensure the stability of the busy sites with resilient design. Builtin goctl greatly improves the development productivity.

You can find more information about Watermill in the GitHub and in the documentation at go-zero.dev.

Hi there

Observability is a must have today, maybe we can have a Observability / Telemetry path to the roadmap?

I think future will be https://opentelemetry.io/, but there are a lot of framework technology : https://radar.cncf.io/2020-09-observability

I just stumble upon your developer roadmap, as a newbie, I would like to know why you suggesting echo as framework of choice, since most of golang dev I met/talked to prefer no framework so they cannot help explain it.

I'm coming from PHP and Python so community already have general consensus on what framework to use, even PHP community basically advise to start new project using framework mainly due to possible security issue with no framework implementation.

Also some description on other decision would be great.

Since there is a GraphQL section already, I think its best to add some libraries to that section. More specifically these?

• gqlgen
• graphql-go

Would love to PR if need be.

Hi @Alikhll , this PR add a Go language library Excelize and update the chart title to "Go Developer in 2022".

Excelize is a library written in pure Go providing a set of functions that allow you to write to and read from XLSX / XLSM / XLTM / XLTX files. Supports reading and writing spreadsheet documents generated by Microsoft Excel™ 2007 and later. Supports complex components by high compatibility, and provided streaming API for generating or reading data from a worksheet with huge amounts of data.

You can find more information about Excelize in the GitHub and in the documentation.

There could be a lot of approach to store your configuration to some file such as JSON, YAML, TOML, INI and etc. I wonder what's the proposed way to read/write configuration file in golang?