@phnt @Inginsub @Suiseiseki @dcc @waff

> Ahh, I forgot that you had issues when interacting with it from Ruby.

I've used the iconv tool a lot, too.

> Input validation is for babies.

Yeah, I feel like...if I have to reimplement half of the library's functionality just to avoid making the library segfault

---HEY IT JUST FINISHED, SEE BELOW

...then the library is useless and I may as well just do it myself.

> glib also likes to bail out on mundane memory errors instead of trying to deal with them. No, that's hard for feet devs. abort() is much simpler.

God help you if you turn off overcommit but still want to use something that prefers to gobject a gstring instead of just doing `char *` like a normal person.

I was making some sort of point about gcc being bloated at some point earlier in the thread and I decided to do `git pull` and while I was waiting for that I typed `git gc` (after first accidentally typing `go gc`) but that took an hour and then the gc took most of an hour. It took so long that I typed `history` to get an informal benchmark, but it took so damn long that the thread moved elsewhere by the time this process finished running.

> 6 2025-05-25 07:04 git pull
> 7 2025-05-25 08:03 go gc
> 8 2025-05-25 08:03 git gc
> 9 2025-05-25 08:46 history