Barnaby Keene

I see, that makes sense, Zap cannot know this. And I suppose hard-coding special treatment for pkg/errors would be a bad idea in terms of future proof and design. So...

That's pretty much what I had in mind, the pain I was referring to was forgetting to use `PlainError` on _every_ log entry!

I've always found "pkg" useless. 1. it's a 3 letter shortening, which isn't friendly to non-English speakers who may think it's an acronym for something (P.K.G.?) 2. it's a useless...

> This means your project should never contain any directory because your documentations, deployment manifests, scripts and whatever is part of your repository are also only “files“. I think you...

here's what we use when we need error handling: ```go type ( MapIteratee[T any, R any] func(T) R MapErrIteratee[T any, R any] func(T) (R, error) ) // Map is stolen...

> @Southclaws this looks great - it would be nice if this were a part of lo - or published as a package somewhere. made a quick package, but it...

This doesn't need a rebase, it's literally a 2 line change: https://github.com/Southclaws/sampctl/pull/476/commits/201a2c20dca5b1cb88b3c89da7e23705fa0e1a9e

Here's a Nushell version: ```nu npm list -g -json | from json | get dependencies | items {|key, value| { name: $key, version: $value.version } } | format "{name}@{version}" |...

That's why I simply wrote it in Go instead 😂

I'm not sure, that codebase still uses Prisma though and it seems to be running quite well with fairly high traffic still. However, the "posts" schema referenced has since been...