[00:26] <snap-l> http://arstechnica.com/information-technology/2013/05/fios-customer-discovers-the-limits-of-unlimited-data-77-tb-in-month/
[00:26] <snap-l> What the fuck
[00:26] <rick_h_> yea, <3
[00:26] <rick_h_> some good stuff on ars today
[00:26] <rick_h_> I was lol'ing at the new MS mice
[00:26] <snap-l> Dude was running a fucking datacenter out of his house
[00:27] <rick_h_> just a rack, a DC has many :)
[00:27] <snap-l> Um, seriously? :)
[00:27] <snap-l> I think JoDee would either marry me all over again or kill me if I had that setup
[00:27] <snap-l> not sure which
[04:52] <greg-g> g'morning in AMS (6:52am)
[04:52] <greg-g> been up since like 4:30ish
[10:47] <rick_h_> greg-g: morning
[10:48] <greg-g> it's lunch time!
[12:34] <rick_h_> well, first time using more then 8G of ram today woot
[12:35] <brousch> whoa
[12:36] <rick_h_> 3lxc running, 4G ram windows VM, chrome tabs/windows galore, wheee
[12:36] <rick_h_> and don't even notice it woot
[12:37] <brousch> SSD FTW
[12:37] <rick_h_> the lxc/virtualbox vms are on a normal HD
[12:38] <rick_h_> thinking it's more the 6cores (12 with hyperthread) and 32GB of ram :)
[12:40] <brousch> geez
[12:41] <brousch> That is 2x the ram in my entire "data center"
[12:41] <rick_h_> the virtualbox ram slider jumps around in big chunks :)
[13:09] <snap-l> Good morning
[13:10] <rick_h_> morning
[13:10] <rick_h_> how goes the raid rebuild?
[13:10] <snap-l> Finished up overnight, but am running into partition misalignment issues with the new drive.
[13:11] <snap-l> It's a Seagate drive
[13:11] <snap-l> Seems to be performant, so not sure if I should be worried or not
[13:12] <snap-l> currently in the "not worrying" category
[13:12] <snap-l> Also, it's 68F in the den, and I'm happy
[13:12] <rick_h_> well if it's rebuild, get a second drive of the new type to try tomatch them up. Always best to have matched drives for raid
[13:14] <brousch> I thought it was best to have mismatched drives so they don't fail at the same time
[13:14] <greg-g> that's the theory
[13:14] <greg-g> it's what I did for my btrfs raid setup
[13:15] <rick_h_> so if they're not matched they'll have diff performance characteristics, different layouts, diff firmware, etc.
[13:15] <rick_h_> it'll not let the raid work at its best as it's fighting the diff drives trying to write the data
[13:15] <rick_h_> is my understanding.
[13:16] <rick_h_> just because we both buy two trucks on the same day doesn't mean they'll fail on the same day. It's mechanical and just don't see that
[13:16] <brousch> So you're giving up some performance for reliability
[13:16] <brousch> One word: Deskstar
[13:16] <rick_h_> I'd argue that reliability is a false assumption there
[13:17] <snap-l> Well, it's also a work machine
[13:17] <rick_h_> hah, well don't buy crap cheap drives :P
[13:17] <brousch> they were not cheap at the time
[13:18] <snap-l> I think the real reason the drive failed was the drives were jammed together under each other, so one drive was busily cooking the other
[13:18] <rick_h_> snap-l: what's the warranty on them? I mean it's been a few years now?
[13:18] <rick_h_> drives do have life expectancies
[13:19] <snap-l> Not sure
[13:20] <rick_h_> how do people deal with windows...I mean really?! /me wants apt-get install ie10
[13:20] <snap-l> rick_h_: I think they just don't know any better
[13:21] <snap-l> "Linux is so complicated, just give me a drive letter that I can memorize"
[13:21] <rick_h_> "pick your version" just install the right one dammit. I don't "apt-get install python-and64"
[13:21] <snap-l> Even though all of the drive letters can quickly change
[13:22] <jrwren> where is AMS?
[13:24] <brousch> rick_h_: I have a script to bootstrap distutils/pip/virtualenv for python3.2 if you need it
[13:24] <greg-g> rick_h_: re fighting the raid controller: btrfs deals with this just fine :)
[13:24] <greg-g> I mean, it explicitly doesn't care and "just does the right thing"
[13:25] <rick_h_> jrwren: amsterdam
[13:26] <greg-g> its the airport code
[13:48] <jrwren> oh!
[13:49] <jrwren> i wish I was there with greg-g getting coffee
[13:50] <brousch> Yeah. "Coffee"
[14:40]  * greg-g takes a big long dr^C^C sip of his coffee
[14:48] <rick_h_> al...most...to...10GB of ram used. Need more things to run!
[14:53] <brousch> Want to process some unflattened semi-corrupt 36"x48" vector PDFs for me?
[14:53] <rick_h_> onlyif the tool to do it is multi-core enabled
[14:54] <rick_h_> I want to light up some of these things
[14:55] <brousch> You could run multiple instances
[14:55] <brousch> I never did get around to making it a multiprocess queue
[15:25] <nullspace> concurrency is powerful but tricky to write for
[15:25] <jrwren> i disagree.
[15:26] <nullspace> which part, powerfull or tricky?
[15:26] <brousch> Yeah, and the project has died because we bought a new plotter that doesn't choke on as many iffy PDFs
[15:26] <jrwren> tricky
[15:27] <nullspace> tricky meaning you really need to think about what your trying to accomplish and ensure threads don't collied or corrupt data
[15:28] <jrwren> you've made so many assumptions given taht statement that we are no longer talking about only concurrency.
[15:28] <jrwren> i agree, threads and data sharing is tricky.
[15:29] <nullspace> then what was the part you we're disagreeing with?
[15:29] <jrwren> that concurrency is tricky to write for.
[15:29] <jrwren> its not.
[15:30] <nullspace> writing isn't but programming is more than just writing code
[15:31] <jrwren> indeed.
[15:33] <nullspace> I recently wrote my first big concurrent feature in java, was dealing with get and sending  data to a flakey SOAP setup
[15:34] <jrwren> ugh. flakey soap is pretty bad.
[15:36] <nullspace> that service is the biggest pain in my ass, hopefully by september we be rid of it
[15:38] <nullspace> it's like completely ignored any standards and hand wrote the methods to implement it
[15:39] <jrwren> is it by a vendor?
[15:42] <nullspace> I'm not entirely sure what it is, our sister company's IT department brought it into existance
[15:44] <nullspace> from what I heard it was a learning experience for most staff members on databases as well as SOAP, XML and web services in general
[15:44] <brousch> Your WTF of the day: "I'm trying to package an (Kivy) app for android that will be using pymssql to communicate with sql server"
[15:44] <nullspace> this sounds like a horrible idea
[15:46] <brousch> I put on my jrwren mask and told him he's doing it wrong
[15:46] <nullspace> unless it's a database management tool
[15:46] <jrwren> lol
[15:47] <brousch> "Our system though is running directly within our local network and just happens to be the android platform. They're really running just the same way a normally networed computer terminal would. Just think of it as an integrated touchscreen device."
[15:48] <nullspace> not sure why someone would want to manage a database on a mobile device
[15:48] <jrwren> brousch: doesn't matter.
[15:49] <jrwren> that database should never be an integation point.
[15:49] <nullspace> you'd think a web app would be easier and less stupid
[15:49] <jrwren> its the wrong design for a desktop app too.
[15:49] <brousch> jrwren: I agree, but I've done my due-diligence education
[15:49] <jrwren> http://haacked.com/archive/2007/04/23/avoid-using-a-database-as-an-api-integration-point.aspx
[15:49] <rick_h_> apis ftw
[15:51] <brousch> I can't imagine how fragile this app is going to be with all the weirdness he's putting together
[15:51] <brousch> And now it's directly accessing your database
[15:51] <jrwren> not my database. it isn't allowed :)
[15:55] <nullspace> brousch: is it actually an intgration point? are they pulling/psuhing data to the DB via this app or are they using it to build a database, both are horrible ideas I'm just wondering what kinda stupid they are
[15:56] <jrwren> it sounds like a 2tier 80s/90s app client server arch where server is dbserver.
[15:56] <jrwren> its hard for me to think of a good reason to build apps like that these days
[15:57] <nullspace> http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/100000/70000/6000/300/176362/176362.strip.sunday.gif
[15:58] <brousch> nullspace: I don't know
[15:58] <nullspace> it might be for the best
[15:59] <brousch> Right
[15:59] <nullspace> otherwise you might have the uncontrolable urge to remove them from the gene pool
[16:12] <jrwren> starting new little projects is fun.
[16:39] <snap-l> http://www.thinkgeek.com/product/12d9/
[16:39] <snap-l> What the fuch
[16:41] <snap-l> rick_h_: Good day?
[16:42] <rick_h_> snap-l: heh...let's just say I've got firm opinions on the mocha JS testing tool
[16:42] <rick_h_> and dealing with other people's CI and such
[16:49] <snap-l> rick_h_: Yeah, I can see that. :)
[19:14] <jjesse> some dude at the starbucks i'm working out of today just fired up his "Windows Vista Premium" laptop
[19:14] <jjesse> sad face
[19:17] <jjesse> that dude looks grumpy, i bet its because of his laptop
[19:20] <snap-l> http://www.musicmanumit.com/2013/05/jazzcast-summer-series-episode-1-with.html
[19:23] <jcastro> hey jrwren
[19:23] <jcastro> when are you off today, 5ish?
[20:09] <jrwren> jcastro: i went home already.
[20:09] <jrwren> jcastro: you want to come over?
[20:17] <jcastro> mebbe
[20:17] <jcastro> maybe we should eat in AA tonite
[20:18] <jrwren> lol.
[20:18] <jrwren> for sure.
[23:06] <jcastro> greg-g: hippie ping
[23:06] <jcastro> what's the tldr on this monsanto thing
[23:06] <jcastro> the march website sucks at explaining the why
[23:07] <jcastro> other than "global xbox sized food grower"