<rekado>I cannot comprehend why one would like to replace GNU coreutils with something new that's been written in Rust at this fundamental level.
<zimoun>I do not know. What I find confusing is the mix of #~ with backquote. As in petsc, native-inputs backquote, arguments #~, but the package veusz in the same file uses backquote in arguments. It adds a level of complexity, and let the feeling of automagic thing; especially for non-lispers.
<civodul>it looks like a struggle for hegemony, as opposed to bringing something to the free OS table
<rekado>I really don't mind Rust; obviously I don't like the poor bootstrapping situation, the lack of support for other architectures, the lack of version-to-version stability, and the lack of dynamic linking --- but I don't actually mind the "rewrite in rust" meme per se.
<rekado>for many people it seems that the mere fact that something *other* than C is used *is* a gift to the free OS table.
<civodul>i mean, every distro has to import 200+ packages just to build librsvg, right?
<civodul>so even if we ignore bootstrapping issues, it can't be just a Guix problem
<civodul>or to put it differently, distros will be pressured to give up on curation, unbundling, bootstrapping, and other forms of QA work
<zimoun>civodul: well, arguments not always quoted? We can do stats, but it appears to me almost surely quoted or backquoted. And for small corner cases as substitute-keyword-arguments, it is not unified. Bikeshedding about syntax, all this adds complexity and we often hear: «I need to learn Guile for packaging» (see Café Guix ;-))
<civodul>zimoun: i'm open to solutions, i'm just saying it's not this simple :-)
<zimoun>civodul: about Rustify. Bah, drifting and going offtopic, it just looks like how the World is going these days for almost everything: create a big black box ready for consumption, sell it at all cost saying it is “better” than the rest, define “better” as own direct ’interests’ for creators, hide what “better” implies for future, loop.