l'empathie mécanique @dpwiz@qoto.org

@p that's "beginners tips"
Real pro tip: test your backups (can be combined with wiping the OS!)

@thor "Escape? From my safe space?"

@chris__martin Nah. It's just lousy UX with cryptic, error-prone rituals. Mercurial and Bazaar had it so much better.

@amiloradovsky *reversed

@anselmschueler At least it isn't |> or something like that. Ew.

@meowski @ahmetasabanci Stuff like this happened since the early days.

Especially illuminating that a bot "trained" on Slack logs learns to tell "tomorrow", "ok" and so on, but is very reluctant to actually put an effort.

@cab404 for the glory of the satan
fa-fa-fa-fa la la la

@gerrymcgovern Degrowth, maybe, but not before settling interplanetary space.
Too early and you're subscribing billions of humans and all the species to a "death from entirely natural causes".

@edgarogh Yeah, operators are pretty unsearchable.

However there's an index for many kinds of #Haskell stuff you may be interested in.

Search operators: https://hoogle.haskell.org/?hoogle=%28%26%29&scope=set%3Astackage

Search by name: https://hoogle.haskell.org/?hoogle=Semigroupoid

Search by type (!): https://hoogle.haskell.org/?hoogle=Maybe%20a%20-%3E%20%5Ba%5D

(Bonus) Find packages: https://hackage.haskell.org/packages/search?terms=containers

@akshay Un-dvent of Haskell, day 1

@johnny > drop the transaction if we've had no luck for x seconds

That would be [registerDelay](https://hackage.haskell.org/package/base-4.19.0.0/docs/GHC-Conc.html#v:registerDelay). It's in IO, but it gives you a TVar, that will flip to True when the time comes. You can readTVar it to decide retry or bail.

Also, you can wrap pretty much anything in `timeout` (in IO proper).

@jesper Better start merging...

Why 5 more years for Agda? Aren't you in control of your toolchain?

@underlap @6d03 @abuseofnotation I'm afraid Mappable and the likes are less searchable *adding* learning overhead and frustration

@cwebber@octodon.social not blaming, that's one hard to swallow

@djrmarques@emacs.ch Figuring out "how to install X with NixOS" is an NixOS problem, not X q:

@parismarx The problem with the "fantasies" is that when their feasibility will become evident to a non-specialist it would be waaaaaay too late to do anything.

Meanwhile, enjoy fighting your corporate overlords. There's no real need to dunk on other people working on other problems.

@glyph should be in coreutils