Page 1 of 95 | Next »
[15:24:30] eam: it has a sensor and only turns on when there's particulate in the air. when there are wildfires this means I open a door and then bam, I hear it turn on a minute or two later
[17:12:08] eam: I'd rather use minitest or something that looks like all the other testing frameworks in all the other languages I use
[19:40:06] eam: ivanskie: I always shell out to ssh, there's unfortunately no other way to do fully featured ssh sessions
[17:47:27] eam: the specifics ... I really haven't had enough coffee to debug terminal problems this early in the morning :)
[18:21:37] eam: ivanskie: sorry, working on the fires they pay me to put out -- looks like you got it though!
[01:14:44] eam: allow me to share my cautionary tale with you all, as some of you already know I've been lying on my back for the last 6 weeks
[03:07:58] eam: reading back to the top, "salty" seems like a pretty fair characterization to me -- that it omits an attempt at deeper understanding aside
[03:09:17] eam: I saw a great comment somewhere, I forget where, but to paraphrase it was "most liberal gains in the last half century have been through the courts rather than legislation"
[03:09:43] eam: "both the right and the left have figured this out and that's why these SCOTUS appointments are so bitter"
[03:11:55] eam: totally unrelated, but if you could move to any country in the world where would you go?
[05:16:36] eam: you want to run the sinatra server on a command line and have it run in the background?
[05:20:08] eam: so it sounds like this is really a question about the interaction between the shell and a program being run
[05:20:40] eam: if that's the case, the answer is that you absolutely must fork and create two processes -- but the first one will exit
[05:21:01] eam: and it *is* possible to communicate between forked processes, but we would need more specifics
[22:50:02] eam: is there a way to generate a new Gemfile.lock without actually installing all the damn gems with bundle install?
[21:59:01] eam: elomatreb: DGRAM/STREAM distinguishes between tcp/udp for an IP socket, but they apply to unix sockets too
[17:46:06] eam: desnudopenguino: the errors I see are: "openssl_missing.h:196:22: error: static declaration of 'EVP_PKEY_get0_RSA' follows non-static declaration"
[17:48:17] eam: it's in this one https://gist.github.com/desnudopenguino/c050bec601d95ee7075e140ec973d278#file-errors3-log
[17:52:11] eam: in any event it looks like you've maybe mixed up two different openssl dev environments
[00:23:24] eam: cthulchu: you should use File.join because it will work on platforms where / isn't the directory separator
[00:35:58] eam: in fact, I'm not sure ruby has access to the set of non-relative filesystem access calls on linux
[00:37:56] eam: like, at least linux implements non relative calls but OSX can't do it unless you're going to do something like write your own kernel module
[01:35:37] eam: when I turn it on full it sounds like a jet engine and it lifts my hair on end and creates a huge upward draft
[01:36:00] eam: I used to use it to torch weeds in my side yard but now I use it to instantly start my charcoal bbq
[01:38:44] eam: here's a dude using one for weed control https://www.youtube.com/watch?v=125L5E3N7wU#t=1m
[20:21:30] eam: just saying the defaults are silly and overly pedantic with bad opinions. of course they can be changed
[20:23:02] eam: if they were less opinionated we might be able to establish a widely agreed upon common subset!
[20:25:23] eam: the defaults are poor, are too opinionated. "too" opinionated is not the same as "not having opinions at all"
[20:27:00] eam: it is possible for something to be "less opinionated" without having no opinion whatsoever
[20:29:03] eam: 20:23 < eam> if they were less opinionated we might be able to establish a widely agreed upon common subset!
[20:43:25] eam: severity 5 is stuff that is almost certainly an error, or will be actively dangerous
[20:44:51] eam: it's pretty important, because some things are almost certainly errors that a linter should catch (eg, assignment in what appears to be a test)
[20:45:46] eam: then there are increasingly pedantic and opinionated sets of criticisms which you can use if you like
[20:47:24] eam: rubocop, by default, makes it hard to distinguish between important syntax problems and silly ones
[20:50:17] eam: the ranking of severity is also useful, I think, because it indicates to a newbie whether the style is a pure style issue or a possible serious mistake
[15:09:19] eam: why don't we ever run production on developer machines, the code always works there :D
[23:08:09] eam: a local variable is just a bare word "x". Maybe you'd create one inside a method, and it exists for the duration of the method call
[23:08:44] eam: an instance variable is prefixed with @, like @x, and it exists for the duration of the object instance
[23:09:09] eam: a class variable is prefixed with @@ and it exists for the duration of the class itself (so, essentially globally)
[01:47:21] eam: maybe in my copious free time I can send over a version that opens the socket nonblocking and selects
[16:55:02] eam: derp10327: if you want to take the string "seconds" and refer to the variable named seconds you would use eval or binding.local_variable_get
[22:40:14] eam: and yes, the first time a variable is assigned it's instantiated and subsequent assignments reassign it
[23:02:33] eam: do you always want to remove the first duplicate? I think I'd have to write a method
[23:18:53] eam: I think I'd iterate the first array and for each item iterate the second array, removing from both on match
[23:31:55] eam: gotta iron out the semantics -- is it only ever removing the first instance and is the second array unique?
[21:49:39] eam: jordanm: garyserj: that is not true - text/binary influences the character encoding of strings read from a file
[21:50:34] eam: this can be enormously important -- I once had a (unix) ruby script which went from hours of runtime to seconds after changing to binary
[23:07:30] eam: garyserj: the difference is that a string will have indices access of O(n) instead of O(1) if the string uses a variable width encoding like UTF-8
[23:10:29] eam: with a fixed character size and O(1) indexing, the above will complete almost instantly
[23:10:47] eam: but if you do this when the string has a variable width encoding it will take a reeeeallly long time