<civodul>right, and modules can do -mtune=native, which makes software blazingly fast!
<rekado_>we’ve had real trouble with a group here that stubbornly refused to use Guix. And when they started because they couldn’t build the thing manually they mixed that one Guix package with a whole bunch of Conda and artisanal hand compiled packages.
<civodul>handcrafted vs. industrial packages, in a way
<civodul>i can imagine the pain that ensued for everyone involved
<rekado_>for months they would get really angry, blame all problems on Guix, and then suddenly asked us to ‘fix Guix’, because the compiler doesn’t work.
<rekado_>we first heard from them when they demanded we fix Guix.
<rekado_>it was then that I bought some new tools for the garden and lost myself in a daydream of leaving computers behind for good.
<civodul>look, you're blaming computers when the real issue is elsewhere: users
<rekado_>We’ll probably offer short monthly Guix intros again.
<zimoun>Read somewhere « I installed these compilers with "apt install" on debian11, the exact version is: intel-oneapi-compiler-dpcpp-cpp 2021.3.0-3350 » Arf, source version is different from binary version…
<civodul>re getting this message out, i think we'll just have to repeat ourselves
<civodul>and to join forces with others projects that share the same goals, such as Debian
<civodul>they have been saying this for decades, in fact
<dstolfa>civodul: yeah. i also thing we could maybe try and get these things out to hackernews and lobsters as an initial thing, but maybe we could do a better job at bringing it up during discussions at our respective workplaces/universities so people think about these issues and naturally run into guix
<zimoun>dstolfa, yeah! Except, people think about these issues but then avoid to fix them because it changes too much their current habits. As civodul said earlier today: «often, people would need more general intros to GNU/Linux, the shell, and all that»
<drakonis>hn itself is starting to ride the wave right now
<drakonis>to entice the average hn/lobsters reader, the posts would require something extra
<drakonis>as they're most likely going to ask themselves why would they prefer to use guix over nix or anything else
<rekado_>(unless that’s meant as a sarcastic play on ‘few’)
<rekado_>I needed three attempts to understand this sentence: ‘Not providing those libraries or providing a variant that is not binary-compatible with what `libtorch_cpu.so` expects is the end of the game.’
<rekado_>‘end of the game’ –> ‘Game Over’, ah! Took me a while to make the connection.
<rekado_>I’d also suggest to update the URLs to specific commits instead of just ‘…/master/…’ because the contents will eventually change (while the blog post won’t).
<rekado_>‘if some of the packaging implicit assumptions are not met’ –> ’if some of the implicit packaging assumptions are not met’?
<rekado_>‘deploy a [-software] complex software stack’
<rekado_>this sounds like something is missing: ‘—look what’s inside and which may not be immediately obvious.’
<rekado_>‘It[+’s] a step backwards several years in the past,’