zlacker

That sounds like your kernel refusing to create that file, nothing to do with Go.

  $ cat main.go
  package main

  import (
   "log"
   "os"
  )

  func main() {
   f, err := os.Create("\xbd\xb2\x3d\xbc\x20\xe2\x8c\x98")
   if err != nil {
    log.Fatalf("create: %v", err)
   }
   _ = f
  }
  $ go run .
  $ ls -1
  ''$'\275\262''='$'\274'' ⌘'
  go.mod
  main.go

>>yencab+(OP)
I'm confused, so is Go restricted to UTF-8 only filenames, because it can read/write arbitrary byte sequences (which is what string can hold), which should be sufficient for dealing with other encodings?

>>comman+UK
Go is not restricted, since strings are only conventionally utf-8 but not restricted to that.

>>yencab+(OP)
> That sounds like your kernel refusing to create that file

Yes, that was my assumption when bash et al also had problems with it.

>>yencab+UL
Then I am having a hard time understanding the issue in the post, it seems pretty vague, is there any idea what specific issue is happening, is it how they've used Go, or does Go have an inherent implementation issue, specifically these lines:

If you stuff random binary data into a string, Go just steams along, as described in this post.

Over the decades I have lost data to tools skipping non-UTF-8 filenames. I should not be blamed for having files that were named before UTF-8 existed.

>>comman+Ks1
Yeah, the complaint is pretty bizarre, or at least unclear.

>>comman+Ks1
Let me translate: "I have decided to not like something so now I associate miscellaneous previous negative experiences with it"

>>yencab+(OP)
I've posted a longer explanation in >>44991638 . I'm interested to hear which kernel and which firesystem zimpenfish is using that has this problem.

>>comman+Ks1
The post is wrong on this point, although it's mostly correct otherwise. Just steaming along when you have random binary data in a string, as Golang does, is how you avoid losing data to tools that skip non-UTF-8 filenames, or crash on them.

>>kragen+JH2
I believe macOS forces UTF-8 filenames and normalizes them to something near-but-not-quite Unicode NFD.

Windows doing something similar wouldn't surprise me at all. I believe NTFS internally stores filenames as UTF-16, so enforcing UTF-8 at the API boundary sounds likely.

>>yencab+nM2
That sounds right. Fortunately, it's not my problem that they're using a buggy piece of shit for an OS.