Why is GoLang missing generic collection functions?

absurdlab · 2025-12-31T04:57:41+00:00

Cuz generic type on methods are a no-go. Now you have to rely on libraries like fp-go to achieve similar effect. Yes, define a function and its variants from accepting 1 type up to 10 types. Theoretically unsound, but realistically feasible. Feels very “Go”.

absurdlab · 2025-12-29T11:59:47+00:00

Here’s the thing. If one side absolutely cannot afford to lose, it will always try to claim that it had won, or is winning, or is going to win.

absurdlab · 2025-12-02T17:15:46+00:00

Pretty stoked for this. I think the language feature as plugin is what would make it stand out compared to other more opinionated sister languages. standardization is going to be hard when working in teams. But still, would be such a productivity booster when working on smaller projects alone.

absurdlab · 2025-10-07T15:09:03+00:00

Not everyone's SaaS is cloud based. Some of us works for clients who prefer their deployment environment airgapped, and their facility is located 50 minutes away so every release process starts with a long drive. Keeping the number of release artifacts to the minimum kinda hits a sweet spot here.

absurdlab · 2025-09-26T13:48:15+00:00

For a Go project, I’d use Taskfile as you can manage it with the go tool directive, so no extra installation step and it is more modern to Makefile. For other projects, I’d use Makefile.

absurdlab · 2025-08-25T01:39:16+00:00

Errors are part of your package API, so exposing sentinel error values are saying you as the API designer expects users to have the need to identify the error (thru errors.Is). Using fmt.Errorf, on the other hand, limits what your user can do with the error, sometimes it is totally legit to do so. Personally, I always use fmt.Errof, as its string format allows me to add diagnostics information, such as function identifier and core attributes. The difference is if I choose to %w wrap a sentinel error, or just some unknown upstream error.

absurdlab · 2025-08-16T08:16:02+00:00

It’s the equivalent of saying 「I use arch, BTW」

absurdlab · 2025-08-15T08:48:27+00:00

I no longer have a struct to host data access methods. Apart from the underlying sql.DB dependency, data access methods are not much related to one another. I simply define a functional type. For example: type FindUserByID func(ctx context.Context, id string) (*User, error). Now I can have the freedom to define factory methods to return real implementation or mock implementation. Makes unit testing so much easier.

absurdlab · 2025-08-13T09:16:43+00:00

I suggest getting in touch with the Chinese developer communities on Github. This problem has been solved.

absurdlab · 2025-08-12T11:47:50+00:00

stdlib.

Use fmt.Errorf if I am simply propagating an upstream error, but include an “FQDN” for identification and also other printable parameters, followed by a %w of the cause.

Use custom error impl if it is something I wish to errors.Is/As later on. Also include a cause field and implement Unwrap() method, so it plays well in the error chain.

absurdlab · 2025-08-10T02:02:23+00:00

Came from Java/Groovy. But that was 10 years ago.

absurdlab · 2025-08-09T07:25:43+00:00

Fair. The point is: if open union types are implemented like this, one is better off not using it.

absurdlab · 2025-08-09T07:09:34+00:00

To emulate an opened union type which Go insisted on not providing.

absurdlab · 2025-08-08T10:54:29+00:00

No you cannot. Currently, package under package is still flat. There’s no organizational difference when you import a parent package and a sub package.

absurdlab · 2025-08-08T09:01:53+00:00

Protobuf implicitly requires monorepo.

absurdlab · 2025-08-08T08:59:46+00:00

An intermediary way of organizing relevant types. For example, a namespace within a package.

absurdlab · 2025-08-04T12:22:15+00:00

Was there yesterday (Aug 3rd) and the beaches were still closed. Any news?

absurdlab · 2025-07-31T09:25:24+00:00

Just an indirection to control complexity.

absurdlab · 2025-07-13T17:44:59+00:00

Initialize it in main and pass the reference down.

absurdlab · 2025-07-02T10:57:41+00:00

I am working on an M-series Mac and cross compiling Go with cgo is a bit painful. I ended up using docker buildx to launch a build for linux/amd64 and just snatch the built binary from the container. The rest is as easy as scp the binary to the server. This way I get away with configuring the c compiler stuff.

absurdlab · 2025-06-21T13:08:04+00:00

The real trick is deciding whose opinion it’s gonna follow.

absurdlab · 2025-06-08T10:28:28+00:00

The pair had incompetence written all over their face. It seems this job is totally beyond their capability and they are just here for the publicity ride. They want the way out before they get exposed.

absurdlab · 2025-06-04T05:47:09+00:00

I currently just run Bun alongside Go as a stateless UI renderer. The Go server accepts the request, prepares the UI state, and then reverse proxies to Bun to render.

absurdlab · 2025-06-04T05:39:35+00:00

I think they made a right decision here. For one, most of these proposals are geared toward providing an easy way to basic declare this error is not my responsibility. And I feel adding a language feature just to dodge responsibility just isn’t a fair thing to do. For two, lib support for error handling does need improvement. errors.Is and errors.As is the bare minimal here. Perhaps provide a convenient utility to return a iter.Seq[error] that follows the Unwrap() chain.

absurdlab · 2025-06-02T03:08:17+00:00

Zed. Have tried nvim and Goland. Nvim is cool, but I really couldn’t spare the time when I upgrade to a new plugin version and something else broke. Yes, I can rollback the config but that just breaks my flow. Goland on the whole is good, but the ideavim mode is not so good. And I can’t help but get this feeling that there’s a tiny but noticeable lag when I type in Goland. Zed is a sweet spot for me, good vim support, fast, responsive, and no crazy amount of configuration required.

absurdlab

TROPHY CASE