Viewing profile — aleksi

I was on this talk expecting to hear about MongoDB abusing open source (as you could guess from my profile, that’s a topic dear to my heart). Instead, I saw the most entertaining t…

Yet most, if not all, READMEs of official branches recommend using mutable vM tags. Not even branches — tags that they re-create.

See also https://github.com/golang/go/issues/66653 (that I don’t think is linked from the article)

You omit the fact that he took those words back and said “Crimea is Ukraine” while being in prison, knowing well it will not make his life (and death) easier

> What languages will be supported? > As a real keyboard with the QWERTY layout, Communicator supports languages that use the Latin alphabet: [...] Russian Weird

Aaaand it's gone!

You can make it run much better by increasing the game's process priority with `renice`. I know that sounds like something that should not work, but it does.

You are right; I stand corrected

> If you have a struct with a simple int field, and you store that somewhere as an *int, the entire struct and anything it points to will be kept alive. While Go allows interior po…

As a producer of the response, if I didn't care about being understood, I would use a made-up language. As a consumer, you may care about understanding my response, but you cannot …

I think you missed the “any handler” part. Currently, the types that my library package could use depend on the handler used by the caller. This limits types to an unspecified subs…

1) The idea is that your library should accept the slog logger and use it. The caller would create a logger with a handler that defines how log messages are handled. But there are …

My problem with that is that it makes it impossible to use slog logger safely without knowing what handler is being used. Which kind of defeats the purpose of defining the common s…

Not sure I understand your sarcasm. I read the documentation, source code, handler writing guide, and issues in the Go repository multiple times over two years, and I use slog exte…

So clearly not all values are supported. And I know that I can create a wrapper for unsupported types. My problem is exactly that – I don't know what types are supported. Is error …

Well, is fmt.Stringer supported? The result might surprise you: req := expvar.NewInt("requests") req.Add(1) attr := slog.Any("requests", req) slog.New(slog.NewTextHandler(os.Stderr…

My biggest gripe with slog is that there is no clear guidance on supported types of attributes. One could argue that supported types are the ones provided by Attr "construct" funct…

And our (FerretDB) take on it: https://www.linkedin.com/feed/update/urn:li:share:7365677213...

And our take on it: https://www.linkedin.com/feed/update/urn:li:share:7365677213...

I open-sourced my MongoDB alternative, and all I got was this lousy lawsuit.

> It's too slow to run in prod to be worth it I disagree there. It is reasonable to run a few service instances with a race detector. I have a few services where _all_ instances ar…

See https://manticoresearch.com/comparison/vs-sphinx/ . Sphinx is no longer open-source.