#ruby - 30 November 2018
« Back 1 day Forward 1 day »
[00:22:57] baweaver: There's a difference between learning something useful and just developing bad habits.
[00:26:59] cthu|: Ha! works! It's the first and the last time I'm overloading a native method in Ruby. I wonder if I could use something else, instead of $stdout. Could I?
[00:27:09] coltkirk: ive been prattling with emacs/elisp for a few years, thinking about taking the next step into the ruby-verse
[00:28:49] cthu|: right, but I thought maybe there was a child of stdout that is closer to our beloved puts
[00:30:06] cthu|: although, it may be the other way around. Maybe put is somewhere above and then stdout just uses it to create puts
[10:50:07] xco: hi everyone, need some second pair of eyes, i rewrote this method can someone please tell me if they are the same? i think they are https://gist.github.com/xcobar/e485b5e7e591959e993aedae35423991
[12:07:35] xco: hi everyone, need some second pair of eyes, i rewrote this method can someone please tell me if they are the same? i think they are https://gist.github.com/xcobar/e485b5e7e591959e993aedae35423991
[14:55:07] crankharder: I'm trying to improve a gem's test suite (that uses appraisal) and it's spitting out a huge amount of these warnings: "warning: method redefined; discarding old request" - Does anyone know how to reproduce a warning like that? Can't say I've seen it much. Seems like it's a warning coming out of ruby-core, but maybe not?
[15:56:06] havenwood: pwned: Ruby Threads are backed by pthreads but there's a global vm lock (GVL) that sometimes prevents parallel.
[15:57:30] havenwood: pwned: Here's a three-part article on how the GVL (used to be called GIL) works: https://www.jstorimer.com/blogs/workingwithcode/8085491-nobody-understands-the-gil
[15:57:50] havenwood: For fun, you can unlock the GVL with Fiddle: https://gist.github.com/tenderlove/5733632
[19:59:51] havenwood: @baweaver's RubyConf talk was just posted: https://www.youtube.com/watch?v=x3b9KlzjJNM