01:01:02 <jeffro256[m]> NakedKing what do you mean by dangerous? Also what are you doing with the wallets; receiving, sending, etc?
06:49:33 <spirobel[m]> <wernervasquez[m]> "spirobel: Can you give a..." <- the issue for me is that I don't have an understanding of how the go scheduler works and there is an opportunity cost to find out about it. If I work with threads and processes there is a lot of intuitions to draw on. Coroutines are also well studied. Goroutines on the other hand are an idiosyncratic language feature that will most likely always be a niche thing, so it is not worth to
06:49:33 <spirobel[m]> get a deep understanding of them. But that is just my opinion. Maybe somebody has a deep belief that goroutines are great and is happy with that. I wouldnt argue against that. 🙂
06:50:16 <spirobel[m]> * not worth it to get
07:59:21 <cornfeedhobo> eh, it's just a hard pillar to base your life on. I think people had a similar stance about tuning the JVM, but that's proven to last and scale way beyond "a niche thing"
08:06:09 <cornfeedhobo> .. but i get the spirit of your comment. it's definitely domain specific and that's not for everyone
08:22:29 <mj-xmr[m]> C and C++ are also domain specific. We here just happen to be in the same domain (one of them).
08:22:55 <mj-xmr[m]> and GO sounds foreign from this perspective.
08:23:23 <mj-xmr[m]> Just pick the tool for the job.
12:53:25 <moneromooo> I think https://mitchellh.com/writing/contributing-to-complex-projects is a pretty good read for people who're considering contributing.
14:53:26 <reeemuru[m]> <moneromooo> "I think https://mitchellh.com/..." <- >Experiment and break things
14:53:26 <reeemuru[m]> I'm good with the breaking part. Also, a l lot of console.log()'ing or cout'ing when I don't see what is happening at specific line of code
14:53:35 <reeemuru[m]> * > Experiment and
14:53:40 <reeemuru[m]>  * > Experiment and break things
14:53:40 <reeemuru[m]> I'm good with the breaking part. Also, a l lot of console.log()'ing or cout'ing when I don't see what is happening at specific line of code
16:57:22 <Elijah[m]> <spirobel[m]> "> <@spirobel:matrix.org> the..." <- The article is bang on. It's the wrong kind of simple. It's like Lego with only bricks. Or minecraft with only cube blocks. An example for what simple means to me: want to build a lamp post? Here's a pipe. Go would say "okay so you buy or mine iron, then you make it round, make sure to specify the ending of the pipe, and now you can place it in the ground. Isn't go so simple? 😀." If I
16:57:22 <Elijah[m]> recall, you can make go use real threads instead of async threads. 
18:30:18 -xmr-pr- UkoeHB opened pull request #8220: multisig: add post-kex verification round
18:30:18 -xmr-pr- > https://github.com/monero-project/monero/pull/8220