@algowatching Menslifting
When you try hard sticking to Boring #Haskell and then a new GHC comes out
I didn't like that "death by fancy autocorrect" meme at first, but then I've begun to be more accepting.
The idea of humanity auto-correcting itself (out of existence) by means of war and/or gross negligence has a certain ring to it.
Another batch of humanity auto-correction risks spotted
@Xilokar @dabbling_duck@oldbytes.space this. Also, endianness.
@cstross @dakkar @jpkmensah unless your antiquated colobox is a SPARCStation old enough to avoid being an LLVM-supported platform it should be able to host a backend.
@angusm The date is off. Fancy Autocorrect will do its correction in 2032CE.
@mickdarling @erictopol According to people in nuclear security that "0" can turn into "1" very fast, just by sheer luck. The field is underfunded and understaffed and getting worse with time.
@robcornelius @AlSweigart Garbage [feedback] in - garbage results out, classic.
@omgubuntu > a classic, deb-based version (default) and, for the first time, an immutable, snap-based build for enthusiasts to experiment with.
This should be somewhere just under the title.
@emilymbender The one does not cancel the other. Having bad incentive structures doesn't automatically prevent death by sepsis or getting accidental rock in head.
My own hypothesis is that the harmful thing is "engagement maximization" and not "social media", and that you could have engagement-maximization algorithms applied to other things and make them more harmful, but I don't have hard data to support that and I don't really even know how to start going about gathering it, or falsifying this hypothesis.
@travisfw I've seen a lot of humongous illegible diagrams that could have been a few lines of code. If there's a tool to make it legible, I don't know about it.
I'm not against no-code or something. It is visual coding that makes my eyes hurt.
@travisfw IDK. Visual "code" doesn't scale well. Text is more succinct and easier to pattern-match.
@omgubuntu Th[e]Underbird
@travisfw No-code for what result?
I acquired (with help) a killer audio cassette digitizing rig, and then IMMEDIATELY had to spend over 2 months digitizing 90+ cassettes from the 1999 Game Developers Conference (via a slow-and-steady workflow that got the job done without being too disruptive to any other work I was doing).
So, here we are, it's done. Go enjoy 70+ hours of presentations about all aspects of game making and producing, in 1999.
https://archive.org/details/1999_Game_Developers_Conference_Audio
Toots as he pleases.