#ruby - 09 May 2019
« Back 1 day Forward 1 day »
[00:36:47] comet23: i want it to go back to the first index and then until x number of desired iterations
[00:37:20] comet23: like [1,2,3] iterate 5 times and you start at 0 and you would get the 2nd index with the value of 3
[13:30:08] _sfiguser: hello all guys i wanted to learn some new programming language and was considering ruby... is it still viable in 2019? i wanted to do some network programming...
[14:48:27] t3hyoshi: I don't think Rails is good to learn as a newcomer to Ruby. If you want to make simple sites, start with Sinatra before jumping into Rails.
[14:51:40] adam12: To be fair, there is a bunch of work going on to improve Ruby for networking. The async-* packages and lightweight fibers being one.
[14:56:24] Bish: that's the best thing about ruby, it's super high, and crafting "strings"/buffers with it is great
[15:05:56] pwillard: _sfiguser: Take a look at AsciiDoctor-pdf for an example of really cool "current" stuff being done with ruby. I use it to write all my documentation now.
[19:01:51] anoob: Is it possible to unlock a sidekiq unique job only if it goes to the "dead queue"? My jobs are unlocked when they fail and I need them to retry ...
[23:15:35] symm-: hi, can I have nested modules and within them module functions that I can call like `Foo.Bar.blah()`?
[23:16:08] symm-: I found that it's possible to do `Foo::Bar.blah()` but the cognitive dissonance is killing me
[23:17:47] phaul: you could do :: on the method too, so Foo::Bar::blah works, but Dont. This is the acceted way.
[23:18:38] phaul: modules and methods are different, it's fine to separate them differently - as far as dissonance is concerned
[23:20:29] havenwood: symm-: The Ruby convention is :: separator between modules and classes and . for method calls.
[23:21:03] havenwood: symm-: Here's an example of the interface you want: https://gist.github.com/havenwood/9ae14630c79031ed6f4c44d14c9a2578
[23:21:04] phaul: calling a method on a receiver, and resolving a constant in module nesting are fundamentally different things
[23:39:37] symm-: just to confirm: is saying `def self.method` equivalent to `def ModuleName.method` in a module?
[23:43:27] phaul: ah. it's true what I said but didn't really make sense, so the short answer is yes you were right with that symm-