2022/04/17

2022-04-17 00:00:04 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2022-04-17 00:01:16 +0200 <hololeap> anyone know a haskell lib with MathJax in the docs off the top of their head? I want to see if my local MathJax.js setup works
2022-04-17 00:01:31 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)
2022-04-17 00:03:26 +0200juri_(~juri@178.63.35.222) (Ping timeout: 250 seconds)
2022-04-17 00:03:31 +0200juri__(~juri@79.140.115.71)
2022-04-17 00:03:31 +0200juri__(~juri@79.140.115.71) (Read error: Connection reset by peer)
2022-04-17 00:06:18 +0200anomal(~anomal@87.227.196.109) (Remote host closed the connection)
2022-04-17 00:08:31 +0200juri_(~juri@178.63.35.222)
2022-04-17 00:08:55 +0200wyrd(~wyrd@gateway/tor-sasl/wyrd) (Ping timeout: 240 seconds)
2022-04-17 00:09:07 +0200wyrd(~wyrd@gateway/tor-sasl/wyrd)
2022-04-17 00:24:47 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 256 seconds)
2022-04-17 00:25:17 +0200nahcetan(~nate@98.45.169.16)
2022-04-17 00:26:00 +0200acidjnk(~acidjnk@p200300d0c722df627ca148a3877b8356.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2022-04-17 00:26:51 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 00:31:31 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 246 seconds)
2022-04-17 00:38:46 +0200ishaan(~ishaan@122.161.53.177) (Quit: Client closed)
2022-04-17 00:45:44 +0200simeon(~pi@dslb-088-076-113-221.088.076.pools.vodafone-ip.de) (Ping timeout: 248 seconds)
2022-04-17 00:48:26 +0200argento(~argent0@168-227-97-23.ptr.westnet.com.ar)
2022-04-17 00:49:43 +0200neceve(~quassel@2.29.116.221) (Ping timeout: 246 seconds)
2022-04-17 00:56:10 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com)
2022-04-17 00:56:10 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com) (Changing host)
2022-04-17 00:56:10 +0200wroathe(~wroathe@user/wroathe)
2022-04-17 00:58:01 +0200simeon(~pi@dslb-088-076-113-221.088.076.pools.vodafone-ip.de)
2022-04-17 01:00:47 +0200chargen(~chargen@D964062A.static.ziggozakelijk.nl) (Quit: Leaving)
2022-04-17 01:03:43 +0200bontaq(~user@ool-45779fe5.dyn.optonline.net) (Ping timeout: 246 seconds)
2022-04-17 01:03:56 +0200pavonia(~user@user/siracusa)
2022-04-17 01:08:52 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) (Ping timeout: 250 seconds)
2022-04-17 01:10:44 +0200euandreh_(~euandreh@2804:14c:33:9fe5:88ce:e5fa:f6ef:a25b)
2022-04-17 01:12:46 +0200euandreh(~euandreh@2804:14c:33:9fe5:9d95:c71:11e4:3e0f) (Ping timeout: 250 seconds)
2022-04-17 01:15:47 +0200euandreh_(~euandreh@2804:14c:33:9fe5:88ce:e5fa:f6ef:a25b) (Ping timeout: 240 seconds)
2022-04-17 01:21:33 +0200TonyStone(~TonyStone@cpe-74-76-51-197.nycap.res.rr.com)
2022-04-17 01:21:38 +0200euandreh_(~euandreh@2804:14c:33:9fe5:8ead:4f39:6c3c:67f6)
2022-04-17 01:22:01 +0200wroathe(~wroathe@user/wroathe) (Ping timeout: 256 seconds)
2022-04-17 01:32:25 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 01:32:57 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Client Quit)
2022-04-17 01:34:33 +0200euandreh_(~euandreh@2804:14c:33:9fe5:8ead:4f39:6c3c:67f6) (Remote host closed the connection)
2022-04-17 01:34:59 +0200euandreh_(~euandreh@2804:14c:33:9fe5:be1f:339b:bf2e:3750)
2022-04-17 01:35:11 +0200vicfred(~vicfred@user/vicfred)
2022-04-17 01:38:06 +0200DNH(~DNH@8.43.122.67) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2022-04-17 01:44:16 +0200Midjak(~Midjak@82.66.147.146) (Quit: This computer has gone to sleep)
2022-04-17 01:46:46 +0200vicfred(~vicfred@user/vicfred) (Ping timeout: 246 seconds)
2022-04-17 01:49:44 +0200vicfred(~vicfred@user/vicfred)
2022-04-17 01:55:27 +0200dlromw^(~dlromw@50.226.13.122) (Remote host closed the connection)
2022-04-17 01:55:28 +0200xff0x_(~xff0x@om126033110024.35.openmobile.ne.jp)
2022-04-17 02:02:01 +0200axeman(~quassel@2a02:8109:a380:78:cc32:643d:863c:ed2b) (Ping timeout: 248 seconds)
2022-04-17 02:02:26 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2022-04-17 02:04:41 +0200jgeerds(~jgeerds@d5364b87.access.ecotel.net) (Ping timeout: 248 seconds)
2022-04-17 02:05:24 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 02:13:35 +0200gurkenglas(~gurkengla@dslb-178-012-018-212.178.012.pools.vodafone-ip.de) (Ping timeout: 256 seconds)
2022-04-17 02:19:51 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 02:20:59 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Client Quit)
2022-04-17 02:21:57 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 02:24:46 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 02:26:08 +0200vysn(~vysn@user/vysn)
2022-04-17 02:29:48 +0200oxide(~lambda@user/oxide)
2022-04-17 02:34:34 +0200chenqisu1(~chenqisu1@183.217.200.38)
2022-04-17 02:44:08 +0200chomwitt(~chomwitt@2a02:587:dc0f:ad00:bf65:8d32:22b6:5d0b) (Ping timeout: 248 seconds)
2022-04-17 02:45:55 +0200 <energizer> is there a segment of the haskell community that's against typeclasses?
2022-04-17 02:46:07 +0200 <energizer> (for one reason or another)
2022-04-17 02:47:48 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 02:48:28 +0200 <davean> energizer: I doubt it is possible to actually program anything non-trivial in Haskell without being for typeclasses, and if they don't code non-trivial things what part of the community are they? The set of people who program much of anything and are against typeclasses is almost definately empty.
2022-04-17 02:49:24 +0200 <davean> There are some people against multiparameter typeclasses I think? Mostly because they're not fully specified.
2022-04-17 02:50:24 +0200 <energizer> i mean people who wish haskell didn't use typeclasses and used some other mechanism instead
2022-04-17 02:51:01 +0200 <davean> I understood that
2022-04-17 02:51:08 +0200 <davean> I answered in that light
2022-04-17 02:51:15 +0200samuel(~samuel@2804:d59:cb88:600:6dbc:2943:43d1:eb16)
2022-04-17 02:51:37 +0200 <davean> You've got like a single option
2022-04-17 02:51:54 +0200 <davean> And we know why its horrible
2022-04-17 02:52:09 +0200samuel(~samuel@2804:d59:cb88:600:6dbc:2943:43d1:eb16) (Client Quit)
2022-04-17 02:54:57 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 256 seconds)
2022-04-17 02:56:04 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2022-04-17 02:56:16 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com)
2022-04-17 02:56:16 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com) (Changing host)
2022-04-17 02:56:16 +0200wroathe(~wroathe@user/wroathe)
2022-04-17 02:57:38 +0200Unicorn_Princess(~Unicorn_P@93-103-228-248.dynamic.t-2.net) (Remote host closed the connection)
2022-04-17 02:57:51 +0200 <davean> Everything else you can do is either make everything concrete, which means no datastructures as complicated as Map, and then why are you using Haskell at all? It provides basicly nothing, or something basicly isomorphic to passing a dictionary, which is equivilent to typeclasses, except incoherent so you don't know if it works without tracing every path to every location in your code.
2022-04-17 02:58:43 +0200 <davean> Theres not much space here for options
2022-04-17 02:59:03 +0200lottaquestions(~nick@2607:fa49:5041:a200:e015:4a6a:8224:d2c6)
2022-04-17 02:59:29 +0200 <davean> You can do pretty small things like "typeclasses, but without return type polymorphism" but thats dumb because if you look at our type system we can just recover that with some extra finger wiggling
2022-04-17 02:59:45 +0200 <abastro> Yeah, never seen anyone who dislike typeclasses
2022-04-17 02:59:47 +0200 <davean> at which point you're just making a style claim
2022-04-17 03:00:11 +0200 <abastro> Well, I guess someone like evan(Elm creator) hated typeclasses.. but eh
2022-04-17 03:00:11 +0200 <davean> abastro: yah, like asking this question says a lot about not understanding what they are mathematicly I think
2022-04-17 03:00:41 +0200 <hololeap> energizer: elm people :)
2022-04-17 03:01:19 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2022-04-17 03:01:37 +0200 <davean> hololeap: except even they implimented them, just as special cases, not a language feature
2022-04-17 03:01:59 +0200 <abastro> I also don't know what is typeclasses in mathematics tho
2022-04-17 03:02:01 +0200 <davean> thats sorta a debate about who should get access to type classes
2022-04-17 03:02:25 +0200 <abastro> Do you mean like, records denoting extra structures equipped on a set?
2022-04-17 03:03:09 +0200 <davean> abastro: well, importantly they're coherent
2022-04-17 03:05:20 +0200 <abastro> Coherent?
2022-04-17 03:05:51 +0200 <abastro> Clearly I slept through math formalism class I guess, as I don't know what coherence means here
2022-04-17 03:06:29 +0200 <c_wraith> it means they behave the same way in all contexts
2022-04-17 03:07:11 +0200 <c_wraith> Like, it doesn't depend on the context `a == b' always returns the same result for the same expressions a and b
2022-04-17 03:07:43 +0200 <c_wraith> If type classes could be overridden locally, that would no longer be true
2022-04-17 03:08:57 +0200 <abastro> Oh I thought you were talking about typeclasses in mathematics
2022-04-17 03:11:02 +0200 <davean> I mean they're not really different - type theory is a mathematics.
2022-04-17 03:11:30 +0200 <abastro> Yea type theory is a branch of mathematics
2022-04-17 03:11:37 +0200 <davean> right all you have in math is branches
2022-04-17 03:11:45 +0200 <c_wraith> math is a tree!
2022-04-17 03:11:47 +0200 <davean> and some functors between them :)
2022-04-17 03:12:22 +0200 <davean> the above discussion ports pretty trivial to several parts of mathematics.
2022-04-17 03:13:44 +0200 <abastro> Hmm, I wonder if `process` package is bundled with ghc installations.
2022-04-17 03:14:13 +0200 <abastro> I want sth which won't upgrade until ghc itself is reinstalled..
2022-04-17 03:14:30 +0200 <abastro> How do I enforce this
2022-04-17 03:14:44 +0200 <davean> abastro: thats not how it works
2022-04-17 03:14:46 +0200 <abastro> Wait nvm, I guess I don't need to worry about it in this specific case
2022-04-17 03:14:48 +0200 <davean> You're wrong about your assumption
2022-04-17 03:14:54 +0200 <abastro> Which assumption?
2022-04-17 03:14:57 +0200 <davean> https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/packages.html process is in GHC's distruction set
2022-04-17 03:15:01 +0200 <davean> but that doesn't mean it doesn't get upgraded
2022-04-17 03:15:11 +0200 <davean> I've *often* had to upgrade packages that ship with GHC
2022-04-17 03:15:12 +0200 <abastro> I see
2022-04-17 03:15:23 +0200 <davean> and nixos FUCKED ME OVER by making your dumb, wrong assumption
2022-04-17 03:15:24 +0200 <abastro> Quite annoying when packages upgrade
2022-04-17 03:15:31 +0200 <davean> why?
2022-04-17 03:15:33 +0200 <c_wraith> There are only a few packages that are wired in, like ghc, template-haskell, base, and I'm probably missing a couple
2022-04-17 03:15:50 +0200 <davean> Why do you even notice at all when packages upgrade?
2022-04-17 03:15:55 +0200 <abastro> Well, many baseline packages end up duplicated
2022-04-17 03:16:04 +0200 <davean> So?
2022-04-17 03:16:04 +0200 <abastro> + It takes awful lot of time to upgrade those packages
2022-04-17 03:16:09 +0200 <davean> how?
2022-04-17 03:16:17 +0200 <davean> How does it take more than a couple seconds of CPU time?
2022-04-17 03:16:32 +0200 <abastro> By building those packages?
2022-04-17 03:16:43 +0200 <davean> Yes, which is a couple seconds of CPU once and its over
2022-04-17 03:16:49 +0200 <abastro> Uh
2022-04-17 03:16:55 +0200 <abastro> For me it's like solid 10 minutes
2022-04-17 03:17:37 +0200 <davean> ... I can build a very large stack of everything from scratch in 10 minutes, what are you building this on?
2022-04-17 03:18:02 +0200 <davean> And it doesn't ever build stuff again until it changes
2022-04-17 03:18:10 +0200 <abastro> I mean, for me updating something like `cabal-install` (by updated hackage) takes 10 minutes
2022-04-17 03:18:11 +0200 <davean> that would still be a single 10 minutes the one time if changes.
2022-04-17 03:18:50 +0200 <abastro> IDK, somehow it duplicates the baseline dependencies as well.
2022-04-17 03:18:55 +0200cosimone`(~user@93-47-228-79.ip115.fastwebnet.it)
2022-04-17 03:19:08 +0200 <davean> I mean, if it depends on updates of them
2022-04-17 03:19:28 +0200 <davean> I just deleted ~/.cabal, and I'll run cabal install cabal-install
2022-04-17 03:19:50 +0200 <c_wraith> I use ghcup to install the cabal binary these days
2022-04-17 03:19:52 +0200cosimone(~user@2001:b07:ae5:db26:c24a:d20:4d91:1e20) (Ping timeout: 248 seconds)
2022-04-17 03:19:55 +0200 <abastro> package A depends on package B, package A updates, new copy of package B installed
2022-04-17 03:20:06 +0200 <abastro> Oh, the cabal-install thing was a demonstration, and I mean the case of depending on them
2022-04-17 03:20:08 +0200 <davean> abastro: one single time
2022-04-17 03:20:16 +0200 <abastro> Well I should have rather said, `Cabal`
2022-04-17 03:20:20 +0200 <davean> That happens a single time, and then never again until either A or B upgrades
2022-04-17 03:20:49 +0200 <abastro> I mean, whenever package A upgrades, new copy of the same version of package B is installed
2022-04-17 03:20:57 +0200 <davean> Yes, one single time
2022-04-17 03:21:25 +0200 <abastro> And quite often, one of the packages upgrade.
2022-04-17 03:21:33 +0200 <abastro> Like once a week
2022-04-17 03:21:43 +0200Null_A(~null_a@2601:645:8700:2290:9c14:dd1b:c930:439d)
2022-04-17 03:21:52 +0200 <abastro> And that takes 10 minutes
2022-04-17 03:22:15 +0200 <davean> The impressive part here for me is it takes 10 minutes, but also stuff low down in the stack defiantely doesn't update once a week
2022-04-17 03:22:39 +0200 <abastro> I mean, stuff higher up in the stack updates
2022-04-17 03:22:44 +0200 <davean> Most of them don't upgrade once a year.
2022-04-17 03:22:57 +0200 <abastro> And then, all its dependency has additional copy of the same version
2022-04-17 03:23:08 +0200 <abastro> Let's say, package B is updated from 1.0 to 1.1
2022-04-17 03:23:18 +0200 <abastro> package B depends on package A version 1.0
2022-04-17 03:23:24 +0200 <c_wraith> I still don't understand why you're updating packages all the time.
2022-04-17 03:23:41 +0200 <abastro> Then, when package B updates from 1.0 to 1.1, it installs a copy of package A version 1.0
2022-04-17 03:23:46 +0200 <abastro> So there is 2 copies of package A version 1.0
2022-04-17 03:23:53 +0200 <davean> Incorrect
2022-04-17 03:23:56 +0200 <abastro> Even though package A is not updated
2022-04-17 03:23:57 +0200 <davean> YOu're just wrong
2022-04-17 03:24:00 +0200 <abastro> Well, that happened to me
2022-04-17 03:24:04 +0200 <davean> No, it doesn't
2022-04-17 03:24:06 +0200 <abastro> I saw it.
2022-04-17 03:24:07 +0200 <davean> You're jsut wrong
2022-04-17 03:24:13 +0200 <c_wraith> it can happen if A inlines stuff from B
2022-04-17 03:24:13 +0200 <davean> No, you are wrong about what you saw
2022-04-17 03:24:44 +0200 <abastro> Yep, I guess package A inlined some stuffs of B and that portion changed.
2022-04-17 03:24:53 +0200 <abastro> Somehow it happens quite frequently, really.
2022-04-17 03:25:46 +0200 <c_wraith> but the thing is... while those versions of A have the same version number, they are *not* compatible
2022-04-17 03:25:56 +0200 <c_wraith> Or at least, cabal can't assume they are
2022-04-17 03:26:09 +0200 <c_wraith> so it has to manage them separately
2022-04-17 03:26:13 +0200 <davean> c_wraith: No, V depends on A
2022-04-17 03:26:13 +0200 <abastro> Indeed.
2022-04-17 03:26:16 +0200 <davean> c_wraith: No, B depends on A
2022-04-17 03:26:30 +0200 <c_wraith> davean: that's not what the premise said
2022-04-17 03:26:48 +0200 <davean> "01:23:18 abastro package B depends on package A version 1.0"
2022-04-17 03:26:58 +0200 <davean> No, that is what he stated here
2022-04-17 03:27:18 +0200 <c_wraith> hmm, that's incompatible with what it says above.
2022-04-17 03:27:25 +0200 <davean> So B updating can not cause an rebuild of A
2022-04-17 03:27:27 +0200 <abastro> Hm yea I could be confusing something here, but at least if something updates, something else has to update as well
2022-04-17 03:27:28 +0200 <davean> It *can not*
2022-04-17 03:27:44 +0200 <davean> Only an update of A can cause a rebuild of B
2022-04-17 03:27:49 +0200 <abastro> I guess things underneath were updated then.
2022-04-17 03:28:00 +0200 <c_wraith> davean: yet above, it says A depends on B. I think you have to assume one of those was a misstatement, and in the direction that makes sense
2022-04-17 03:28:39 +0200 <davean> c_wraith: well the second scenario is entirely incopatible with the first, so I assumed he started talkign about a different scenario
2022-04-17 03:28:39 +0200 <abastro> Sorry, this thing is confusing
2022-04-17 03:28:59 +0200 <abastro> I confused I guess
2022-04-17 03:29:01 +0200andrey__(~andrey@p200300dbcf409200f598c2566b8ed921.dip0.t-ipconnect.de)
2022-04-17 03:29:15 +0200 <c_wraith> abastro: the one thing you haven't addressed is why you update packages constantly. Are they security releases?
2022-04-17 03:29:22 +0200 <yushyin> Maybe not updating the index as often as you do is an option? ^^
2022-04-17 03:29:29 +0200 <abastro> ^
2022-04-17 03:29:30 +0200 <c_wraith> do they have changes you want to take advantage of?
2022-04-17 03:29:35 +0200 <abastro> Well, I update the package index
2022-04-17 03:29:39 +0200 <c_wraith> or are you just creating churn for yourself?
2022-04-17 03:29:39 +0200 <davean> I mean even if he does, theres not a ton that changes low down in the stack
2022-04-17 03:29:43 +0200 <abastro> cabal then chooses to update it.
2022-04-17 03:29:57 +0200 <c_wraith> cabal doesn't update stuff unless you run cabal clean or something
2022-04-17 03:29:58 +0200 <yushyin> you can also pin the index
2022-04-17 03:30:00 +0200 <abastro> My experience was that there were many changes in the lower level
2022-04-17 03:30:04 +0200 <davean> its damn rare for one of the distributed packages to get updated *with* GHC, never mind between releases
2022-04-17 03:30:16 +0200 <c_wraith> if you just use cabal build, it doesn't care that that the index changed
2022-04-17 03:30:25 +0200 <c_wraith> it just uses the existing plan
2022-04-17 03:30:36 +0200 <davean> Most low level packages don't see a release every 2 years
2022-04-17 03:30:37 +0200 <abastro> Strange, for me `cabal build` cares that index changed.
2022-04-17 03:30:58 +0200 <sclv> only if you cabal configure again
2022-04-17 03:31:01 +0200 <sclv> it caches
2022-04-17 03:31:04 +0200 <abastro> Hmmmmm
2022-04-17 03:31:15 +0200 <sclv> it caches the build plan unless you reconfigure
2022-04-17 03:31:17 +0200 <abastro> Now I don't understand what phenomenon I am getting
2022-04-17 03:31:18 +0200 <sclv> or clean
2022-04-17 03:31:27 +0200andrey_(~andrey@p200300dbcf2fb5008488c657f5155c0c.dip0.t-ipconnect.de) (Ping timeout: 240 seconds)
2022-04-17 03:31:35 +0200 <abastro> Because it tries to update hard to the newest version unless I do `cabal freeze`
2022-04-17 03:31:52 +0200 <davean> extensible-exceptions last released in 2012, filepath has a release in late 2021 but the one before that is 2018 ...
2022-04-17 03:31:54 +0200 <abastro> 5 copies of `aeson-2.0.3.0` is irritating tbh
2022-04-17 03:32:00 +0200 <sclv> if you change the cabal file it forces a reconfigure btw
2022-04-17 03:32:04 +0200 <davean> Like the low level packages *litterly* go years between releases
2022-04-17 03:32:06 +0200 <abastro> Oh
2022-04-17 03:32:15 +0200 <abastro> Now I see.
2022-04-17 03:32:21 +0200 <abastro> I changed the cabal file without knowing tht
2022-04-17 03:32:29 +0200justsomeguy(~justsomeg@user/justsomeguy)
2022-04-17 03:32:31 +0200 <sclv> and always calculates a buld plan from latest
2022-04-17 03:32:42 +0200 <abastro> So whenever I change cabal file, I should run cabal freeze to fix the build plan. I guess
2022-04-17 03:32:42 +0200 <sclv> but you can fix an index snapshot to avoid this
2022-04-17 03:32:59 +0200 <davean> abastro: Even with a reconfigure it'll only rebuild if something is different. Other than build time is there something that upsets you about having multiple copies of things like aeson?
2022-04-17 03:33:03 +0200 <sclv> or just let cabal do what it does since the behavior is good
2022-04-17 03:33:08 +0200 <abastro> Yea, but since sometimes I want newer stuffs, I guess I should go with cabal freeze
2022-04-17 03:33:13 +0200 <davean> (aeson is VERY high up the tree, so it'll rebuild a lot)
2022-04-17 03:33:17 +0200 <sclv> that default behavior was picked for a reason
2022-04-17 03:33:39 +0200 <sclv> it ensures your locally developed packages can take advantage of the latest bugfixes
2022-04-17 03:33:54 +0200 <abastro> Multiple copy of things are irritating because, you know, disk space
2022-04-17 03:33:59 +0200 <sclv> and remain building against the bleeding edge
2022-04-17 03:34:18 +0200 <abastro> Currently my cabal store is 5GB but I am afraid it will easily grow to 50GB+
2022-04-17 03:34:25 +0200 <davean> abastro: It won't
2022-04-17 03:34:32 +0200 <davean> 5GiB is HUGE for it
2022-04-17 03:34:39 +0200 <abastro> I experienced such cabal store growth
2022-04-17 03:34:49 +0200 <davean> And every time you do a compiler upgrade the old stuff becomes irrelivent
2022-04-17 03:34:50 +0200 <sclv> all my disk space for haskell stuff pales in comparison to one modestly graphiclly intensive game from 10 years ago
2022-04-17 03:34:56 +0200 <abastro> Well also other ppl in this chat said similar things about huge cabal store
2022-04-17 03:35:27 +0200 <sclv> or like ten episodes of a podcast that doesn’t compress its stream well
2022-04-17 03:35:27 +0200 <yushyin> if disk space is your concern, haskell might not be the right language for you :P
2022-04-17 03:35:34 +0200 <davean> You can remove your old compilers when you're done using them
2022-04-17 03:35:41 +0200 <abastro> I did
2022-04-17 03:35:52 +0200 <abastro> ghc-9.2.2 cabal store contains 5.3GB of contents.
2022-04-17 03:37:00 +0200 <davean> Hum, as far as I can tell, process is the fastest updated distributed library and it averages like once per quarter.
2022-04-17 03:37:06 +0200 <abastro> I mean.. I think 50GB~100GB range could surely be concerning
2022-04-17 03:37:30 +0200 <abastro> Nvm about the `process` part
2022-04-17 03:37:35 +0200 <davean> abastro: And I mean if that ever happens I would ... do something impressive
2022-04-17 03:37:47 +0200 <abastro> OH right, some dependency of `lens` also frequently updates
2022-04-17 03:38:04 +0200 <davean> I *think* I could *make* that happen inside a GHC lifetime if I tried *really* hard
2022-04-17 03:38:13 +0200 <davean> I'm not sure it is even possible though
2022-04-17 03:38:16 +0200 <yushyin> i have multiple ghcs and a cabal store of 8GB, also 10GB ~/.ghcup
2022-04-17 03:38:21 +0200 <davean> (For a single GHC version)
2022-04-17 03:38:28 +0200 <abastro> Interesting
2022-04-17 03:38:38 +0200 <abastro> Perhaps xmonad stuffs are quite huge?
2022-04-17 03:38:43 +0200 <davean> No
2022-04-17 03:38:47 +0200 <abastro> Hmmm
2022-04-17 03:38:58 +0200 <abastro> How do I have 5GB cabal store, I wonder
2022-04-17 03:39:14 +0200 <davean> I mean 5GiB is possible
2022-04-17 03:39:26 +0200 <abastro> In a week
2022-04-17 03:39:30 +0200 <davean> but 50GiB is an order of magnitude higher and it gets VERY hard to keep making it larger
2022-04-17 03:39:49 +0200 <abastro> I see, I mean before in 8.10.7, I had 20~30GB
2022-04-17 03:39:58 +0200 <davean> oh I mean, getting to like 2GiB is what I get just setting up - there s a lot of packages.
2022-04-17 03:40:00 +0200 <abastro> 50GB wouldn't take long from there I think
2022-04-17 03:40:07 +0200 <justsomeguy> I don't even use many Haskell packages (just core, QuickCheck, and HSpec), but my ~/.cabal/package directory is 781.84MiB. ~/.stack is 22.7GiB.
2022-04-17 03:40:23 +0200 <davean> justsomeguy: yes, but how many GHC versions?
2022-04-17 03:40:25 +0200 <abastro> Yep, wait even stack suffers from the problem
2022-04-17 03:40:33 +0200 <justsomeguy> davean: Maybe two?
2022-04-17 03:40:35 +0200 <sclv> stack suffers more!
2022-04-17 03:40:41 +0200 <abastro> More?
2022-04-17 03:40:43 +0200 <davean> yah, stack stuffers much more
2022-04-17 03:40:50 +0200 <abastro> I thought pinning versions would have lessened the problem
2022-04-17 03:41:27 +0200 <justsomeguy> Ohh, nevermind, I forgot that I have a test project that pulls the latest nightly GHC.
2022-04-17 03:41:33 +0200 <justsomeguy> No wonder.
2022-04-17 03:41:33 +0200 <davean> justsomeguy: .. right
2022-04-17 03:41:56 +0200 <abastro> Btw I like how `lens` package gets updated every other week or so, some dependeny of it is clearly updated often
2022-04-17 03:41:57 +0200 <davean> and building one project can reasonable build 2GiB
2022-04-17 03:42:00 +0200 <abastro> I don't know which
2022-04-17 03:42:03 +0200 <davean> but its very hard to keep growing
2022-04-17 03:42:16 +0200 <davean> abastro: well right, lens is basicly the top of the tree
2022-04-17 03:42:26 +0200 <abastro> Okay, let's see if it does not grow from 5GB
2022-04-17 03:42:39 +0200 <abastro> Yea, lens is annoying
2022-04-17 03:42:42 +0200justsomeguygoes off somewhere to delete his nightly stackage resolver snapshots.
2022-04-17 03:42:43 +0200 <davean> abastro: I mean do clean out old compilers as you move on from them
2022-04-17 03:42:58 +0200 <abastro> I even deleted 8.10.7
2022-04-17 03:43:00 +0200 <davean> Thats where the real growth is, that grows linearly
2022-04-17 03:43:13 +0200 <abastro> And that's barely "old", you know, in terms of what is really old
2022-04-17 03:43:14 +0200 <davean> but inside a compiler its growth is sublinear
2022-04-17 03:43:40 +0200machinedgod(~machinedg@24.105.81.50) (Ping timeout: 246 seconds)
2022-04-17 03:43:53 +0200 <abastro> 11 copies of gi-cairo-render lol
2022-04-17 03:44:08 +0200 <abastro> I thought I could do nothing in a week
2022-04-17 03:46:13 +0200xff0x_(~xff0x@om126033110024.35.openmobile.ne.jp) (Read error: Connection reset by peer)
2022-04-17 03:47:12 +0200 <davean> abastro: so you have two concerns; disk usage and build time
2022-04-17 03:47:23 +0200 <abastro> Yep.
2022-04-17 03:47:31 +0200 <davean> disk usage I don't think is worth worrying about, since it should be sublinear
2022-04-17 03:47:37 +0200 <davean> build time, thats entirely different
2022-04-17 03:47:51 +0200 <abastro> Well okay, to be frank, disk usage worry was from using old laptop a year ago
2022-04-17 03:47:57 +0200 <davean> that should be as it is, I'm not sure why it bothers you but thats the core problem as I see it
2022-04-17 03:48:11 +0200 <abastro> Had like 64GB on that 5-6 year old laptop
2022-04-17 03:48:52 +0200 <abastro> Is the build time shorter than 10 minutes for you?
2022-04-17 03:49:18 +0200 <davean> I mean yes, I can build lens and a bunch of things it doesn't include in way less than 10 minutes
2022-04-17 03:49:28 +0200 <davean> from a brand new system
2022-04-17 03:49:46 +0200 <davean> but I mostly build on a desktop
2022-04-17 03:49:57 +0200 <davean> So you know, possibly massively better performance
2022-04-17 03:50:03 +0200 <abastro> How good is your desktop end?
2022-04-17 03:50:31 +0200 <davean> pretty bad, its a 1950X, so you know old and slow
2022-04-17 03:50:50 +0200 <davean> a modern consumer chip is easly 50% faster
2022-04-17 03:51:26 +0200 <davean> Just performance is never an issue for me so I've not considered ugprading
2022-04-17 03:51:33 +0200shriekingnoise(~shrieking@201.231.16.156)
2022-04-17 03:53:15 +0200 <abastro> Oh, I see
2022-04-17 03:53:27 +0200 <abastro> Interesting how newer laptops still have less cores than old desktops
2022-04-17 03:53:33 +0200 <abastro> Mine has 8 CPU cores
2022-04-17 03:53:43 +0200 <abastro> amd-ryzen-9-4900hs
2022-04-17 03:53:46 +0200 <davean> I mean its an old high end desktop
2022-04-17 03:53:55 +0200 <abastro> Oh
2022-04-17 03:53:56 +0200 <davean> but a modern gaming CPU has 16 cores
2022-04-17 03:54:06 +0200 <davean> and mugh higher clock, and faster per clock
2022-04-17 03:54:13 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 03:54:16 +0200 <abastro> Yea, with this, it would take at least twice slower
2022-04-17 03:54:28 +0200 <abastro> Because IIRC cabal build can use all the cores
2022-04-17 03:54:32 +0200 <davean> laptops are also thermally limited unlike most desktops
2022-04-17 03:54:40 +0200 <davean> cabal build can *often* use all the cores
2022-04-17 03:54:50 +0200 <davean> but only by having multiple packages to build
2022-04-17 03:54:58 +0200 <davean> not when it doesn't have seperate packages
2022-04-17 03:55:11 +0200 <abastro> Yep, but I often have multiple packages to build
2022-04-17 03:55:12 +0200 <davean> and only when that build isn' contradicted by dependencies
2022-04-17 03:55:25 +0200 <davean> it can only build it in accordance with a topological sort
2022-04-17 03:55:26 +0200 <abastro> + This is better than most other languages I think.. at least I think..
2022-04-17 03:55:33 +0200 <davean> Yes, well it could be better
2022-04-17 03:55:43 +0200 <davean> we could build in parallel inside a package - GHC supports that
2022-04-17 03:55:57 +0200 <davean> what we lack is the ability to allocate cores to GHC dynamically
2022-04-17 03:56:09 +0200 <davean> the communication between GHC is considered but currently non-existant
2022-04-17 03:56:39 +0200 <abastro> It says that Ryzen 1950x is launched at 2017
2022-04-17 03:56:42 +0200 <davean> which is part of what makes something like a 1950X *so bad* for Haskell
2022-04-17 03:56:45 +0200 <abastro> That's.. hardly old
2022-04-17 03:57:10 +0200 <davean> Its past long term deprciation
2022-04-17 03:57:17 +0200 <davean> its well past any standard replacement cycle
2022-04-17 03:57:20 +0200 <davean> almost double most
2022-04-17 03:57:22 +0200 <abastro> Uhm
2022-04-17 03:57:23 +0200 <abastro> I mean
2022-04-17 03:57:38 +0200 <abastro> I've seen many ppl not changing their end for like 10 years
2022-04-17 03:57:44 +0200 <abastro> Like cars, you know
2022-04-17 03:58:01 +0200 <davean> I mean that can *only* occure in the last 10 years
2022-04-17 03:58:02 +0200 <abastro> So I thought I should not change mine for 7~8 years
2022-04-17 03:58:19 +0200ub(~Thunderbi@p200300ecdf15887a8d97c724330f0103.dip0.t-ipconnect.de)
2022-04-17 03:58:22 +0200oxide(~lambda@user/oxide) (Ping timeout: 246 seconds)
2022-04-17 03:58:29 +0200 <davean> between 2000 and 2010 that would be completely non-viable
2022-04-17 03:58:37 +0200 <abastro> Oh, why?
2022-04-17 03:59:04 +0200 <davean> compare the best CPU in 2000 to the worst released in 2010
2022-04-17 03:59:20 +0200ubert(~Thunderbi@p200300ecdf15883338aa5c9dba4a51bd.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2022-04-17 03:59:20 +0200ububert
2022-04-17 03:59:25 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 246 seconds)
2022-04-17 03:59:39 +0200 <davean> a computer from half way through there would have basicily had no chance in *any* terms of using software from 2010
2022-04-17 03:59:53 +0200 <davean> the systems of 2000 couldn't put in enough RAM to even load them
2022-04-17 04:00:09 +0200 <abastro> Wow
2022-04-17 04:00:36 +0200 <abastro> I was too young at 2000 to see that
2022-04-17 04:00:37 +0200oxide(~lambda@user/oxide)
2022-04-17 04:00:45 +0200 <davean> You happen to have only considered the slowest period of developement in computers in history, because Intel had no competition
2022-04-17 04:00:55 +0200 <abastro> Interesting, basically we reached some kind of plateau in terms of computer performance
2022-04-17 04:01:05 +0200 <abastro> Wait wha
2022-04-17 04:01:05 +0200 <davean> and almost all the change since 2010 to 2020 was in 2018-2020
2022-04-17 04:01:11 +0200 <abastro> Is it because Intel had no competition?
2022-04-17 04:01:36 +0200 <abastro> I thought it was genuinely because of semiconductor dead-end
2022-04-17 04:01:40 +0200 <davean> Well they stopped updating stuff, AMD came out with a competative chip, and they started again :-p
2022-04-17 04:01:45 +0200 <abastro> (Can't keep going smaller)
2022-04-17 04:01:52 +0200 <davean> No, there was no semiconductor dead end in the first half of that
2022-04-17 04:01:55 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 04:01:55 +0200 <abastro> Lul, intel
2022-04-17 04:02:02 +0200 <davean> and we've kept going smaller
2022-04-17 04:02:12 +0200 <davean> There *was* a slow period in there
2022-04-17 04:02:19 +0200 <davean> and there does need to be an end
2022-04-17 04:02:25 +0200 <abastro> So the plateau in semiconductor is rather in the future than the past
2022-04-17 04:02:27 +0200 <davean> but the slowness was also when stuff was getting faster again
2022-04-17 04:02:34 +0200 <davean> er
2022-04-17 04:02:44 +0200 <davean> to be clear, the slowness in getting smaller was when CPUs were getting faster again
2022-04-17 04:02:49 +0200deadmarshal_(~deadmarsh@95.38.231.67)
2022-04-17 04:02:58 +0200 <abastro> These delayed-delayed delays are fun
2022-04-17 04:04:11 +0200frost(~frost@user/frost)
2022-04-17 04:06:07 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Ping timeout: 240 seconds)
2022-04-17 04:07:07 +0200deadmarshal_(~deadmarsh@95.38.231.67) (Ping timeout: 246 seconds)
2022-04-17 04:07:41 +0200 <davean> So the Pentium 4 Willamette launched at the *end* of 2000, a quick look suggests if you got the largest RAM you could get on the market you could have, for several thousand dollars then (and multiply that a bit for modern currency), you COULD have gotten 2GiB into the system, and it looks like you probably can't buy a phone with a core as slow as its single core was.
2022-04-17 04:07:52 +0200 <davean> In practice the RAM to put 2GiB into that wasn't actually even on the market.
2022-04-17 04:08:19 +0200 <davean> RAM was in MiB not GiB in practice.
2022-04-17 04:08:24 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470) (Ping timeout: 248 seconds)
2022-04-17 04:08:51 +0200 <davean> Checking old builds, people bragged about 512MiB for the entire system
2022-04-17 04:09:58 +0200 <davean> Looking at what was on sale for prebuilts they're offering like 128MiB often :)
2022-04-17 04:10:40 +0200 <davean> Yes, modern systems might have more *cache* than those systems had RAM
2022-04-17 04:12:42 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2022-04-17 04:13:03 +0200 <monochrom> In 486 days I bragged about having 16MB RAM and comfortably running OS/2. >:)
2022-04-17 04:13:15 +0200 <abastro> Wow
2022-04-17 04:13:36 +0200 <monochrom> (Most people settled for 4MB and ran DOS 6, maybe once in a while Windows 3.)
2022-04-17 04:13:41 +0200 <davean> My computer has RAM and CPUs comparable to a supercomputer I used in 2003
2022-04-17 04:13:51 +0200 <davean> *a supercomputer*
2022-04-17 04:13:59 +0200 <davean> *it cost several million dollars*
2022-04-17 04:14:16 +0200 <monochrom> Now let's flash back to the floppy diskette days...
2022-04-17 04:14:47 +0200 <davean> abastro: anyway, your laptop CPU core is a bit faster than my desktop CPU core, but I expect your laptop gets hot within like 5-10 seconds and slows down below it per-core
2022-04-17 04:15:16 +0200 <davean> I have twice the cores, but that only matters some of the time, I'm probably winning on thermals
2022-04-17 04:15:16 +0200 <monochrom> Yeah laptop is more susceptible to thermal throttling.
2022-04-17 04:15:30 +0200 <monochrom> But I do have a laptop cooling pad. :)
2022-04-17 04:15:54 +0200 <davean> monochrom: the 486 only stopped being sold in 2007 ;)
2022-04-17 04:16:15 +0200 <davean> abastro: I expect, by the end of next year, to buy a computer twice as fast as my current one
2022-04-17 04:16:33 +0200 <davean> abastro: around 2004 you could probably get a computer twice as fast every year
2022-04-17 04:16:40 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 04:17:41 +0200 <abastro> Twice as fast??
2022-04-17 04:17:41 +0200 <davean> Ok, the best Intel CPU you could get in 2010 MIGHT have been the i5 Clarkdale, not sure
2022-04-17 04:17:43 +0200 <abastro> Oh no
2022-04-17 04:17:59 +0200 <davean> it had 2 cores
2022-04-17 04:18:11 +0200 <monochrom> MLton was like "beware that it needs 128MB, it may be too big for your system" :)
2022-04-17 04:18:29 +0200 <davean> Core i5-680 was released in April 2010
2022-04-17 04:18:47 +0200 <monochrom> Today that's the average size of a smartphone app.
2022-04-17 04:18:52 +0200 <davean> So, how much faster is *my* 5 year old desktop vs. a 2010 system?
2022-04-17 04:19:15 +0200 <davean> well, each of my RAM sticks is the size of the *max system memory* of that CPU
2022-04-17 04:20:04 +0200 <hololeap> same here which strangely gets me 12GB due to two of the slots being different (desktop comp from ~2011)
2022-04-17 04:21:17 +0200 <davean> and it looks like my CPU is something like .... 20 times faster?
2022-04-17 04:22:24 +0200 <hololeap> probably depends on the operations and if they're optimized by some new processor feature
2022-04-17 04:22:31 +0200 <davean> hololeap: definately
2022-04-17 04:22:38 +0200 <davean> thats assuming you can use my extra cores
2022-04-17 04:22:55 +0200 <monochrom> I'm added to Haskell and other modern high-level languages. Going back to those slower and smaller computers is no longer an option. >:) Although, maybe I could get hugs to run on DOS...
2022-04-17 04:23:00 +0200 <hololeap> yeah
2022-04-17 04:23:06 +0200 <monochrom> s/added/addicted/
2022-04-17 04:23:12 +0200 <davean> and just using your standard spec benchmarks
2022-04-17 04:24:00 +0200 <davean> If you compare to a Ryzen 9 5950X the comparison gets more insane
2022-04-17 04:24:05 +0200 <davean> and this is in the *slow* period
2022-04-17 04:24:07 +0200 <abastro[m]> When will "semiconductor dead end" hit hard
2022-04-17 04:24:15 +0200 <davean> abastro[m]: unclear.
2022-04-17 04:24:26 +0200 <abastro[m]> Like, it seems like smaller than 1nm is extremely hard
2022-04-17 04:24:30 +0200 <davean> abastro[m]: So what REALLY happened between 2010 and now is that games went GPU based
2022-04-17 04:24:52 +0200 <hololeap> abastro[m]: you have to understand that there is $$$$$$$$ in keeping up moore's law
2022-04-17 04:24:56 +0200 <davean> abastro[m]: no, we already build *some* stuff smaller than 1nm, we'll almost definately go below 1nm
2022-04-17 04:25:37 +0200abastro(~abab9579@220.75.216.63) (Ping timeout: 256 seconds)
2022-04-17 04:25:39 +0200 <davean> abastro[m]: *gamers* stopped having to upgrade CPUs, just GPUs, and entire classes of games came into popularity that didn't even need more GPU
2022-04-17 04:25:43 +0200 <hololeap> if moore's law wasn't a thing, the majority of people might start thinking about just keeping their old hardware around
2022-04-17 04:26:02 +0200AlexNoo_(~AlexNoo@178.34.150.20)
2022-04-17 04:26:04 +0200 <davean> hololeap: well, also theres just good economic benefits from more computation
2022-04-17 04:26:08 +0200 <davean> computation is enabling
2022-04-17 04:26:12 +0200 <davean> most CPUs don't go to consumers
2022-04-17 04:26:21 +0200 <davean> most CPUs are bought by corporations these days
2022-04-17 04:26:28 +0200 <davean> well, uh, sorry, leaving out smartphones
2022-04-17 04:26:29 +0200 <hololeap> right, good point, but my point still stands
2022-04-17 04:26:56 +0200 <davean> hololeap: right, sure, I'm just saying even if people kept all their old equipment we'd still have a lot of money in going smaller
2022-04-17 04:27:16 +0200 <davean> The replacement just ramps it up even further
2022-04-17 04:27:32 +0200 <hololeap> they have an economic incentive to make sure each new gen is way faster than the last, which is going to seriously push innovation
2022-04-17 04:27:39 +0200 <davean> abastro[m]: In no way is it clear where we'll top out of what is *practical*
2022-04-17 04:27:40 +0200sarupbanskota(~sarupbans@2601:645:8500:dc0:1cba:bfa3:5d61:5fe2)
2022-04-17 04:27:53 +0200sarupbanskota(~sarupbans@2601:645:8500:dc0:1cba:bfa3:5d61:5fe2) (Client Quit)
2022-04-17 04:27:56 +0200 <davean> hololeap: right, but even without the consumer space we have a lot of money for it
2022-04-17 04:28:11 +0200 <davean> because we need a LOT more compute to stop making money by having massively more of it
2022-04-17 04:28:15 +0200 <hololeap> money that wouldn't be spent unless the jump in performance was enough...
2022-04-17 04:28:32 +0200Alex_test(~al_test@178.34.151.248) (Ping timeout: 272 seconds)
2022-04-17 04:28:44 +0200 <davean> hololeap: Right, but performance makes people a LOT of money still, in terms of servers
2022-04-17 04:29:02 +0200 <davean> we're massively compute limited still
2022-04-17 04:29:19 +0200 <davean> sure they'd buy the current gens, and just run more of them - they are
2022-04-17 04:29:28 +0200 <davean> but theres a lot of money to be made in offering the faster one
2022-04-17 04:29:30 +0200AlexZenon(~alzenon@178.34.151.248) (Ping timeout: 250 seconds)
2022-04-17 04:29:35 +0200AlexNoo(~AlexNoo@178.34.151.248) (Ping timeout: 256 seconds)
2022-04-17 04:29:47 +0200 <hololeap> I still think that if they don't hit some benchmark every year they have a serious risk of everyone (including corporations) thinking twice about upgrading, which makes them pull some crazy stuff out of a hat, because these are seriously rich coporations
2022-04-17 04:30:15 +0200 <davean> hololeap: I agree other than the server space
2022-04-17 04:30:40 +0200 <davean> the server space will still need to buy hundreds of thousands of CPUs, per company, yearly just to keep up with current demand
2022-04-17 04:30:45 +0200 <hololeap> yeah I don't actually understand the economics, but I think I understand it well enough to get that :)
2022-04-17 04:31:02 +0200 <monochrom> But we already have the history that AMD was not a serious competitor therefore Intel also stagnated but still got as much purchases.
2022-04-17 04:31:03 +0200 <davean> and they have things they could sell if they had more compute
2022-04-17 04:31:28 +0200 <davean> monochrom: yep! though, note that was bad for the companies and they threw a LOT of money in working around it
2022-04-17 04:31:37 +0200 <hololeap> davean: that's a fair point
2022-04-17 04:31:40 +0200 <davean> look at the Power initiative, and the ARM cpu vendors they funded
2022-04-17 04:32:01 +0200 <davean> monochrom: Corporations were scared shitless of that stagnation and poured *billions* into working around Intel's stagnation
2022-04-17 04:32:56 +0200 <davean> So they *gamble* they could get ahead of that stagnation was worth tens of billions between them
2022-04-17 04:33:09 +0200 <davean> which tells you just how much that increase in compute is worth to them
2022-04-17 04:33:12 +0200Alex_test(~al_test@178.34.150.20)
2022-04-17 04:33:25 +0200 <hololeap> more compute = more $$$$, but when it doesn't we blame the technology
2022-04-17 04:33:58 +0200AlexZenon(~alzenon@178.34.150.20)
2022-04-17 04:34:15 +0200 <davean> monochrom: I see the argument "they were fine while Intel stagnated" a lot, but in truth they started emptying warchests because of it. Which rather tells the opposite story at least competatively
2022-04-17 04:34:45 +0200 <hololeap> computing is so full of hype and hyperbole it's laughable
2022-04-17 04:34:45 +0200 <davean> Considering the amounts they spent its easy to estimate they thought taht slowdown was costing them potentially in the hundreds of billions
2022-04-17 04:35:07 +0200 <davean> So it depends on what you consider "fine"
2022-04-17 04:37:00 +0200 <davean> is "if someone else solves this and we don't, we probably go out of business" fine?
2022-04-17 04:37:21 +0200dyeplexer(~dyeplexer@user/dyeplexer)
2022-04-17 04:37:29 +0200 <hololeap> who said "fine"?
2022-04-17 04:38:28 +0200 <davean> hololeap: no one, but monochrom said "Intel also stagnated but still got as much purchases"
2022-04-17 04:39:06 +0200 <davean> But Google, AWS, etc all started massively funding new competitors to Intel
2022-04-17 04:39:11 +0200sarupbanskota(~sarupbans@2601:645:8500:dc0:1cba:bfa3:5d61:5fe2)
2022-04-17 04:39:19 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Killed (NickServ (Forcing logout FinnElija -> finn_elija)))
2022-04-17 04:39:19 +0200finn_elija(~finn_elij@user/finn-elija/x-0085643)
2022-04-17 04:39:19 +0200finn_elijaFinnElija
2022-04-17 04:39:21 +0200 <davean> so its not really true that was a stable situation
2022-04-17 04:39:30 +0200 <davean> people were desperately trying to find a life raft
2022-04-17 04:39:37 +0200 <davean> that was VERY clearly a short term truth
2022-04-17 04:40:38 +0200Cale(~cale@cpef48e38ee8583-cm30b7d4b3fc20.cpe.net.cable.rogers.com) (Remote host closed the connection)
2022-04-17 04:41:02 +0200 <hololeap> well, they have the economic impetus to pull the rabbit out of the hat
2022-04-17 04:41:49 +0200 <hololeap> "we have 999 specialists, but we can afford the 1000th one" or something like that, until it works...
2022-04-17 04:42:05 +0200justsomeguy(~justsomeg@user/justsomeguy) (Quit: WeeChat 3.4)
2022-04-17 04:42:10 +0200Cale(~cale@cpef48e38ee8583-cm30b7d4b3fc20.cpe.net.cable.rogers.com)
2022-04-17 04:42:32 +0200slack1256(~slack1256@191.126.227.223)
2022-04-17 04:42:33 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat)
2022-04-17 04:43:05 +0200 <davean> Theres something like 10B USD just in looking for a fix to "this one particular computing problem is slow so can't enter new markets"
2022-04-17 04:43:09 +0200 <davean> for one given problem
2022-04-17 04:43:37 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1)
2022-04-17 04:43:54 +0200 <davean> Computers are currently too slow for the problems we have today, from a server perspective :)
2022-04-17 04:44:13 +0200joo-_(~joo-_@fsf/member/joo--) (Ping timeout: 246 seconds)
2022-04-17 04:44:14 +0200Victor_Huang(~Victor_Hu@103.197.70.229)
2022-04-17 04:45:13 +0200 <hololeap> maybe we should redistribute the funds to making people healthier and more educated, instead of spending it on more cpus
2022-04-17 04:45:33 +0200 <davean> You've sorta propose a contradictory goal there to a large degree
2022-04-17 04:45:41 +0200 <davean> a lot of that is making people healthier at least
2022-04-17 04:46:05 +0200 <davean> Do you ahve any idea how much compute things like medical imaging takes?
2022-04-17 04:46:06 +0200 <hololeap> I would expect to see a strong upward trend in life expentancy at least
2022-04-17 04:46:20 +0200joo-_(~joo-_@80-62-117-124-mobile.dk.customer.tdc.net)
2022-04-17 04:46:20 +0200 <davean> and drug discovery
2022-04-17 04:46:20 +0200joo-_(~joo-_@80-62-117-124-mobile.dk.customer.tdc.net) (Changing host)
2022-04-17 04:46:20 +0200joo-_(~joo-_@fsf/member/joo--)
2022-04-17 04:46:22 +0200 <davean> etyc
2022-04-17 04:46:48 +0200deadmarshal_(~deadmarsh@95.38.231.67)
2022-04-17 04:46:50 +0200 <davean> hololeap: medical stuff isn't even the main driver of life expectance IIRC :/
2022-04-17 04:47:10 +0200 <davean> Though I can't recall the analysises ATM
2022-04-17 04:47:18 +0200 <davean> You said healthier, not life expectancy
2022-04-17 04:47:46 +0200 <hololeap> that's a good point. we don't want to spend the last 30 years of our lives in chemical labotomy
2022-04-17 04:48:18 +0200 <davean> perhaps you're interested in the metric "quality adjusted years of life"
2022-04-17 04:48:53 +0200 <davean> But when you get to this stuff, I'm not sure we can directly apply money to society
2022-04-17 04:49:06 +0200 <davean> Money isn't *that* fungible
2022-04-17 04:52:01 +0200slack1256is in love with the `jacinda` package/lang.
2022-04-17 04:53:57 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 05:09:35 +0200stiell_(~stiell@gateway/tor-sasl/stiell) (Ping timeout: 240 seconds)
2022-04-17 05:16:16 +0200Lycurgus(~juan@98.4.112.204)
2022-04-17 05:20:22 +0200 <Lycurgus> currently life style/environment followed by genetics are still the main determiners of life expectancy, with the latter pulling ahead of the former
2022-04-17 05:20:31 +0200 <Lycurgus> in the developed countries at least
2022-04-17 05:22:22 +0200inversed(~inversed@94.13.111.159) (Ping timeout: 272 seconds)
2022-04-17 05:23:31 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 05:23:34 +0200sarupbanskota(~sarupbans@2601:645:8500:dc0:1cba:bfa3:5d61:5fe2) (Quit: Client closed)
2022-04-17 05:24:05 +0200stiell_(~stiell@gateway/tor-sasl/stiell)
2022-04-17 05:25:47 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 240 seconds)
2022-04-17 05:26:01 +0200 <Lycurgus> and like 10 out of 11 or better super centenarians are female
2022-04-17 05:27:44 +0200 <Lycurgus> 80% of centenarians apparently
2022-04-17 05:28:15 +0200 <Lycurgus> patriarchy 0, roar 1
2022-04-17 05:29:26 +0200 <Lycurgus> JC's record will prolly be passed by a japanese woman by mid century or so
2022-04-17 05:30:55 +0200 <Lycurgus> by which time nemowhosits and nak can eat crow in the devolved RF
2022-04-17 05:33:29 +0200Lycurgus(~juan@98.4.112.204) (Quit: Exeunt)
2022-04-17 05:36:47 +0200raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 240 seconds)
2022-04-17 05:42:42 +0200sarupbanskota(~sarupbans@c-71-198-153-147.hsd1.ca.comcast.net)
2022-04-17 05:47:55 +0200deadmarshal_(~deadmarsh@95.38.231.67) (Ping timeout: 246 seconds)
2022-04-17 05:50:42 +0200 <dsal> /join haskell
2022-04-17 05:51:15 +0200 <abastro[m]> Quite funny how Intel stagnated and watched how other companies struggle
2022-04-17 05:51:24 +0200 <abastro[m]> Like wh, monopoly power go brrrrr
2022-04-17 05:51:41 +0200 <abastro[m]> Basically "Deal with it" corporate edition
2022-04-17 05:54:33 +0200 <abastro[m]> Btw I think making ppl healthier is actually against the direction money wants
2022-04-17 05:55:32 +0200harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2022-04-17 05:56:50 +0200cdman(~dcm@27.2.216.214)
2022-04-17 05:56:50 +0200cdman(~dcm@27.2.216.214) (Changing host)
2022-04-17 05:56:50 +0200cdman(~dcm@user/dmc/x-4369397)
2022-04-17 06:04:30 +0200argento(~argent0@168-227-97-23.ptr.westnet.com.ar) (Quit: leaving)
2022-04-17 06:04:55 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 240 seconds)
2022-04-17 06:05:27 +0200bontaq(~user@ool-45779fe5.dyn.optonline.net)
2022-04-17 06:05:55 +0200wroathe(~wroathe@user/wroathe) (Ping timeout: 256 seconds)
2022-04-17 06:05:58 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470) (Remote host closed the connection)
2022-04-17 06:07:31 +0200inversed(~inversed@94.13.111.159)
2022-04-17 06:08:02 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2022-04-17 06:10:16 +0200xff0x_(~xff0x@i121-117-52-147.s41.a013.ap.plala.or.jp)
2022-04-17 06:13:56 +0200waleee(~waleee@2001:9b0:213:7200:cc36:a556:b1e8:b340) (Ping timeout: 250 seconds)
2022-04-17 06:17:47 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-17 06:23:33 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 06:24:10 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Client Quit)
2022-04-17 06:26:49 +0200flinner(~flinner@user/flinner)
2022-04-17 06:26:53 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 256 seconds)
2022-04-17 06:27:27 +0200dolio(~dolio@130.44.130.54) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-17 06:29:21 +0200dolio(~dolio@130.44.130.54)
2022-04-17 06:29:21 +0200dolio(~dolio@130.44.130.54) (Client Quit)
2022-04-17 06:29:49 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-17 06:32:56 +0200zebrag(~chris@user/zebrag) (Quit: Konversation terminated!)
2022-04-17 06:36:24 +0200dolio(~dolio@130.44.130.54)
2022-04-17 06:52:08 +0200Benzi-Junior(~BenziJuni@dsl-149-64-179.hive.is) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-17 06:56:04 +0200link(~link@197.210.28.238)
2022-04-17 06:56:56 +0200slack1256(~slack1256@191.126.227.223) (Remote host closed the connection)
2022-04-17 06:59:17 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection)
2022-04-17 06:59:44 +0200mixfix41(~sdenynine@user/mixfix41) (Quit: signing off cya)
2022-04-17 07:02:48 +0200xff0x_(~xff0x@i121-117-52-147.s41.a013.ap.plala.or.jp) (Ping timeout: 248 seconds)
2022-04-17 07:10:30 +0200Victor_Huang(~Victor_Hu@103.197.70.229) (Ping timeout: 250 seconds)
2022-04-17 07:14:26 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 07:17:00 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-04-17 07:17:11 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 07:22:55 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 07:26:44 +0200nun51(~nun@119.131.229.149)
2022-04-17 07:36:24 +0200flinner(~flinner@user/flinner) (Ping timeout: 248 seconds)
2022-04-17 07:38:09 +0200whatsupdoc(uid509081@id-509081.hampstead.irccloud.com)
2022-04-17 07:38:55 +0200takuan(~takuan@178-116-218-225.access.telenet.be)
2022-04-17 07:39:17 +0200stefan-_(~cri@42dots.de) (Ping timeout: 260 seconds)
2022-04-17 07:43:25 +0200stefan-_(~cri@42dots.de)
2022-04-17 07:45:16 +0200Pickchea(~private@user/pickchea)
2022-04-17 07:46:00 +0200kmein(~weechat@user/kmein) (Quit: ciao kakao)
2022-04-17 07:46:39 +0200kmein(~weechat@user/kmein)
2022-04-17 07:46:54 +0200frost(~frost@user/frost) (Ping timeout: 250 seconds)
2022-04-17 07:49:49 +0200 <Digit> short money, maybe. racing to the bottom might not be the only "option" though.
2022-04-17 07:50:04 +0200link(~link@197.210.28.238) (Ping timeout: 246 seconds)
2022-04-17 07:57:04 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2022-04-17 08:07:24 +0200johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Quit: ZNC - http://znc.in)
2022-04-17 08:18:51 +0200mmhat(~mmh@55d49239.access.ecotel.net)
2022-04-17 08:19:09 +0200Leary(~leary@122-58-90-96-vdsl.sparkbb.co.nz)
2022-04-17 08:19:45 +0200Digit(~user@user/digit) (Remote host closed the connection)
2022-04-17 08:22:12 +0200Leary[Leary]
2022-04-17 08:25:43 +0200axeman(~quassel@2a02:8109:a380:78:a30e:f3ea:6f40:1ffc)
2022-04-17 08:26:46 +0200[Leary]Lears
2022-04-17 08:27:10 +0200Pickchea(~private@user/pickchea) (Ping timeout: 246 seconds)
2022-04-17 08:28:25 +0200echoreply(~echoreply@45.32.163.16) (Quit: WeeChat 2.8)
2022-04-17 08:28:53 +0200echoreply(~echoreply@45.32.163.16)
2022-04-17 08:31:10 +0200vgtw(~vgtw@user/vgtw) (Quit: ZNC - https://znc.in)
2022-04-17 08:35:53 +0200Lears(~leary@122-58-90-96-vdsl.sparkbb.co.nz) ()
2022-04-17 08:36:09 +0200jakalx(~jakalx@base.jakalx.net) ()
2022-04-17 08:36:55 +0200[Leary](~Leary]@122-58-90-96-vdsl.sparkbb.co.nz)
2022-04-17 08:38:58 +0200gurkenglas(~gurkengla@dslb-178-012-018-212.178.012.pools.vodafone-ip.de)
2022-04-17 08:43:32 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-04-17 08:46:36 +0200jakalx(~jakalx@base.jakalx.net)
2022-04-17 08:49:41 +0200coot(~coot@213.134.190.95)
2022-04-17 08:50:09 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection)
2022-04-17 08:50:11 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2022-04-17 08:50:38 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2022-04-17 08:51:17 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2022-04-17 08:52:34 +0200acidjnk(~acidjnk@p200300d0c722df980150968fc3b616d7.dip0.t-ipconnect.de)
2022-04-17 08:54:07 +0200kaph(~kaph@37.39.168.109.cust.ip.kpnqwest.it) (Ping timeout: 240 seconds)
2022-04-17 08:58:07 +0200axeman(~quassel@2a02:8109:a380:78:a30e:f3ea:6f40:1ffc) (Ping timeout: 240 seconds)
2022-04-17 09:00:56 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 09:00:58 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 09:01:11 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection)
2022-04-17 09:01:35 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2022-04-17 09:06:15 +0200gehmehgeh(~user@user/gehmehgeh)
2022-04-17 09:09:31 +0200xkuru(~xkuru@user/xkuru) (Read error: Connection reset by peer)
2022-04-17 09:12:51 +0200jakalx(~jakalx@base.jakalx.net) (Disconnected: Replaced by new connection)
2022-04-17 09:12:52 +0200jakalx(~jakalx@base.jakalx.net)
2022-04-17 09:14:39 +0200axeman(~quassel@2a02:8109:a380:78:91f:3294:a86:55c4)
2022-04-17 09:21:18 +0200fendor(~fendor@178.115.59.109.wireless.dyn.drei.com)
2022-04-17 09:28:15 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 09:29:22 +0200sarupbanskota(~sarupbans@c-71-198-153-147.hsd1.ca.comcast.net) (Quit: Client closed)
2022-04-17 09:35:58 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-04-17 09:36:35 +0200gehmehgeh(~user@user/gehmehgeh) (Ping timeout: 240 seconds)
2022-04-17 09:37:16 +0200gehmehgeh(~user@user/gehmehgeh)
2022-04-17 09:44:57 +0200Midjak(~Midjak@82.66.147.146)
2022-04-17 09:51:31 +0200odnes(~odnes@5-203-180-192.pat.nym.cosmote.net)
2022-04-17 09:51:36 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 09:52:04 +0200vgtw(~vgtw@user/vgtw)
2022-04-17 10:01:12 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2022-04-17 10:02:07 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 240 seconds)
2022-04-17 10:06:16 +0200jmdaemon(~jmdaemon@user/jmdaemon) (Ping timeout: 248 seconds)
2022-04-17 10:14:23 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)
2022-04-17 10:22:55 +0200littlebo1eep(~alMalsamo@gateway/tor-sasl/almalsamo) (Ping timeout: 240 seconds)
2022-04-17 10:25:08 +0200littlebobeep(~alMalsamo@gateway/tor-sasl/almalsamo)
2022-04-17 10:30:29 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 10:33:52 +0200 <abastro> Does packages rebuild when even `allow-newer` part for unrelated package is updated?
2022-04-17 10:34:41 +0200 <abastro> Wait, I guess what's the problem. The dependency in between somewhere cannot support newest version I guess..
2022-04-17 10:34:55 +0200 <abastro> Which requires the package to be rebuilt, and any layers lower are built again as well
2022-04-17 10:34:56 +0200 <abastro> MEH
2022-04-17 10:35:11 +0200 <abastro> So that takes 20 minutes+
2022-04-17 10:36:02 +0200anomal(~anomal@87.227.196.109)
2022-04-17 10:36:25 +0200chomwitt(~chomwitt@ppp-94-69-27-34.home.otenet.gr)
2022-04-17 10:38:37 +0200_ht(~quassel@231-169-21-31.ftth.glasoperator.nl)
2022-04-17 10:39:03 +0200bontaq(~user@ool-45779fe5.dyn.optonline.net) (Ping timeout: 256 seconds)
2022-04-17 10:44:45 +0200fciocan(~fciocan@188.24.47.102)
2022-04-17 10:46:09 +0200DNH(~DNH@8.43.122.67)
2022-04-17 10:49:56 +0200zeenk(~zeenk@2a02:2f04:a313:d600:8d26:ec9f:3ff6:fc94)
2022-04-17 10:51:07 +0200axeman(~quassel@2a02:8109:a380:78:91f:3294:a86:55c4) (Ping timeout: 240 seconds)
2022-04-17 10:54:17 +0200zer0bitz(~zer0bitz@2001:2003:f444:8f00:5d67:8c6d:de09:8205)
2022-04-17 10:58:15 +0200 <albet70> are there some famous sequences like fibonacci?
2022-04-17 10:58:56 +0200 <albet70> fib 22 is 17711, is a huge number
2022-04-17 11:00:06 +0200kalxd[m](~kalxdmatr@2001:470:69fc:105::1:576e) (Quit: You have been kicked for being idle)
2022-04-17 11:00:07 +0200justache(~justache@user/justache) (Read error: Connection reset by peer)
2022-04-17 11:00:08 +0200tsmc[m](~tsmcmatri@2001:470:69fc:105::1:7e1) (Quit: You have been kicked for being idle)
2022-04-17 11:00:48 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) (Ping timeout: 250 seconds)
2022-04-17 11:01:02 +0200justache(~justache@user/justache)
2022-04-17 11:02:13 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-04-17 11:02:31 +0200tzh(~tzh@c-24-21-73-154.hsd1.wa.comcast.net) (Quit: zzz)
2022-04-17 11:02:35 +0200DNH(~DNH@8.43.122.67) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2022-04-17 11:04:36 +0200fciocan(~fciocan@188.24.47.102) (Quit: Ping timeout (120 seconds))
2022-04-17 11:07:47 +0200deadmarshal_(~deadmarsh@95.38.231.67)
2022-04-17 11:08:17 +0200coot(~coot@213.134.190.95) (Quit: coot)
2022-04-17 11:09:13 +0200xff0x_(~xff0x@om126033110024.35.openmobile.ne.jp)
2022-04-17 11:12:56 +0200acidjnk(~acidjnk@p200300d0c722df980150968fc3b616d7.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2022-04-17 11:13:15 +0200coot(~coot@213.134.190.95)
2022-04-17 11:13:22 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 11:14:07 +0200whatsupdoc(uid509081@id-509081.hampstead.irccloud.com) (Quit: Connection closed for inactivity)
2022-04-17 11:16:33 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 11:16:40 +0200nun51(~nun@119.131.229.149) (Ping timeout: 248 seconds)
2022-04-17 11:18:14 +0200rembo10(~rembo10@main.remulis.com) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-17 11:18:45 +0200 <pavonia> Prime numbers are the most famous, I guess
2022-04-17 11:19:10 +0200rembo10(~rembo10@main.remulis.com)
2022-04-17 11:21:33 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 256 seconds)
2022-04-17 11:26:44 +0200Natch(~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection)
2022-04-17 11:27:04 +0200 <zzz> albet70: try #math
2022-04-17 11:27:07 +0200abastro(~abab9579@220.75.216.63) (Ping timeout: 240 seconds)
2022-04-17 11:33:39 +0200Macbethwin(~chargen@D964062A.static.ziggozakelijk.nl)
2022-04-17 11:35:42 +0200zer0bitz_(~zer0bitz@2001:2003:f444:8f00:c16e:99ad:f968:663c)
2022-04-17 11:36:56 +0200zer0bitz(~zer0bitz@2001:2003:f444:8f00:5d67:8c6d:de09:8205) (Ping timeout: 248 seconds)
2022-04-17 11:38:56 +0200 <abastro[m]> Btw for any a and b,
2022-04-17 11:38:56 +0200 <abastro[m]> `seq a b = go where go = a : b : zipWith (+) go (tail go)`
2022-04-17 11:38:56 +0200 <abastro[m]> forms a sequence
2022-04-17 11:39:07 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 256 seconds)
2022-04-17 11:40:42 +0200 <pavonia> Generalized Fibonacci sequences?
2022-04-17 11:40:57 +0200 <abastro[m]> Yea
2022-04-17 11:41:21 +0200jakalx(~jakalx@base.jakalx.net) (Error from remote client)
2022-04-17 11:42:04 +0200 <abastro[m]> Then there are boring sequences like `iterate (+n) 0`, `iterate (*n) 1`
2022-04-17 11:42:13 +0200 <abastro[m]> Which are still important anyway IIRC
2022-04-17 11:42:48 +0200zer0bitz_(~zer0bitz@2001:2003:f444:8f00:c16e:99ad:f968:663c) (Ping timeout: 248 seconds)
2022-04-17 11:43:27 +0200 <abastro[m]> > iterate (2 ^) 0
2022-04-17 11:43:29 +0200 <lambdabot> [0,1,2,4,16,65536,2003529930406846464979072351560255750447825475569751419265...
2022-04-17 11:44:02 +0200 <abastro[m]> That also had a name iirc
2022-04-17 11:44:18 +0200zer0bitz(~zer0bitz@2001:2003:f444:8f00:c8bc:45b2:2fda:b1e9)
2022-04-17 11:46:41 +0200 <abastro[m]> Oh, Tetration
2022-04-17 12:00:29 +0200Macbethwinieeesebel
2022-04-17 12:03:42 +0200zer0bitz_(~zer0bitz@2001:2003:f444:8f00:448a:96f0:1d30:764e)
2022-04-17 12:04:40 +0200zer0bitz(~zer0bitz@2001:2003:f444:8f00:c8bc:45b2:2fda:b1e9) (Ping timeout: 248 seconds)
2022-04-17 12:06:16 +0200coot(~coot@213.134.190.95) (Quit: coot)
2022-04-17 12:09:13 +0200zer0bitz_(~zer0bitz@2001:2003:f444:8f00:448a:96f0:1d30:764e) (Read error: Connection reset by peer)
2022-04-17 12:12:09 +0200 <jackdk> albet70: you may find some useful names in the online encyclopaedia of integer sequences (OEIS)
2022-04-17 12:13:00 +0200econo(uid147250@user/econo) (Quit: Connection closed for inactivity)
2022-04-17 12:17:22 +0200odnes_(~odnes@5-203-200-233.pat.nym.cosmote.net)
2022-04-17 12:18:01 +0200sprout(~quassel@2a02-a467-ccd6-1-d47-e8be-40dc-4588.fixed6.kpn.net) (Ping timeout: 248 seconds)
2022-04-17 12:18:26 +0200odnes(~odnes@5-203-180-192.pat.nym.cosmote.net) (Read error: Connection reset by peer)
2022-04-17 12:21:02 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2022-04-17 12:27:09 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2022-04-17 12:27:37 +0200deadmarshal_(~deadmarsh@95.38.231.67) (Ping timeout: 246 seconds)
2022-04-17 12:29:56 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi) (Read error: Connection reset by peer)
2022-04-17 12:30:25 +0200Vajb(~Vajb@2001:999:504:1dda:267d:6860:bdf7:f68b)
2022-04-17 12:30:31 +0200Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2022-04-17 12:33:03 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2022-04-17 12:34:02 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2022-04-17 12:39:09 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2022-04-17 12:41:11 +0200Benzi-Junior(~BenziJuni@88-149-64-179.du.xdsl.is)
2022-04-17 12:42:28 +0200odnes_(~odnes@5-203-200-233.pat.nym.cosmote.net) (Remote host closed the connection)
2022-04-17 12:42:50 +0200odnes_(~odnes@5-203-200-233.pat.nym.cosmote.net)
2022-04-17 12:44:25 +0200jakalx(~jakalx@base.jakalx.net)
2022-04-17 12:47:15 +0200littlebobeep(~alMalsamo@gateway/tor-sasl/almalsamo) (Ping timeout: 240 seconds)
2022-04-17 12:53:03 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)
2022-04-17 12:55:04 +0200muhammadnaqdi(~user@91.98.164.53)
2022-04-17 12:55:11 +0200zer0bitz(~zer0bitz@2001:2003:f444:8f00:d49:457:7f2b:1073)
2022-04-17 12:58:26 +0200 <ManofLetters[m]> hi! I need help: how to best express partial application of a type function if the order of its arguments is wrong? Currently I'm using... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8eabe24135f9de2938dc8f06f690b789c5dc…)
2022-04-17 12:58:45 +0200nate1(~nate@98.45.169.16)
2022-04-17 12:59:23 +0200odnes_(~odnes@5-203-200-233.pat.nym.cosmote.net) (Remote host closed the connection)
2022-04-17 12:59:51 +0200 <geekosaur> there is type level Flip somewhere
2022-04-17 13:00:17 +0200 <geekosaur> that said, partial application at type level is somewhat problematic
2022-04-17 13:02:10 +0200vysn(~vysn@user/vysn) (Quit: WeeChat 3.4)
2022-04-17 13:02:57 +0200pretty_dumm_guy(trottel@gateway/vpn/protonvpn/prettydummguy/x-88029655)
2022-04-17 13:03:33 +0200nate1(~nate@98.45.169.16) (Ping timeout: 256 seconds)
2022-04-17 13:04:55 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 13:08:43 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-04-17 13:08:58 +0200abastro(~abab9579@220.75.216.63)
2022-04-17 13:09:35 +0200hololeap(~hololeap@user/hololeap) (Ping timeout: 240 seconds)
2022-04-17 13:09:56 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 13:14:48 +0200boxscape_(~boxscape_@p4ff0b7be.dip0.t-ipconnect.de)
2022-04-17 13:16:15 +0200ss4(~wootehfoo@user/wootehfoot)
2022-04-17 13:17:35 +0200gehmehgeh(~user@user/gehmehgeh) (Ping timeout: 240 seconds)
2022-04-17 13:17:53 +0200 <boxscape_> :t let x x = x in x x
2022-04-17 13:17:54 +0200 <lambdabot> p -> p
2022-04-17 13:18:24 +0200vysn(~vysn@user/vysn)
2022-04-17 13:18:43 +0200axeman(~quassel@2a02:8109:a380:78:e2e1:c866:45da:63b)
2022-04-17 13:18:51 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Ping timeout: 256 seconds)
2022-04-17 13:21:44 +0200hololeap(~hololeap@user/hololeap) (Remote host closed the connection)
2022-04-17 13:23:16 +0200gehmehgeh(~user@user/gehmehgeh)
2022-04-17 13:27:04 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 13:31:48 +0200Pickchea(~private@user/pickchea)
2022-04-17 13:35:09 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 13:36:15 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 13:37:38 +0200 <hpc> > let x x = x in x x "x"
2022-04-17 13:37:40 +0200 <lambdabot> "x"
2022-04-17 13:37:42 +0200 <hpc> :D
2022-04-17 13:39:49 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Ping timeout: 256 seconds)
2022-04-17 13:48:24 +0200 <abastro> How do I set `-haddock` ghc flag as default to use on all projects?
2022-04-17 13:48:46 +0200AlexNoo_AlexNoo
2022-04-17 13:52:23 +0200neceve(~quassel@2.29.116.221)
2022-04-17 13:54:04 +0200 <geekosaur> if you're using cabal, there'sa specific flag for it in ~/.cabal/config ("documentation: true" iirc)
2022-04-17 13:54:13 +0200Guest|10(~Guest|10@78-58-191-226.static.zebra.lt)
2022-04-17 13:54:46 +0200Guest|10(~Guest|10@78-58-191-226.static.zebra.lt) (Client Quit)
2022-04-17 13:54:59 +0200 <ManofLetters[m]> geekosaur: thank you; it's https://hackage.haskell.org/package/type-combinators-0.2.4.3/docs/Data-Type-Combinator.html#t:Flip; it should be clearer in some contexts, but unfortunately it requires just as many coercions (being a newtype)
2022-04-17 13:57:35 +0200Guest6(~Guest6@41.216.204.136)
2022-04-17 13:58:07 +0200Guest6(~Guest6@41.216.204.136) (Client Quit)
2022-04-17 13:59:02 +0200califax(~califax@user/califx) (Remote host closed the connection)
2022-04-17 13:59:05 +0200Pickchea(~private@user/pickchea) (Ping timeout: 256 seconds)
2022-04-17 13:59:53 +0200hololeap(~hololeap@user/hololeap) (Remote host closed the connection)
2022-04-17 13:59:59 +0200euandreh(~euandreh@2804:14c:33:9fe5:f4eb:139c:3daf:9882)
2022-04-17 13:59:59 +0200califax(~califax@user/califx)
2022-04-17 14:01:03 +0200Unicorn_Princess(~Unicorn_P@93-103-228-248.dynamic.t-2.net)
2022-04-17 14:02:22 +0200euandreh_(~euandreh@2804:14c:33:9fe5:be1f:339b:bf2e:3750) (Ping timeout: 250 seconds)
2022-04-17 14:02:48 +0200 <abastro[m]> documentation: true? I see, thank you
2022-04-17 14:04:03 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 14:04:40 +0200euandreh(~euandreh@2804:14c:33:9fe5:f4eb:139c:3daf:9882) (Ping timeout: 248 seconds)
2022-04-17 14:05:12 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) (Ping timeout: 248 seconds)
2022-04-17 14:08:04 +0200 <abastro> geekosaur: `documentation: True` recompiles everything even though I had `-haddock` compiler flag on.
2022-04-17 14:08:30 +0200 <abastro> Why is this?
2022-04-17 14:08:45 +0200machinedgod(~machinedg@24.105.81.50)
2022-04-17 14:08:48 +0200 <geekosaur> it includes additional flags like --hyperlink-source
2022-04-17 14:09:21 +0200 <geekosaur> beyoond that I think you would have to ask sclv, but I suspect people requested it because they were annoyed they had to rebuild everything manually after changing it
2022-04-17 14:09:57 +0200littlebobeep(~alMalsamo@gateway/tor-sasl/almalsamo)
2022-04-17 14:10:07 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 240 seconds)
2022-04-17 14:10:19 +0200 <abastro> Oh, I see
2022-04-17 14:10:39 +0200 <abastro> Perhaps I would purge once more? Ah no, it would be fine to have one more copy... *cries*
2022-04-17 14:12:34 +0200vysn(~vysn@user/vysn) (Quit: WeeChat 3.4)
2022-04-17 14:12:49 +0200 <geekosaur> monochrom has a tool for maintaining / cleaning cabal stores. https://github.com/treblacy/cabalgc
2022-04-17 14:13:25 +0200 <abastro> Yep, I mean I tried it, but last time it failed to delete handful of duplicated copies.
2022-04-17 14:13:47 +0200 <geekosaur> (I have an extra 2 copies of everything currently because I gave my testing sandbox its own .ghcup and .cabal, and accidentally built everything for 8.10.7 initially :)
2022-04-17 14:14:55 +0200littlebobeep(~alMalsamo@gateway/tor-sasl/almalsamo) (Ping timeout: 240 seconds)
2022-04-17 14:15:27 +0200 <geekosaur> mm, and a few more copies becuase I rebuilt everything with -g
2022-04-17 14:15:40 +0200 <geekosaur> copies copies everywhere :)
2022-04-17 14:15:52 +0200 <abastro> :o
2022-04-17 14:16:05 +0200 <abastro> Anyway, I am now back at 5GB store
2022-04-17 14:16:27 +0200 <abastro> Guess I won't mind :P
2022-04-17 14:17:30 +0200littlebobeep(~alMalsamo@gateway/tor-sasl/almalsamo)
2022-04-17 14:17:37 +0200deadmarshal_(~deadmarsh@95.38.231.67)
2022-04-17 14:18:29 +0200ZanpakutoB(~Zanpakuto@2405:204:a399:44f6:9017:ee41:371c:198f)
2022-04-17 14:19:40 +0200ntinoom^(~ntinoom@50.226.13.122)
2022-04-17 14:22:04 +0200deadmarshal_(~deadmarsh@95.38.231.67) (Ping timeout: 246 seconds)
2022-04-17 14:32:59 +0200MajorBiscuit(~MajorBisc@86-88-79-148.fixed.kpn.net)
2022-04-17 14:34:11 +0200frost(~frost@user/frost)
2022-04-17 14:35:14 +0200chenqisu1(~chenqisu1@183.217.200.38) (Quit: Leaving)
2022-04-17 14:37:50 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 14:43:04 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 246 seconds)
2022-04-17 14:43:14 +0200RajatVerma[m](~rajatvmat@2001:470:69fc:105::1:fb34)
2022-04-17 14:50:04 +0200MajorBiscuit(~MajorBisc@86-88-79-148.fixed.kpn.net) (Ping timeout: 246 seconds)
2022-04-17 14:51:04 +0200darkstardevx(~darkstard@50.53.212.60) (Ping timeout: 248 seconds)
2022-04-17 14:53:51 +0200 <abastro> Guess some dependency around conduit is overly constrained by some higher-up package
2022-04-17 14:59:05 +0200phma(phma@2001:5b0:211f:3fe8:4742:ae6f:94a2:91e2) (Read error: Connection reset by peer)
2022-04-17 14:59:45 +0200phma(phma@2001:5b0:212a:f9a8:e995:81c4:a7fc:5c82)
2022-04-17 15:01:12 +0200axeman(~quassel@2a02:8109:a380:78:e2e1:c866:45da:63b) (Ping timeout: 248 seconds)
2022-04-17 15:04:47 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-17 15:06:27 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-17 15:08:38 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 15:08:56 +0200razetime(~quassel@117.254.35.62)
2022-04-17 15:09:19 +0200mc47(~mc47@xmonad/TheMC47)
2022-04-17 15:09:44 +0200axeman(~quassel@2a02:8109:a380:78:208a:e3f7:38e6:9de3)
2022-04-17 15:12:43 +0200anomal(~anomal@87.227.196.109) (Remote host closed the connection)
2022-04-17 15:14:13 +0200shailangsa(~shailangs@host86-186-142-63.range86-186.btcentralplus.com) ()
2022-04-17 15:17:04 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-17 15:18:04 +0200mikoto-chan(~mikoto-ch@213.177.151.239)
2022-04-17 15:18:44 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-04-17 15:20:51 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2022-04-17 15:21:13 +0200jrm(~jrm@156.34.173.250) (Quit: ciao)
2022-04-17 15:22:38 +0200jrm(~jrm@156.34.173.250)
2022-04-17 15:30:42 +0200axeman(~quassel@2a02:8109:a380:78:208a:e3f7:38e6:9de3) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2022-04-17 15:35:15 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 240 seconds)
2022-04-17 15:36:27 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 15:37:15 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2022-04-17 15:41:05 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Ping timeout: 256 seconds)
2022-04-17 15:45:08 +0200coot(~coot@213.134.190.95)
2022-04-17 15:48:34 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Remote host closed the connection)
2022-04-17 15:49:07 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 15:51:19 +0200gabriel_sevecek(~gabriel@188-167-229-200.dynamic.chello.sk) (Quit: WeeChat 3.5)
2022-04-17 15:51:39 +0200gabriel_sevecek(~gabriel@188-167-229-200.dynamic.chello.sk)
2022-04-17 15:54:33 +0200Pickchea(~private@user/pickchea)
2022-04-17 15:54:38 +0200gabriel_sevecek(~gabriel@188-167-229-200.dynamic.chello.sk) (Client Quit)
2022-04-17 15:55:12 +0200gabriel_sevecek(~gabriel@188-167-229-200.dynamic.chello.sk)
2022-04-17 15:55:47 +0200razetime(~quassel@117.254.35.62) (Remote host closed the connection)
2022-04-17 16:02:29 +0200gehmehgeh(~user@user/gehmehgeh) (Remote host closed the connection)
2022-04-17 16:03:16 +0200gehmehgeh(~user@user/gehmehgeh)
2022-04-17 16:07:00 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 16:07:27 +0200ntinoom^(~ntinoom@50.226.13.122) (Remote host closed the connection)
2022-04-17 16:08:41 +0200hololeap(~hololeap@user/hololeap) (Read error: Connection reset by peer)
2022-04-17 16:08:41 +0200conjunctive(sid433686@id-433686.helmsley.irccloud.com) (Ping timeout: 245 seconds)
2022-04-17 16:09:19 +0200nrr___(sid20938@id-20938.lymington.irccloud.com) (Ping timeout: 256 seconds)
2022-04-17 16:10:34 +0200azimut(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2022-04-17 16:10:42 +0200conjunctive(sid433686@id-433686.helmsley.irccloud.com)
2022-04-17 16:10:57 +0200azimut(~azimut@gateway/tor-sasl/azimut)
2022-04-17 16:11:14 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 16:11:16 +0200nrr___(sid20938@id-20938.lymington.irccloud.com)
2022-04-17 16:16:22 +0200ZanpakutoB(~Zanpakuto@2405:204:a399:44f6:9017:ee41:371c:198f) (Remote host closed the connection)
2022-04-17 16:16:40 +0200ZanpakutoB(~Zanpakuto@2405:204:a399:44f6:9017:ee41:371c:198f)
2022-04-17 16:29:43 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com)
2022-04-17 16:29:43 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com) (Changing host)
2022-04-17 16:29:43 +0200wroathe(~wroathe@user/wroathe)
2022-04-17 16:31:58 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com)
2022-04-17 16:38:34 +0200DNH(~DNH@8.44.0.68)
2022-04-17 16:38:55 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 240 seconds)
2022-04-17 16:41:09 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 256 seconds)
2022-04-17 16:42:00 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2022-04-17 16:52:15 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 240 seconds)
2022-04-17 16:54:17 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2022-04-17 16:59:51 +0200Pickchea(~private@user/pickchea) (Ping timeout: 256 seconds)
2022-04-17 17:03:49 +0200machinedgod(~machinedg@24.105.81.50) (Ping timeout: 256 seconds)
2022-04-17 17:06:12 +0200pagnol(~user@014198154145.ctinets.com)
2022-04-17 17:06:49 +0200kenran(~kenran@200116b82ba94b00de0a59f3cf1cacd6.dip.versatel-1u1.de)
2022-04-17 17:07:24 +0200systemfault(sid267009@id-267009.uxbridge.irccloud.com) (Ping timeout: 240 seconds)
2022-04-17 17:09:12 +0200systemfault(sid267009@id-267009.uxbridge.irccloud.com)
2022-04-17 17:10:54 +0200 <pagnol> is there a straightforward [Either e a] -> Either [e] [a]?
2022-04-17 17:11:19 +0200 <boxscape_> @hoogle partitionEithers
2022-04-17 17:11:19 +0200 <lambdabot> Data.Either partitionEithers :: [Either a b] -> ([a], [b])
2022-04-17 17:11:19 +0200 <lambdabot> Data.Strict.Either partitionEithers :: [Either a b] -> ([a], [b])
2022-04-17 17:11:19 +0200 <lambdabot> Protolude partitionEithers :: () => [Either a b] -> ([a], [b])
2022-04-17 17:11:31 +0200 <boxscape_> that's probably what you want
2022-04-17 17:11:50 +0200 <pagnol> ah yeah that's good, thanks
2022-04-17 17:12:27 +0200 <pagnol> at first I thought sequence, but that gives Either e [a] apparently
2022-04-17 17:13:18 +0200 <boxscape_> yeah, since `Either e` is the Functor here, sequence can't change that
2022-04-17 17:14:17 +0200 <pagnol> I see
2022-04-17 17:14:27 +0200wroathe(~wroathe@user/wroathe) (Ping timeout: 240 seconds)
2022-04-17 17:14:44 +0200niemand(~niemand@p54a9c9a9.dip0.t-ipconnect.de)
2022-04-17 17:14:49 +0200chexum(~quassel@gateway/tor-sasl/chexum) (Quit: No Ping reply in 180 seconds.)
2022-04-17 17:15:11 +0200chexum(~quassel@gateway/tor-sasl/chexum)
2022-04-17 17:16:25 +0200 <boxscape_> pagnol if your goal is to collect a number of errors, you might also find Data.Either.Validation useful, from the either package
2022-04-17 17:17:06 +0200 <niemand> SCC pragmas don't affect optimization, do they?
2022-04-17 17:19:09 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com) (Remote host closed the connection)
2022-04-17 17:22:07 +0200pagnol(~user@014198154145.ctinets.com) (Ping timeout: 240 seconds)
2022-04-17 17:24:36 +0200muhammadnaqdi(~user@91.98.164.53) (Remote host closed the connection)
2022-04-17 17:24:46 +0200raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2022-04-17 17:29:10 +0200pagnol(~user@014198154145.ctinets.com)
2022-04-17 17:29:45 +0200DNH(~DNH@8.44.0.68) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2022-04-17 17:30:07 +0200waleee(~waleee@2001:9b0:213:7200:cc36:a556:b1e8:b340)
2022-04-17 17:30:48 +0200shailangsa(~shailangs@host86-186-142-63.range86-186.btcentralplus.com)
2022-04-17 17:31:40 +0200coot(~coot@213.134.190.95) (Quit: coot)
2022-04-17 17:35:02 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com)
2022-04-17 17:35:08 +0200pagnol(~user@014198154145.ctinets.com) (Ping timeout: 250 seconds)
2022-04-17 17:36:22 +0200DNH(~DNH@8.44.0.68)
2022-04-17 17:39:35 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com) (Ping timeout: 260 seconds)
2022-04-17 17:44:45 +0200frost(~frost@user/frost) (Quit: Client closed)
2022-04-17 17:45:11 +0200niemand(~niemand@p54a9c9a9.dip0.t-ipconnect.de) (Ping timeout: 256 seconds)
2022-04-17 17:53:47 +0200abastro(~abab9579@220.75.216.63) (Ping timeout: 240 seconds)
2022-04-17 17:55:57 +0200cdman(~dcm@user/dmc/x-4369397) (Ping timeout: 256 seconds)
2022-04-17 17:57:50 +0200Brandon_IX(~brandon@178-79-138-117.ip.linodeusercontent.com)
2022-04-17 17:58:03 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 18:04:08 +0200xff0x_(~xff0x@om126033110024.35.openmobile.ne.jp) (Read error: Connection reset by peer)
2022-04-17 18:04:18 +0200zincy(~zincy@86.160.236.152)
2022-04-17 18:05:44 +0200joo-_(~joo-_@fsf/member/joo--) (Ping timeout: 248 seconds)
2022-04-17 18:05:56 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Remote host closed the connection)
2022-04-17 18:07:05 +0200ChanServ+o litharge
2022-04-17 18:07:06 +0200litharge-bo *!*@86.32.51.33 litharge
2022-04-17 18:07:27 +0200joo-_(~joo-_@80-62-117-45-mobile.dk.customer.tdc.net)
2022-04-17 18:07:27 +0200joo-_(~joo-_@80-62-117-45-mobile.dk.customer.tdc.net) (Changing host)
2022-04-17 18:07:27 +0200joo-_(~joo-_@fsf/member/joo--)
2022-04-17 18:08:59 +0200zincy(~zincy@86.160.236.152) (Ping timeout: 256 seconds)
2022-04-17 18:10:07 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 18:10:28 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 18:13:12 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2022-04-17 18:17:10 +0200jacks2(~bc8147f2@cerf.good1.com)
2022-04-17 18:18:13 +0200 <jacks2> is there some naming convention that one should follow for having top-level variables, especially if they are mutable references?
2022-04-17 18:20:24 +0200vicfred(~vicfred@user/vicfred) (Quit: Leaving)
2022-04-17 18:25:50 +0200vicfred(~vicfred@user/vicfred)
2022-04-17 18:26:11 +0200tzh(~tzh@c-24-21-73-154.hsd1.or.comcast.net)
2022-04-17 18:26:25 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com)
2022-04-17 18:29:49 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)
2022-04-17 18:29:58 +0200sprout(~quassel@2a02-a467-ccd6-1-61ea-c654-ec6a-777e.fixed6.kpn.net)
2022-04-17 18:30:34 +0200zincy(~zincy@host86-160-236-152.range86-160.btcentralplus.com) (Ping timeout: 246 seconds)
2022-04-17 18:34:09 +0200jmdaemon(~jmdaemon@user/jmdaemon)
2022-04-17 18:35:04 +0200Vajb(~Vajb@2001:999:504:1dda:267d:6860:bdf7:f68b) (Read error: Connection reset by peer)
2022-04-17 18:35:58 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi)
2022-04-17 18:37:30 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 18:45:54 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d)
2022-04-17 18:47:18 +0200atrptoom^(~atrptoom@50-192-56-193-static.hfc.comcastbusiness.net)
2022-04-17 18:48:19 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi) (Read error: Connection reset by peer)
2022-04-17 18:49:28 +0200boxscape_(~boxscape_@p4ff0b7be.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2022-04-17 18:56:04 +0200deadmarshal_(~deadmarsh@95.38.231.67)
2022-04-17 19:01:21 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net) (Ping timeout: 252 seconds)
2022-04-17 19:10:16 +0200econo(uid147250@user/econo)
2022-04-17 19:11:53 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 256 seconds)
2022-04-17 19:13:47 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 19:15:04 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) (Ping timeout: 248 seconds)
2022-04-17 19:17:06 +0200andrey_(~andrey@p508d53e7.dip0.t-ipconnect.de)
2022-04-17 19:18:07 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net) (Ping timeout: 256 seconds)
2022-04-17 19:19:20 +0200andrey__(~andrey@p200300dbcf409200f598c2566b8ed921.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2022-04-17 19:22:23 +0200ss4(~wootehfoo@user/wootehfoot) (Quit: Leaving)
2022-04-17 19:22:40 +0200wootehfoot(~wootehfoo@user/wootehfoot)
2022-04-17 19:24:00 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi)
2022-04-17 19:26:17 +0200coot(~coot@213.134.190.95)
2022-04-17 19:35:39 +0200abiss27(~abiss27@190.213.236.106)
2022-04-17 19:36:18 +0200abiss27(~abiss27@190.213.236.106) (Changing host)
2022-04-17 19:36:18 +0200abiss27(~abiss27@user/abiss)
2022-04-17 19:38:21 +0200abiss27(~abiss27@user/abiss) (Client Quit)
2022-04-17 19:45:36 +0200coot(~coot@213.134.190.95) (Ping timeout: 272 seconds)
2022-04-17 19:47:53 +0200slaydr(~slaydr@193.19.109.211)
2022-04-17 19:48:07 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d) (Ping timeout: 240 seconds)
2022-04-17 19:49:10 +0200 <slaydr> is the tuple - (,) - part of standard Prelude?
2022-04-17 19:50:20 +0200ZanpakutoB(~Zanpakuto@2405:204:a399:44f6:9017:ee41:371c:198f) (Ping timeout: 250 seconds)
2022-04-17 19:58:39 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)
2022-04-17 19:58:52 +0200 <slaydr> i would like to redefine the tuple for an exercise. Is there a way to remove the existing data definition?
2022-04-17 19:59:32 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi) (Read error: Connection reset by peer)
2022-04-17 19:59:50 +0200Vajb(~Vajb@hag-jnsbng11-58c3a8-176.dhcp.inet.fi)
2022-04-17 20:00:47 +0200deadmarshal_(~deadmarsh@95.38.231.67) (Ping timeout: 240 seconds)
2022-04-17 20:01:22 +0200 <dsal> slaydr: You mean you want the specific syntax? A tuple is just a generic product type, but it's not a library feature.
2022-04-17 20:02:00 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Quit: Leaving)
2022-04-17 20:02:02 +0200 <dsal> It's easy to make your own thing that's similar to tuple, but with more normal syntax.
2022-04-17 20:03:26 +0200 <slaydr> thanks. I did make a FlippedTuple that does what I want as a Functor instance, but I just wondered if I could actual use the (,) syntax someway...temporarily
2022-04-17 20:06:38 +0200anomal(~anomal@87.227.196.109)
2022-04-17 20:06:49 +0200motherfsck(~motherfsc@user/motherfsck) (Ping timeout: 246 seconds)
2022-04-17 20:07:12 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net)
2022-04-17 20:11:02 +0200ZanpakutoB(~Zanpakuto@2409:4063:6e90:c253:1835:dd0a:a50c:6a11)
2022-04-17 20:17:54 +0200zincy(~zincy@86.160.236.152)
2022-04-17 20:18:01 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net) (Ping timeout: 246 seconds)
2022-04-17 20:18:18 +0200 <dsal> I don't know if there's a language extension to treat tuples differently.
2022-04-17 20:18:19 +0200vicfred(~vicfred@user/vicfred) (Quit: Leaving)
2022-04-17 20:19:05 +0200 <dsal> It might be nice to be able to avoid default instances, but also, for that exact case, I tend to just use a bifunctor.
2022-04-17 20:19:08 +0200 <dsal> :t first
2022-04-17 20:19:09 +0200 <lambdabot> Arrow a => a b c -> a (b, d) (c, d)
2022-04-17 20:19:17 +0200 <dsal> ugh. Not that first.
2022-04-17 20:19:18 +0200 <dsal> @hoogle first
2022-04-17 20:19:19 +0200 <lambdabot> Control.Arrow first :: Arrow a => a b c -> a (b, d) (c, d)
2022-04-17 20:19:19 +0200 <lambdabot> Data.Bifunctor first :: Bifunctor p => (a -> b) -> p a c -> p b c
2022-04-17 20:19:19 +0200 <lambdabot> Text.PrettyPrint.Annotated.HughesPJ first :: Doc a -> Doc a -> Doc a
2022-04-17 20:19:48 +0200 <dsal> I guess they're similar, but I use the bifunctor one with other bifunctors.
2022-04-17 20:20:17 +0200motherfsck(~motherfsc@user/motherfsck)
2022-04-17 20:22:43 +0200zincy(~zincy@86.160.236.152) (Ping timeout: 256 seconds)
2022-04-17 20:24:07 +0200 <zzz> can anyone explain why the second version of this subsets function consistently performs marginally better than the first one? https://paste.jrvieira.com/1650219787366
2022-04-17 20:24:37 +0200sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Remote host closed the connection)
2022-04-17 20:25:38 +0200kenran(~kenran@200116b82ba94b00de0a59f3cf1cacd6.dip.versatel-1u1.de) (Quit: WeeChat info:version)
2022-04-17 20:26:06 +0200 <dsal> zzz: You should be able to find the answer in the core.
2022-04-17 20:27:36 +0200 <zzz> that's a little too advanced for me
2022-04-17 20:30:23 +0200dyeplexer(~dyeplexer@user/dyeplexer) (Remote host closed the connection)
2022-04-17 20:30:35 +0200hololeap(~hololeap@user/hololeap) (Ping timeout: 240 seconds)
2022-04-17 20:31:15 +0200 <dsal> I understand why you might feel that way, but that's where the answer is. :) If you want to know, then learning to read the core would show you the answer both here and in your next performance question.
2022-04-17 20:32:22 +0200ZanpakutoB(~Zanpakuto@2409:4063:6e90:c253:1835:dd0a:a50c:6a11) (Ping timeout: 250 seconds)
2022-04-17 20:32:48 +0200MajorBiscuit(~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) (Ping timeout: 250 seconds)
2022-04-17 20:34:06 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 20:36:25 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d)
2022-04-17 20:43:29 +0200opqdonut_opqdonut
2022-04-17 20:45:33 +0200stackdroid18(14094@user/stackdroid)
2022-04-17 20:49:21 +0200CATS(apic@brezn3.muc.ccc.de) (Quit: Will rejoin shortly.)
2022-04-17 20:49:44 +0200abiss27(~abiss27@user/abiss)
2022-04-17 20:50:07 +0200xkuru(~xkuru@user/xkuru)
2022-04-17 20:50:19 +0200S_Cat(apic@brezn3.muc.ccc.de)
2022-04-17 20:51:37 +0200redb(~nmh@136.49.49.211) (Ping timeout: 256 seconds)
2022-04-17 20:53:26 +0200ishaan(~ishaan@122.161.53.177)
2022-04-17 20:57:10 +0200justsomeguy(~justsomeg@user/justsomeguy)
2022-04-17 20:57:29 +0200dextaa(~dextaa@user/dextaa)
2022-04-17 20:59:34 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com)
2022-04-17 20:59:34 +0200wroathe(~wroathe@206-55-188-8.fttp.usinternet.com) (Changing host)
2022-04-17 20:59:34 +0200wroathe(~wroathe@user/wroathe)
2022-04-17 21:02:14 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net)
2022-04-17 21:06:15 +0200Pickchea(~private@user/pickchea)
2022-04-17 21:08:08 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 21:08:26 +0200zincy_(~zincy@host86-160-236-152.range86-160.btcentralplus.com)
2022-04-17 21:08:29 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d) (Read error: Connection reset by peer)
2022-04-17 21:10:13 +0200ZanpakutoB(~Zanpakuto@2405:204:a399:44f6:7b57:7903:9fbc:7a5c)
2022-04-17 21:13:58 +0200wroathe(~wroathe@user/wroathe) (Ping timeout: 250 seconds)
2022-04-17 21:14:06 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net) (Read error: Connection reset by peer)
2022-04-17 21:14:23 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net)
2022-04-17 21:15:31 +0200justache(~justache@user/justache) (Remote host closed the connection)
2022-04-17 21:17:23 +0200justache(~justache@user/justache)
2022-04-17 21:17:44 +0200sndrsander
2022-04-17 21:18:05 +0200redb(~nmh@136.49.49.211)
2022-04-17 21:19:30 +0200justache(~justache@user/justache) (Remote host closed the connection)
2022-04-17 21:19:40 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Remote host closed the connection)
2022-04-17 21:20:15 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 21:21:36 +0200zincy_(~zincy@host86-160-236-152.range86-160.btcentralplus.com) (Remote host closed the connection)
2022-04-17 21:21:48 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d)
2022-04-17 21:23:06 +0200justache(~justache@user/justache)
2022-04-17 21:23:53 +0200ieeesebel(~chargen@D964062A.static.ziggozakelijk.nl) (Remote host closed the connection)
2022-04-17 21:23:55 +0200redb(~nmh@136.49.49.211) (Ping timeout: 256 seconds)
2022-04-17 21:24:29 +0200justache(~justache@user/justache) ()
2022-04-17 21:25:10 +0200ieeesebel(~chargen@D964062A.static.ziggozakelijk.nl)
2022-04-17 21:25:14 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 250 seconds)
2022-04-17 21:26:06 +0200 <statusbot> Status update: Many haskell.org websites are down due to an issue with our host. We are investigating. -- http://status.haskell.org/pages/incident/537c07b0cf1fad5830000093/625c69cdfcbdd204d4df5603
2022-04-17 21:26:14 +0200jonathanx(~jonathan@h-178-174-176-109.A357.priv.bahnhof.se)
2022-04-17 21:28:49 +0200abiss27(~abiss27@user/abiss) (Quit: hasta la vista... tchau!)
2022-04-17 21:30:16 +0200gawen(~gawen@user/gawen)
2022-04-17 21:30:21 +0200 <Athas> I have a strange issue issue with 'cabal haddock --haddock-for-hackage'. I get:
2022-04-17 21:30:26 +0200 <Athas> haddock: internal error: /home/athas/.cabal/store/ghc-9.0.2/Diff-0.4.1-04df2c01c87cfe54ff31f35bb1a20b246d6dcd854bf79ab8919d50738b1a79d3/share/doc/html/doc-index.json: openBinaryFile: does not exist (No such file or directory)
2022-04-17 21:30:29 +0200abiss27(~abiss27@user/abiss)
2022-04-17 21:30:48 +0200 <Athas> I suspect Diff fails merely because it is alphabetically first. None of the packages have doc-index.json files.
2022-04-17 21:31:27 +0200ishaanv[m](~ishaanvma@2001:470:69fc:105::1:fb72)
2022-04-17 21:35:02 +0200ieeesebel(~chargen@D964062A.static.ziggozakelijk.nl) (Remote host closed the connection)
2022-04-17 21:38:22 +0200 <koz> Is Hoogle down?
2022-04-17 21:38:36 +0200 <koz> Oh never mind, should have read above.
2022-04-17 21:39:54 +0200anomal(~anomal@87.227.196.109) (Remote host closed the connection)
2022-04-17 21:42:37 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl) (Ping timeout: 256 seconds)
2022-04-17 21:50:48 +0200redb(~nmh@136.49.49.211)
2022-04-17 21:54:04 +0200Sgeo(~Sgeo@user/sgeo)
2022-04-17 21:57:08 +0200kenran(~kenran@200116b82ba94b004c8de2398adb39d3.dip.versatel-1u1.de)
2022-04-17 21:59:35 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-17 22:00:34 +0200neceve(~quassel@2.29.116.221) (Ping timeout: 246 seconds)
2022-04-17 22:01:03 +0200mjs2600(~mjs2600@c-24-91-3-49.hsd1.vt.comcast.net)
2022-04-17 22:01:38 +0200acidjnk(~acidjnk@p200300d0c722df980150968fc3b616d7.dip0.t-ipconnect.de)
2022-04-17 22:04:43 +0200mikoto-chan(~mikoto-ch@213.177.151.239) (Ping timeout: 256 seconds)
2022-04-17 22:06:51 +0200mikoto-chan(~mikoto-ch@213.177.151.239)
2022-04-17 22:12:27 +0200redb(~nmh@136.49.49.211) (Ping timeout: 240 seconds)
2022-04-17 22:13:28 +0200redb(~nmh@136.49.49.211)
2022-04-17 22:18:14 +0200redb(~nmh@136.49.49.211) (Ping timeout: 272 seconds)
2022-04-17 22:20:20 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d) (Remote host closed the connection)
2022-04-17 22:20:34 +0200redb(~nmh@136.49.49.211)
2022-04-17 22:22:58 +0200machinedgod(~machinedg@24.105.81.50)
2022-04-17 22:23:02 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net)
2022-04-17 22:25:07 +0200redb(~nmh@136.49.49.211) (Ping timeout: 256 seconds)
2022-04-17 22:25:31 +0200andrey(~andrey@p200300dbcf4bfe0086461f96dc127065.dip0.t-ipconnect.de)
2022-04-17 22:26:57 +0200Lord_of_Life_(~Lord@user/lord-of-life/x-2819915)
2022-04-17 22:27:02 +0200redb(~nmh@136.49.49.211)
2022-04-17 22:27:36 +0200yauhsien(~yauhsien@61-231-24-129.dynamic-ip.hinet.net) (Ping timeout: 248 seconds)
2022-04-17 22:27:57 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 256 seconds)
2022-04-17 22:28:04 +0200andrey_(~andrey@p508d53e7.dip0.t-ipconnect.de) (Ping timeout: 250 seconds)
2022-04-17 22:28:13 +0200Lord_of_Life_Lord_of_Life
2022-04-17 22:29:08 +0200stackdroid18(14094@user/stackdroid) (Quit: hasta la vista... tchau!)
2022-04-17 22:29:35 +0200stackdroid18(14094@user/stackdroid)
2022-04-17 22:29:52 +0200stackdroid18(14094@user/stackdroid) (Client Quit)
2022-04-17 22:31:13 +0200abiss27(~abiss27@user/abiss) (Quit: hasta la vista... tchau!)
2022-04-17 22:33:37 +0200redb(~nmh@136.49.49.211) (Ping timeout: 256 seconds)
2022-04-17 22:35:32 +0200ubert(~Thunderbi@p200300ecdf15887a8d97c724330f0103.dip0.t-ipconnect.de) (Quit: ubert)
2022-04-17 22:39:32 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d)
2022-04-17 22:42:24 +0200redb(~nmh@136.49.49.211)
2022-04-17 22:42:53 +0200vicfred(~vicfred@user/vicfred)
2022-04-17 22:44:55 +0200abiss27(~abiss27@user/abiss)
2022-04-17 22:46:27 +0200redb(~nmh@136.49.49.211) (Ping timeout: 240 seconds)
2022-04-17 22:48:03 +0200eggplantade(~Eggplanta@108-201-191-115.lightspeed.sntcca.sbcglobal.net)
2022-04-17 22:50:05 +0200stackdroid18(14094@user/stackdroid)
2022-04-17 22:54:42 +0200mvk(~mvk@2607:fea8:5ce3:8500::85f6)
2022-04-17 23:04:15 +0200redb(~nmh@136.49.49.211)
2022-04-17 23:06:13 +0200takuan(~takuan@178-116-218-225.access.telenet.be) (Remote host closed the connection)
2022-04-17 23:08:28 +0200redb(~nmh@136.49.49.211) (Ping timeout: 246 seconds)
2022-04-17 23:10:02 +0200zincy(~zincy@2a00:23c8:970c:4801:613c:72c:460b:dd1d) (Remote host closed the connection)
2022-04-17 23:18:30 +0200jacks2(~bc8147f2@cerf.good1.com) (Quit: CGI:IRC (Session timeout))
2022-04-17 23:19:15 +0200hololeap(~hololeap@user/hololeap) (Ping timeout: 240 seconds)
2022-04-17 23:21:13 +0200dextaa(~dextaa@user/dextaa) (Ping timeout: 256 seconds)
2022-04-17 23:22:08 +0200hololeap(~hololeap@user/hololeap)
2022-04-17 23:23:45 +0200fendor(~fendor@178.115.59.109.wireless.dyn.drei.com) (Remote host closed the connection)
2022-04-17 23:26:11 +0200MajorBiscuit(~MajorBisc@86-88-79-148.fixed.kpn.net)
2022-04-17 23:31:22 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2022-04-17 23:32:35 +0200hololeap(~hololeap@user/hololeap) (Ping timeout: 240 seconds)
2022-04-17 23:36:54 +0200redb(~nmh@136.49.49.211)
2022-04-17 23:38:40 +0200tromp(~textual@dhcp-077-249-230-040.chello.nl)
2022-04-17 23:38:46 +0200merijn(~merijn@c-001-001-001.client.esciencecenter.eduvpn.nl)
2022-04-17 23:40:20 +0200_ht(~quassel@231-169-21-31.ftth.glasoperator.nl) (Remote host closed the connection)
2022-04-17 23:41:37 +0200redb(~nmh@136.49.49.211) (Ping timeout: 256 seconds)
2022-04-17 23:44:19 +0200mud(~mud@user/kadoban) (Remote host closed the connection)
2022-04-17 23:44:44 +0200mud(~mud@user/kadoban)
2022-04-17 23:47:46 +0200mmhat(~mmh@55d49239.access.ecotel.net) (Quit: WeeChat 3.5)
2022-04-17 23:53:58 +0200redb(~nmh@136.49.49.211)
2022-04-17 23:54:32 +0200jerry99(~339ea5e9@cerf.good1.com)
2022-04-17 23:55:35 +0200MajorBiscuit(~MajorBisc@86-88-79-148.fixed.kpn.net) (Quit: WeeChat 3.4)
2022-04-17 23:56:11 +0200gehmehgeh(~user@user/gehmehgeh) (Quit: Leaving)
2022-04-17 23:57:59 +0200fockerized(~nut@roc37-h01-176-170-197-243.dsl.sta.abo.bbox.fr) (Remote host closed the connection)
2022-04-17 23:58:16 +0200redb(~nmh@136.49.49.211) (Ping timeout: 248 seconds)
2022-04-17 23:58:31 +0200renzhi(~xp@2607:fa49:6500:b100::229c) (Ping timeout: 260 seconds)
2022-04-17 23:59:47 +0200malinoskj290(~malinoskj@48.170-avail-pool-cc.sccoast.net)