go
golang-developer-roadmap
go | golang-developer-roadmap | |
---|---|---|
2,168 | 9 | |
123,918 | 17,770 | |
0.7% | - | |
10.0 | 0.0 | |
2 days ago | over 1 year ago | |
Go | ||
BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go
-
Why I love Rust for tokenising and parsing
I think they're asking how the code in the Go runtime that implements the garbage collector, a core feature of the language, avoids needing the garbage collector to already exist to be able to run, being written in the language that it's a core feature of. I suspect the answer is just something like "by very carefully not using language features that might tempt the compiler to emit something that requires an allocation". I think it's a fair question as it's not really obvious that that's possible--do you just avoid calling make() and new() and forming pointers to local variables that might escape? Do you need to run on a magical goroutine that won't try to grow its stack with gc-allocated segments? Can you still use slices, closures, ...?
I think the relevant code is https://github.com/golang/go/blob/master/src/runtime/mgc.go and adjacent files. I see some annotations like //go:systemstack, //go:nosplit, //go:nowritebarrier that are probably relevant but I wouldn't know if there's any other specific requirements for that code.
-
Play games from your terminal!
I decided to use Go because I'm familiar with it, it's easy to learn and read, it's popular, and it's fast. Being a compiled, cross-compatible language doesn't hurt, either.
-
How to use migrations with Golang
To follow this article you'll need: Go and Docker with Docker Compose
-
Writing Secure Go Code
My own experience is that the Go stdlib has resulted in worse security than, for example, rust.
The reason for that is that both the Rust and Go stdlib have a stability promise, so anything built into them can't change if it's insecure.
For example, the 'tar' package in go by default returns unsanitized paths, and has led to a bunch of CVEs: https://github.com/golang/go/issues/55356
The go stdlib can't change the tar package to make it secure by default because it would be a breaking change to do so.
Rust, on the other hand, has a tar package outside of the stdlib, and so it can evolve to be more secure and over time find a better interface.
We've seen that with various other packages, where the Go stdlib HTTP implementation defaults to no timeouts, and thus makes it easy to DoS yourself. Ditto for DNS. The tls package has similar backwards compatibility warts that make it less secure by default.
Forcing backwards compatibility with network protocols by baking them into the stdlib has largely not been a security win in my experience.
-
Australia/Lord_Howe is the weirdest timezone
> America/Nuuk does daylight savings at -01:00 (yes, with a negative)
Europe/Dublin also has a negative DST offset. Irish DST runs through the European winter (i.e. the opposite of the other European timezones).
(More details here: https://github.com/golang/go/issues/56743#issuecomment-13157... )
-
Go sync.Cond, the Most Overlooked Sync Mechanism
By the way, there's actually been talk about removing sync.Cond in Go 2: proposal: sync: remove the Cond type.
-
Jia Tanning Go Code
e.g. https://github.com/golang/go/issues/42713
That having been said, I also think the _tag.go mechanism needs to be dropped, it causes more confusion and risk than benefit. There are build tags (//go:build) for conditional compilation, if needed, instead.
-
- 418 I'm a Teapot
If you are bored you can read the discussion when _mnot_ tried removing 418 status code from different languages and implementations because it wasn't technically correct.
https://github.com/nodejs/node/issues/14644
https://github.com/golang/go/issues/21326
And someone even ended up making a website http://save418.com/
-
Understanding Round Robin DNS
https://github.com/golang/go/blob/master/src/net/http/transp...
If I’m reading the code right round trips (HTTP requests) go through queueForIdleConn which picks up any pre-existing connections to a host. The only time these connections are cleaned up (in HTTP2) is if keepalives are turned off and the connection has been idle for too long OR the connection breaks in some way OR the max number of connections is hit LRU cache evictions take place.
Furthermore, the golang dnsclient doesn’t even expose record TTLs to callers so how could the HTTP2 transport know when an entry is stale?
- Testing adding fuzz test support (2021)
golang-developer-roadmap
-
Web api with golang
I have found this road map kind of summarized frameworks and tools but I am not sure if it's up to date https://github.com/Alikhll/golang-developer-roadmap
-
The Dearth of golang content on youtube
Golang tutorial: Table Of Contentshttps://golangbot.com/learn-golang-series/https://quii.gitbook.io/learn-go-with-tests/ - Learn Go by testshttps://gobyexample.com/https://tour.golang.org/https://github.com/Alikhll/golang-developer-roadmap
- Go Developer Roadmap
- Golang roadmap
-
Is this roadmap still viable?
Hey guys Im really new to golang.Learning some basics and willing to switch my whole career to golang. Im a junior frontend developer rn.And starting backend with Go.I was looking for some good structered roadmap and found this https://github.com/Alikhll/golang-developer-roadmap. Its from 2020. Should I still follow it?
-
Web Developer learning Golang
Roadmap: https://github.com/Alikhll/golang-developer-roadmap/blob/master/golang-developer-roadmap.png
-
TIL: Learning Go
Check out a proposal for a Go Developer Roadmap for learning Go in 2020
-
Do we have a golang roadmap?
Don't know if there's an official one but I'm following this roadmap Golang Roadmap
-
As experienced devs of Golang.... how do you guys think i should start from scratch to be industry ready go developer ? and from where also?
Here is a good perspective to be "industry ready". Remember you shouldn't be an expert in everything, but for a junior dev know at least the terms: https://github.com/Alikhll/golang-developer-roadmap
What are some alternatives?
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
data-engineer-roadmap - Roadmap to becoming a data engineer in 2021
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
the-evolution-of-a-go-programmer - The Evolution of a Go Programmer
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
AspNetCore-Developer-Roadmap - Roadmap to becoming an ASP.NET Core developer in 2024
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
cybersecurity-career-path - Cybersecurity Career Path
Angular - Deliver web apps with confidence 🚀
gobyexample - Go by Example
RxGo - Reactive Extensions for the Go language.
Get-Set-Go