3 ms·
The portability story for Go is awful. I've blogged about this before: https://blog.habets.se/2022/02/Go-programs-are-not-portable.html https://blog.habets.se/2
by thomashabets2 10mo ago
The portability story for Go is awful. I've blogged about this before: https://blog.habets.se/2022/02/Go-programs-are-not-portable.html https://blog.habets.se/2022/02/Go-programs-are-not-portable....
It's yet another example of Go authors just implementing the least-effort without even a slight thought to what it would mean down the line, creating a huge liability/debt forever in the language.
- hu3 10mo agoYou expect Go to magically make systemd journaling exist in macOS? I can't even begin to comprehend the thought process here.
- thomashabets2 10mo agoI can't even begin to comprehend how you got from here to there. I encourage you to elaborate on how you think that's connected, and not make a strawman argument. You may have not done so deliberately, but if you can't begin to comprehend that I would mean what you said, then you could give me the benefit of doubt and maybe entertain the idea that I did not. Edit: In my blog post I give the example of getpwnam_r. One should not check for if the OS is Solaris in a given version range, but if getpwnam_r is one or the other type.
- hu3 10mo agoNo language is going to do that for you. And I don't think Go promissed otherwise. Perhaps it's about managing expectations.
- thomashabets2 10mo agoI mean… my whole blog post is about how autotools does that easily, and Go does not. "Language", no. But Go's build comments are not really part of the language proper.