slrz's comments

On: Generics can make your Go code slower

[slrz]

What is it that Go supposedly calls casting? The term (or its variations) does not show up in the language specification.

People sometimes use it for type conversions but that's in line with usage elsewhere, no?

[merely-unlikely → slrz]

Are you talking about type assertions? It's right there in the Go Tour. But that's a different thing than a type conversion.

On: The most important thing to understand about queues (2016)

[slrz]

I guess that basically everything you'd consider for production use allows you to configure queue sizes and related behaviour however you fancy.

On: Go’s major versioning sucks – From a fanboy

[slrz]

For example, debug/pe ImportedLibraries(), which is supposed to return all the libraries that a module imports, was stubbed out to return "nil, nil" in a minor release [1]

I just looked at the Git history and this is plain false. It already looked that way when the big source tree move (src/pkg/ -> src/) was done in 2014. Tracing it back further (to before Go 1.0 times, when there wasn't even a builtin error interface yet and the function returned os.Error), ImportedLibraries was *never* implemented in debug/pe.

On: Go Annoyances

[slrz]

> google's 'reference' layout

Nothing to do with Google here, by the way. It's just the default format of the Unix date command.

So if you can't remember the order, just switch to your shell and run `LC_ALL=C date`.

[davisoneee → slrz]

Not quite. With date, the timezone comes before the year.

LC_ALL=C date => Sun Feb 13 14:27:18 GMT 2022

On: Podman in Linux

[slrz]

No longer true. Podman nowadays ships with an optional daemon that serves a Docker-compatible interface, so you can use docker-compose directly if that's what you want.

See for example: https://www.redhat.com/sysadmin/podman-docker-compose

[KronisLV → slrz]

That does seem better! Of course, there are a few lingering issues with support, but overall the trend is good: https://github.com/containers/podman/issues?q=is%3Aissue+is%...

Of course, there's no Swarm support, as evidenced by that very article:

> Caveats

> One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman.

Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/

Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman

On: The journey to controlling external monitors on M1 Macs

[slrz]

This was never an intended feature. If I understand the article correctly, they were using an undocumented ("private") API which happened to stop working.

[smoldesu → slrz]

Every API is undocumented on MacOS, what do you want them to do? How are you supposed to discern between zombie XNU code and Good LTS Apple Compliant code?

[brokenmachine → smoldesu]

Rule of thumb: if you paid for an official Apple dongle, all related code is LTS (*until said dongle is deprecated on a whim, of course).

On: QUIC is now RFC 9000

[slrz]

You can always use sendmmsg(2), writev(2) or other iovec-based APIs.

On: “They introduce kernel bugs on purpose”

[slrz]

I don't like it either but it's not as bad as it sounds: the ban almost certainly isn't enforced mindlessly and with no recourse for the affected.

I'm pretty sure that if someone from the University of Minnesota would like to contribute something of value to the Linux kernel, dropping a mail to GregKH will result in that being possible.

On: Ask HN: Why is the Linux community struggling to implement hibernation?

[slrz]

Most common distributions turn it on when running on a device with UEFI Secure Boot enabled.

On: Ask HN: Why is the Linux community struggling to implement hibernation?

[slrz]

So CentOS is actually getting better with a more open development model. Awesome.