Activity Graph

Page 1 of 1


[15:17:20] ddfreyne: has joined #ruby


[16:15:36] ddfreyne: Ping timeout: 264 seconds


[19:25:45] ddfreyne: *.net *.split
[19:31:34] ddfreyne: has joined #ruby


[10:03:49] ddfreyne: *.net *.split
[10:03:57] ddfreyne: has joined #ruby


[23:38:42] ddfreyne: *.net *.split
[23:47:58] ddfreyne: has joined #ruby


[09:22:23] ddfreyne: has joined #ruby


[20:57:14] ddfreyne: sediment: Looking at the code for that gem, it seems like that only works after a `include TruncateHtmlHelper`
[20:57:37] ddfreyne: (I assume that Rails does the `include` automatically)
[20:58:05] ddfreyne: sediment: Replace some_html with the string that you want to truncate
[21:03:53] ddfreyne: That might be a lie :o
[21:06:51] ddfreyne: I???d suggest finding a different gem!


[22:53:35] ddfreyne: *.net *.split
[22:58:02] ddfreyne: has joined #ruby


[19:38:34] ddfreyne: *.net *.split
[19:41:05] ddfreyne: has joined #ruby
[21:50:17] ddfreyne: *.net *.split
[21:51:39] ddfreyne: has joined #ruby


[17:01:52] ddfreyne: has joined #ruby


[15:49:25] ddfreyne: has joined #ruby
[15:49:34] ddfreyne: Client Quit


[07:06:49] ddfreyne: Ping timeout: 255 seconds


[06:01:05] ddfreyne: Ping timeout: 252 seconds
[06:14:42] ddfreyne: has joined #ruby


[16:56:15] ddfreyne: (I do not have a highlight for nanoc)
[16:57:11] ddfreyne: What makes it terrible?
[16:58:46] ddfreyne: Yeah, I can understand that. nanoc 4 addresses some of those concerns (it gets rid of the confusing identifiers).
[16:59:11] ddfreyne: As for speed??? I???ve managed to generate thousands of pages in a minute. It depends on the filters you use, most of the time.
[17:01:48] ddfreyne: raz: disclaimer: I am the author of nanoc. I'm always interested in feedback though :)
[17:03:08] ddfreyne: A goal I have for nanoc 4 is for it to be not memory-based, so it doesn't have to deal with garbage collection issues. It's the main bottleneck.
[17:04:08] ddfreyne: It's surprisingly difficult to build a static site generator that has the flexibility of nanoc while also being fast.
[17:04:31] ddfreyne: (The nanoc 3.x design didn't give me much space to fix things either. But then again, that architecture lasted for 6 years.)
[17:04:40] ddfreyne: raz: What would you remove?
[17:07:29] ddfreyne: raz: FYI, in case you're interested in seeing what the recent efforts are about: http://v4.nanoc.ws/doc/nanoc-4-upgrade-guide/
[17:08:23] ddfreyne: raz: Keeping track of dependencies is useful for speeding up compiles (avoid recompiling when possible). It's hard to get right, but I find it really useful.
[17:08:45] ddfreyne: raz: What would you rather have than a rules file?
[17:09:27] ddfreyne: raz: Where would you specify how certain pages or assets are processed?
[17:11:01] ddfreyne: raz: How would you specify which markdown processor to use? Whether or not to minify? Colorize syntax? Run a typography-improving script? ...
[17:12:14] ddfreyne: raz: Mind you, nanoc is designed to be flexible and not make assumptions about what you want to do with the input files. I try to keep it as opinion-free as possible
[17:14:12] ddfreyne: raz: I like it when software gives you possibilities, and you fill in the blanks. Having to resort to JS for colorizing syntax and improving typography can be a good thing, but I don't want to be limited to that.
[17:18:43] ddfreyne: raz: For simple sites, I generally don't even recommend using nanoc myself--it's designed to be flexible, and it is overkill for simple sites.
[17:19:43] ddfreyne: Even though it???s written in JavaScript? ;)
[17:21:16] ddfreyne: raz: If nanoc is that slow, I'd look at the filters you used (that's where the vast majority of the slowness lies)
[17:24:51] ddfreyne: towski_: Please don???t use ???gay??? as an insult.


[16:20:06] ddfreyne: *.net *.split
[16:20:28] ddfreyne: has joined #ruby


[18:30:52] ddfreyne: *.net *.split
[19:52:56] ddfreyne: has joined #ruby


[16:50:43] ddfreyne: *.net *.split
[16:51:08] ddfreyne: has joined #ruby


[08:05:27] ddfreyne: I wouldn???t mind a hackable Ruby IRC client. I don???t know of good IRC or terminal UI libraries ;(
[08:06:06] ddfreyne: That???s a IRC bot framework though


[08:13:16] ddfreyne: yorickpeterse: There's no point in adding gem checksums to the ruby-lint gem repository if you???re not signing your Git commits
[08:13:44] ddfreyne: yorickpeterse: Anyone could commit in your name.


[21:54:02] ddfreyne: Ping timeout: 272 seconds
[22:02:47] ddfreyne: has joined #ruby


[08:19:38] ddfreyne: yorickpeterse: SoundCloud > your company
[08:19:55] ddfreyne: abyss: Upgrade!!!


[10:19:30] ddfreyne: yorickpeterse: Are you so fat that you need two Aeron chairs?


[19:21:56] ddfreyne: Ping timeout: 272 seconds
[19:23:36] ddfreyne: has joined #ruby


[21:25:03] ddfreyne: havenwood: I was a big minitest fan for a long time, but I found that RSpec, when used properly, can be really really awesome.
[21:25:17] ddfreyne: (One of my colleagues showed me how to properly use it. It's awesome.)
[21:25:30] ddfreyne: So now for nanoc 4, I'm writing all new spec in RSpec.
[21:26:58] ddfreyne: adaedra: Yes.
[21:27:17] ddfreyne: bricker: It doesn't
[21:27:23] ddfreyne: havenwood: I find that it is worth it.
[21:32:19] ddfreyne: havenwood: Whatever works for you!
[21:33:07] ddfreyne: I found RSpec's contexts quite useful for catching all cases, and shared_examples to verify that two objects that are supposed to behave the same, actually *do* behave the same.
[21:33:21] ddfreyne: I haven't found a good way to do that in minitest as nicely yet.
[21:35:56] ddfreyne: adaedra: Yup, true.
[21:36:15] ddfreyne: Sou|cutter: matchers (and custom ones) are really really nice.
[21:36:37] ddfreyne: I wrote one myself: https://github.com/nanoc/nanoc/blob/master/spec/spec_helper.rb#L26-L49
[21:37:17] ddfreyne: Why don't you use emacs?
[21:37:22] ddfreyne: michaeldeol: #ruby and #ruby-lang were merged


[17:05:33] ddfreyne: Crystal is pretty nice. I've written some stuff in it, and I plan to use it for more things.


[20:09:59] ddfreyne: Rubocop is <3
[20:10:47] ddfreyne: I generally don't use Rubocop as-is (I always have a few tweaks), but it's really good to have a consistent code style.
[20:11:51] ddfreyne: jhass: http://en.wikipedia.org/wiki/Jinx_(children%27s_game)


[18:10:45] ddfreyne: too late now!
[18:14:11] ddfreyne: hal_9000_: #ruby-lang got merged into #ruby.


[09:42:45] ddfreyne: I'm interested in trying out whether using a Some(x)/None style in Ruby works well. I suppose a None could implement #nil? and #! and it'd behave pretty normally.
[09:45:18] ddfreyne: Mon_Ouie: Yeah, I guess.
[11:43:10] ddfreyne: Nilium: Rusalka VM looks interesting. I've implemented a register-based VM myself. Fun!
[11:46:26] ddfreyne: Nilium: https://github.com/ddfreyne/rcpu
[11:46:37] ddfreyne: Nilium: Hm, not sure... I haven't written a stack one.
[11:47:05] ddfreyne: Prettier README: http://ddfreyne.github.io/rcpu/
[11:47:33] ddfreyne: Nilium: Ah, I didn't get to that point yet.
[11:47:50] ddfreyne: Nilium: But mine has video!
[11:48:30] ddfreyne: Nilium: Couldn't you change the stack pointer and register values instead, rather than copying the entire stack?
[11:48:36] ddfreyne: Nilium: Yeah, I like AsciiDoc.
[11:49:16] ddfreyne: I tried using it for nanoc.ws documentation, but I found Markdown (with bits of HTML) easier.
[11:50:58] ddfreyne: I wanted to implement process management in my VM (or rather, in a kernel written on top of the VM)
[11:51:16] ddfreyne: I wanted something more high-level to work with than assembly, so I started writing my own language that compiles to that VM's assembly
[11:51:40] ddfreyne: It ha been a while since I worked on that, because I also have other stuff to work on. But I'll probably come back to it at some point!
[11:52:19] ddfreyne: Ah, mine's absolutely just for educational purposes.
[11:52:38] ddfreyne: Language: https://github.com/ddfreyne/rcpu-lang -- lisp syntax, but it's not lisp.
[11:53:34] ddfreyne: Biggest assembly program I've ever written: https://github.com/ddfreyne/rcpu/blob/master/samples/video.rcs


[18:58:55] ddfreyne: bootstrappm: Haiku? It's a little hard to use though :)
[19:43:32] ddfreyne: What's the #ruby-lang vs #ruby difference about again, and how come they get unified only now?
[19:43:45] ddfreyne: I've asked this before (years ago) and forgot.


[23:10:52] ddfreyne: Can't have everything, shevy!
[23:13:24] ddfreyne: Dysfunctional programming is my kind of style.


[19:16:33] ddfreyne: For doing stuff with CSVs, I found this tool to be super useful: https://github.com/BurntSushi/xsv
[19:16:40] ddfreyne: And it's fast.


[08:02:02] ddfreyne: Oh yikes. I thought we got rid of 'English' by now.
[08:02:20] ddfreyne: I'd like that to be part of core.
[08:26:49] ddfreyne: ACTION has joins/leaves/quits turned off. Makes IRC such a nicer experience.
[08:28:24] ddfreyne: I switched from irssi to weechat around two weeks ago. I set it up to only show joins/leaves/parts for people that have chatted recently.
[09:53:02] ddfreyne: It???s all about Rust and Crystal and Nim now
[18:26:47] ddfreyne: TheNet: guard. If you want to have a more low-level lib, try guard/listen.


[09:23:40] ddfreyne: Hm, #grep_v is an odd name. I get that it comes from `grep -v`, but still.
[09:25:01] ddfreyne: I didn't know about #grep. My ItemCollection#find_all(pattern) should probably be #grep rather than #find_all.
[09:35:39] ddfreyne: #find_matching?
[09:36:01] ddfreyne: Without the question mark, obviously. Although I suppose that is too close to #find, which returns only a single result.
[09:36:51] ddfreyne: #select_matching, maybe. I suppose #matches is too regex-y.


[14:19:42] ddfreyne: pagios: Have you looked at Shoes?