2024/05/30

Newest at the top

2024-05-30 14:36:53 +0200remmie(ianremsen@tilde.team) (Ping timeout: 240 seconds)
2024-05-30 14:36:05 +0200CiaoSen(~Jura@2a05:5800:2da:8d00:e6b9:7aff:fe80:3d03) (Ping timeout: 256 seconds)
2024-05-30 14:33:15 +0200son0p(~ff@191.104.16.31) (Ping timeout: 256 seconds)
2024-05-30 14:22:01 +0200sand-witch(~m-mzmz6l@vmi833741.contaboserver.net)
2024-05-30 14:21:01 +0200arthurvlearthy
2024-05-30 14:20:45 +0200arthurvl(~arthurvl@2a02-a469-f5e2-1-83d2-ca43-57a2-dc81.fixed6.kpn.net)
2024-05-30 14:20:30 +0200sand-witch(~m-mzmz6l@vmi833741.contaboserver.net) (Remote host closed the connection)
2024-05-30 14:11:12 +0200ddellacosta(~ddellacos@ool-44c73d29.dyn.optonline.net) (Ping timeout: 268 seconds)
2024-05-30 14:08:13 +0200xdminsy(~xdminsy@117.147.70.212)
2024-05-30 14:07:07 +0200xdminsy(~xdminsy@117.147.70.212) (Read error: Connection reset by peer)
2024-05-30 14:06:53 +0200 <__monty__> And TBF bad diagnostic messages are definitely a common thing. My favorite recent one is running a dynamically linked binary on Linux. If it can't find the runtime linker, something like /lib64/ld-linux-x86-64.so.2, you get the error, "sh: /path/to/your/binary/that/exists: No such file or directory"
2024-05-30 13:53:34 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-05-30 13:52:55 +0200danse-nr3(~danse-nr3@151.47.143.144) (Remote host closed the connection)
2024-05-30 13:52:06 +0200danse-nr3(~danse-nr3@151.47.143.144)
2024-05-30 13:49:29 +0200flounders(~flounders@24.246.176.178)
2024-05-30 13:48:23 +0200flounders(~flounders@24.246.176.178) (Ping timeout: 268 seconds)
2024-05-30 13:39:04 +0200Feuermagier(~Feuermagi@user/feuermagier) (Quit: Leaving)
2024-05-30 13:32:15 +0200danse-nr3(~danse-nr3@151.47.143.144) (Remote host closed the connection)
2024-05-30 13:29:48 +0200 <ncf> i don't think it's either of those things
2024-05-30 13:29:30 +0200remmie(ianremsen@tilde.team)
2024-05-30 13:25:09 +0200 <dminuoso> The first part was rather a bit of an interpretation
2024-05-30 13:24:51 +0200 <dminuoso> No, its really just confirmation bias.
2024-05-30 13:24:34 +0200 <tomsmeding> that sounds more like dunning-kruger than confirmation bias
2024-05-30 13:24:33 +0200 <dminuoso> Yeah, indeed.
2024-05-30 13:24:14 +0200 <dminuoso> We developers like to think we're better than our tools, and we already have an established theory before having any diagnostics input.
2024-05-30 13:24:12 +0200 <tomsmeding> that it's usually what you expected, so you look less?
2024-05-30 13:23:52 +0200 <dminuoso> tomsmeding: I think the problem with not looking too closely at what the computer tells you is usually confirmation bias.
2024-05-30 13:20:31 +0200destituion(~destituio@85.221.111.174)
2024-05-30 13:20:01 +0200destituion(~destituio@2a02:2121:2c1:d808:e5d8:f8e7:d625:4745) (Ping timeout: 268 seconds)
2024-05-30 13:14:36 +0200nain(~nain@37.19.205.146) (Quit: Konversation terminated!)
2024-05-30 13:14:12 +0200danse-nr3(~danse-nr3@151.47.143.144)
2024-05-30 13:13:47 +0200danse-nr3(~danse-nr3@151.47.143.144) (Remote host closed the connection)
2024-05-30 13:12:12 +0200 <danse-nr3> i think haskell's design is successful in providing a safe, expressive core one can work on for years. But of course we want to be machos and start our first app with monad transformers
2024-05-30 13:11:56 +0200 <lortabac> deciding where to focus on is a skill
2024-05-30 13:11:11 +0200 <lortabac> TBH we also have too many things to learn. It would be unrealistic to read everything in detail
2024-05-30 13:10:11 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 264 seconds)
2024-05-30 13:09:43 +0200xff0x(~xff0x@2405:6580:b080:900:94b5:b4e0:87f7:aaa5)
2024-05-30 13:09:07 +0200 <danse-nr3> too long, did not read. Wait this is too long! TLDR
2024-05-30 13:08:43 +0200 <danse-nr3> "make it a tweet"
2024-05-30 13:07:52 +0200 <danse-nr3> nah, there is just no place in a given concept of the industry to sit down one hour on a post and read it. We should not feel compelled to bow to that attitude
2024-05-30 13:07:48 +0200CiaoSen(~Jura@2a05:5800:2da:8d00:e6b9:7aff:fe80:3d03)
2024-05-30 13:07:00 +0200 <tomsmeding> (which says nothing about their haskell skill -- those skills are separate things)
2024-05-30 13:06:50 +0200 <tomsmeding> sometimes that's just people not being great writers, though
2024-05-30 13:06:22 +0200 <danse-nr3> actually i still have to consume an impedence coming from other technologies which makes long haskell posts (even just on haskell wiki!) unintelligible
2024-05-30 13:05:25 +0200 <tomsmeding> it's easy to conclude that these things are not useful, with what lots of software (also companies) are trying to tell you
2024-05-30 13:05:00 +0200 <tomsmeding> indeed
2024-05-30 13:04:36 +0200nain_nain
2024-05-30 13:04:36 +0200 <danse-nr3> and also, reading is still useful sometimes, who would think?
2024-05-30 13:04:27 +0200Maxdamantus(~Maxdamant@user/maxdamantus)
2024-05-30 13:03:51 +0200Maxdamantus(~Maxdamant@user/maxdamantus) (Ping timeout: 256 seconds)