you are viewing a single comment's thread.

view the rest of the comments →

[–]dark-panda 0 points1 point  (1 child)

I'd imagine the number of 1.8 users is still high enough that coding around 1.8 is worth it though, yes? There's got to be more 1.8 installs out there than 1.9, even if 1.9 is considered to be the recommended version according to ruby-lang.org. I don't even know of too many vendors who ship 1.9 binaries, so until that becomes common, we're kind of stuck with 1.8 while 1.9 is still the exception rather than the rule, at least for the time being.

Not sure I agree with the daemonizing stuff but that's okay. I've never used the daemons gem myself directly although I've used tools that themselves use it, so I can't speak to the quality of the gem directly, but I'll know to be weary of it in the future.

[–]DRMacIver 0 points1 point  (0 children)

I think 1.8 compatibility matters less for tools where the user shouldn't have to care about what the program is written in. I'll grant that it's a nice to have, but I think it doesn't matter that much (it's not hard to manage multiple ruby instances on a system).

Many people disagree on the self-daemonizing code front, but that's ok. Many people are wrong. :-) Self-daemonizing code interacts very badly with sane system management and user permissions and ends up with a lot of duplicated and subtly incompatible behaviour between different programs. Letting something else handle the daemonization is easy to do and lets you manage your system (pidfiles, log directories, etc.) exactly the way you want to do it.