ELLIOTTCABLE changed the topic of #elliottcable to: #ELLIOTTCABLE — “do something cool, shove it into throats, everyone thinks it's crap, then it's all amazing.” “everything else is just details.”
<jvulc> I guess.
<jvulc> Entire event was "meh" outside of free Mavericks.
<purr> <alexgordon> micahjohnston: eboyjr: 'it turns out that' clang doesn't support grapefruits
<whitequark> wat
<accumulator> jvulc: yeah
<accumulator> jvulc: best thing to come out of it will be 1. the siracusa, 2. some posts by mikeash
<accumulator> because OMG NEW OS X
<jvulc> I don't even know what the fuck Mavericks is other than the billion Top Gun references and the fact it's newer. Haven't followed it.
<jvulc> Hold on while I jizz in a cup over OpenGL 4.0.
<accumulator> jvulc: it's really good actually
<jvulc> I downloaded it and will either install it tonight or tomorrow.
<accumulator> they've done a lot of work on power usage minimisation
<accumulator> and other kernel things
<jvulc> It's free, so props to Apple for doing Service Pack pricing.
<accumulator> compressed memory!
<accumulator> jvulc: heh when steve turned the company around he introduced a kind of "CHARGE FOR EVERYTHING" mentality, which was good because it worked...
<whitequark> compressed memory?
<accumulator> but what makes sense when you're a failing company doesn't make sense when you're one of the biggest companies by market cap
<accumulator> whitequark: what it says on the tin
<jvulc> This is basically a better, meaner, Forstall-free Mac OS .
<whitequark> accumulator: so you mean basically what linux had in... 2005? *trollface*
<jvulc> They basically throw all the underlying stuff that Mavericks does on one slide at their keynote ... basically they don't know what that shit does either.
<accumulator> whitequark: pfft, tell me when linux gets coreaudio ;)
accumulator is now known as alexgordon
<whitequark> alexgordon: dunno, what's good about coreaudio?
<alexgordon> 1. there's only 1 core audio
<alexgordon> 2. core audio works with every piece of pro equipment ever due to apple's monopoly on pro audio
<alexgordon> 3. core audio has low latency
<whitequark> mmm
<alexgordon> don't get me wrong, there's some serious technical debt in it :P
* jvulc forgot what Linux audio is called ... fuck, I hate when I forget names of shit.
<whitequark> no comment on 2), but a guy I know uses OSS4 (I think) and an rt kernel for audio
<alexgordon> working with core audio is a bitch
<whitequark> so the latency part is not exactly applicable
<whitequark> drivers, I dunno. could be good could be bad.
<jvulc> RetroArch and emulator developers rave about audio latency vs. Android.
<whitequark> oh, Android is an entirely different thing
<jvulc> It's true. Core Audio's got their shit together on iOS.
<jvulc> Android is fucking hell crackers.
<alexgordon> linux's problem is http://xkcd.com/927/
<whitequark> it has a mixing layer in software above kernel
<whitequark> that's pretty fucking bad
<whitequark> alexgordon: it's a problem of software in general
<alexgordon> particularly linux audio though
<whitequark> I mean, fucking look at Microsoft
<jvulc> If Caustic even remotely reports audio latency correctly, best case scenario, Android gets about 40ms latency.
<whitequark> they *do* have a near-monopoly, or at least had
<whitequark> and they have the same shit with standards.
<alexgordon> because audio isn't particularly glamorous per se
<whitequark> (if deliberate!)
<whitequark> jvulc: that sounds about true
<alexgordon> it's also hard as hell
<alexgordon> so the only reason you're going to work on it is if you get your name at the top of the credits
<alexgordon> i.e. you make your own incompatible audio layer
<whitequark> something something pulseaudio
<whitequark> aka the most moronic thing after (or is it before?) systemd
<alexgordon> (or you get paid to do it)
<whitequark> alexgordon: well, you get a lot of hard parts for free in linux
<alexgordon> also servers don't need audio usually
<alexgordon> it's more a desktop/workstation thing
<whitequark> linux is by far not only servers
<alexgordon> and all the pro people use OS X (or perhaps windows)
<whitequark> you forget about tons of industrial control applications
<alexgordon> so nobody is going to fund work on linux audio
<whitequark> and that's where you really need latency
<whitequark> including, surprise, actual audio equipment, what do you think it fucking uses
<whitequark> but I sure agree that apple's monopoly and consistent funding gives it quite a bit of advantage.
<jvulc> Pulseaudio ... that's it! That's what I couldn't remember the name too. Having a series of "duh" moments here.
<whitequark> jvulc: it's poettering.
<whitequark> poettering, adj.: bloat, bugs, extreme case of NIH.
<alexgordon> whitequark: there's also a chicken/egg because there's no drivers for linux audio eqipment which means nobody uses linux for audio, which means it doesn't get improved
<whitequark> alexgordon: that's not true
<jvulc> Apple's captured the niche market of people wanting $3000 machined aluminum trashcans and there's no escape.
<alexgordon> jvulc: 7 teraflop trashcans
<alexgordon> whitequark: for example RME makes the gold standard of audio interfaces. do they support linux? nope
<whitequark> hell, there's even a freebsd one: http://www.rme-audio.de/forum/viewforum.php?id=10
<alexgordon> lol it has old in the url
<purr> lol
<alexgordon> and the second one is not official
<alexgordon> which kind of defeats the purpose of spending thousands of dollars on RME's magical drivers
<alexgordon> (plus some magic equipment that works with it ;)
<alexgordon> anyway, I forget why we were even talking about this
<whitequark> I think you spend thousands of dollars on RME's magical FPGA firmware
<whitequark> but whatever
<joelteon> oh my god
<joelteon> you pronounce "gyarados" "garados"
<alexgordon> whitequark: kind of a mix :P
<alexgordon> joelteon: lol
<purr> lol
<joelteon> i thought it was gyro-dos or something
<joelteon> what the fuck is the Y for
<alexgordon> yeah that's how I want to say it
<alexgordon> but
<alexgordon> I haven't felt the need to pronounce "gyarados" for many years
cloudhead has quit [Ping timeout: 272 seconds]
<jvulc> How'd we get on Pokemon?
<jvulc> Also, X and Y are awesome games.
<joelteon> oh somebody said gyarados in a video i was watching on youtube
<joelteon> and I was like "hey, that can't be right"
<joelteon> but it was
alexgordon has quit [Quit: Computer has gone to sleep.]
<purr> <gqbrielle> damn.
eligrey has quit [Quit: Leaving]
<whitequark> devyn: btw
<whitequark> recall the simulator discussion?
<whitequark> I just remembered how I had a carpet with city infrastructure drawn on it
<whitequark> and my brain wanted more, and more flexibility of it
<whitequark> stupid brain. it knows it doesn't have the capacity to perform city planning on any kind of major scale neither the willpower to actually learn the underlying theory, yet it desires.
<cuttle> hi
<purr> cuttle: hi!
<whitequark> cuttle: hi
<purr> lol
<whitequark> this is completely insane.
niggler_ has joined #elliottcable
niggler has quit [Ping timeout: 265 seconds]
<purr> <Navarr> i'm wondering if #Paws isn't really a language, but a state of zen
niggler_ is now known as niggler
<cuttle> whitequark: oh yeah that pokemon hack is hardcore
fwg has joined #elliottcable
fwg has quit [Ping timeout: 240 seconds]
<purr> <devyn> elliottcable: イフィンdもstボアrdがめsとべ利家てゃt.
<whitequark> devyn: since when do you use google translate for japanese?! I AM DISAPPOINT
<purr> <devyn> AIIIIIIIAHHHH
yorick has joined #elliottcable
fwg has joined #elliottcable
Sgeo has quit [Read error: Connection reset by peer]
alexgordon has joined #elliottcable
<whitequark> you know
<whitequark> when about the only person who can actually say how to make your JS fast is the freakin' compiler author
<whitequark> how about using. less. moving. parts. in. your. fucking. languages.
<whitequark> and in completely platonic languages, too.
<prophile> fewer
<yorick> whitequark: the problem is the JIT outsmarts jsperf quite a lot
<yorick> whitequark: http://youtu.be/65-RbBwZQdU
<prophile> I'm looking at implementing an STL compiler (slightly too late)
<prophile> it watches the way your code actually runs, then compiles it to something that would have been fast once it's finished
<whitequark> yorick: well exactly!
<whitequark> the JIT is so smart you have no idea what it's actually doing unless you are *specifically a developer of that JIT*
<whitequark> even just understanding JITs in general doesn't work
<yorick> the proposed solution is stop caring about performance :)
<whitequark> oh and don't even think about memory usage
<whitequark> well
<whitequark> that's where it's generally headed
<whitequark> and fuck that. the culture of worse is better. seriously, fuck it so much.
<yorick> I mean you should still not do stupid things, but writing |0 instead of Math.floor are things that are stupid and outsmarted by the JIT
<yorickpeterse> FUCKING HIGHLIGHTS, I THOUGHT I FIXED THEM
<prophile> |0 looks almost like a perlism
* prophile evaporates
<yorick> ohi yorickpeterse :D
<whitequark> yorick: outsmarted by *one specific* jit
<whitequark> and have basically no guarantees for other jits
<whitequark> also consider that e.g. webkit has *four tiers* of them
<yorick> whitequark: generally changing your algorithm has a far greater effect than micro-optimizations
<whitequark> yorick: what about when you already use an optimal algo?
<whitequark> which is, majority of the cases.
<whitequark> think about all those guys writing games in webgl. if you can improve render loop by 50%, it means the difference between 40fos and 60fps.
<yorick> whitequark: they made asm.js for less moving parts
<yorickpeterse> lol asm.js
<purr> lol
<whitequark> don't even ask me about asm.js
<yorick> whitequark: also, around 20:15 the video has an example optimization
<yorickpeterse> JQUERY IN ASM.JS FOR WEBSCALE
<yorickpeterse> BARE METAL JQUERY
<yorickpeterse> DOWN TO THE CORE
<yorickpeterse> (sounds like a metal song)
<whitequark> lol elliott's comment
<yorickpeterse> whitequark: you seen that thing that compiles JS to Lua for microcontrollers or something?
<yorickpeterse> I thought that was pretty funny, going from JS to Lua
<whitequark> tessel?
<yorickpeterse> Yeah I think that's the one
<whitequark> I think it's good tech
<whitequark> and seemingly a very strong team
<yorickpeterse> idea wise maybe, but the whole "EVERYBODY KNOWS JS" mantra is getting on my nerves
<whitequark> well, they've got quite a bit of things together apart from js
<whitequark> and on mine too
<whitequark> prophile: (fewer) thanks btw, I always forget that
<yorickpeterse> whitequark: also
<yorickpeterse> GIVE US FOUNDRY ALREADY DAMN IT
<yorickpeterse> I DON'T LIKE C/C++/D ENOUGH
<yorickpeterse> Though D is a hell of a lot better than C/C++
<whitequark> well
<whitequark> go learn ocaml and/or rust
<whitequark> imagine the same but with ruby object model and metaprogramming
<whitequark> decide if you wanna it
<yorickpeterse> Rust is too young, ocaml I'm not really sure about yet
<yorickpeterse> Not a huge fan of the ML inspired syntax
<yorickpeterse> My only real issue with D so far is that it doesn't have any proper runtime reflection
<yorickpeterse> or a system similar ro Ruby's Object#send
<yorickpeterse> you can only do that using static strings that are known during compilation
PragCypher has joined #elliottcable
<whitequark> foundry doesn't have runtime reflection either
Cypher has joined #elliottcable
Cypher is now known as Guest77102
<yorickpeterse> does it have something similar to Object#send that works on non static input?
<yorickpeterse> that is, something like `herp_derp = 'user input here ....' send(herp_derp)`
PragCypher has quit [Client Quit]
Guest77102 has quit [Client Quit]
<whitequark> yorickpeterse: nope
<whitequark> and it's by design.
<yorickpeterse> boooo
<yorickpeterse> In D as far as I currently understand you either end up with a gigantic switch or you have to start throwing function pointers around (if you want some kind of list of "callbacks" or w/e)
<ELLIOTTCABLE> Driving, but,
<ELLIOTTCABLE> cuttle: here?
<ELLIOTTCABLE> Solved.
<ELLIOTTCABLE> Abstract "staging" becomes concrete "event", gains implementor's-API.
<ELLIOTTCABLE> add user's-API procedure, something akin to `create_event`
<ELLIOTTCABLE> identical to stage; BUT, creates a permanent Event for that individual staging when it occurs.
<ELLIOTTCABLE> both that new Event, and the result of the procedure staged, are returned, whenever the called-procedure executes.
<ELLIOTTCABLE> basically, call-with-current-event, akin to call-with-current-continuation
<ELLIOTTCABLE> unsure of that API, discuss later for happies
<ELLIOTTCABLE> Events are just Objects. They can have members, etceteras.
<ELLIOTTCABLE> Such as, "insanity": 43.
<ELLIOTTCABLE> or some shit.
<ELLIOTTCABLE> and finally, the crux:
<ELLIOTTCABLE> At any point in the program, a full list of every Event generated, that has effected the list-generation point, can be obtained.
<ELLIOTTCABLE> (Effected in the insanity-light-cone-sense.)
<ELLIOTTCABLE> Events cannot be *removed*, but they can be time-travelled back out of, obviously. And they can be modified, as you desired, cuttle.
<whitequark> yorickpeterse: well, you can generate that giant switch with metaprogramming
<whitequark> but that's about it.
<ELLIOTTCABLE> Should satisfy all of our requirements for insanity, data-taint, etceteras.
<whitequark> ELLIOTTCABLE: what about locality?
<whitequark> how can I isolate library code from outside if it uses events?
<ELLIOTTCABLE> You're not supposed to be able to.
<ELLIOTTCABLE> If something insane calls into your library code, your library code is insane. Whether you like it or not.
<ELLIOTTCABLE> That's kind of, y'know, the point.
<whitequark> um, what?
<whitequark> either I don't understand something cool
<whitequark> or paws is along with the FORTRAN full of GOTOs in the maintainability sense
<whitequark> brb sleep, will read backlog
cloudhead has joined #elliottcable
<yorickpeterse> sleep at 16:30?
<yorickpeterse> are you slacking off?
<yorick> yorickpeterse: oooh, someone made it an image macro http://i.qkme.me/5a42.jpg
<ELLIOTTCABLE> These are, before anything else, a replacement for exceptions. Error-handling.
<ELLIOTTCABLE> They're *meant* to be non-local flow-control, because non-local flow-control is necessary to handle errors that didn't occur locally, but first *affect* you locally;
<ELLIOTTCABLE> and most importantly, the goal is to integrate this mechanism with time-travel in such a way as to bring error handling *back* to locality.
<yorickpeterse> yorick: ALAS POOR WHO?
<yorickpeterse> ELLIOTTCABLE: are you high?
<ELLIOTTCABLE> yorickpeterse: what?
<ELLIOTTCABLE> yorickpeterse: sure hope not, 'cause I'm doing 124 on the highway while IRC'ing
<yorickpeterse> get off IRC nerd
<ELLIOTTCABLE> yorickpeterse: why do you ask?
<yorick> ur a nerd
<yorickpeterse> ELLIOTTCABLE: because of the whole "if insane code touches your code your code is insane" thing
<ELLIOTTCABLE> Why's that make me high?
<yorickpeterse> because it's a pretty dumb statement
<yorickpeterse> "if somebody uses your bike and breaks their neck it's your fault"
<alexgordon> hi ELLIOTTCABLE
<ELLIOTTCABLE> Hi
<purr> ELLIOTTCABLE: hi!
<ELLIOTTCABLE> yorickpeterse: happy to discuss later. Driving.
<ELLIOTTCABLE> Only came in to shoot my new API refinements at cuttle
erinspice_ is now known as erinspice
<erinspice> hallo
<alexgordon> hi erinspice
<jvulc> Hi
<purr> jvulc: hi!
<purr> <Nuck> I love the feeling of blood on my dick
<yorickpeterse> wat
cloudhead has quit [Ping timeout: 245 seconds]
<alexgordon> yorickpeterse: what type of blood though o_O
<alexgordon> A+? B-?
eligrey has joined #elliottcable
<purr> <eboy> We need some command to murder the person who created the aforementioned command.
<purr\Paws> [Issues] ELLIOTTCABLE comment on issue #6: Hint of an idea … using the execution *itself* as aforementioned mutex. (But doesn't staging something require ownership of it?) https://github.com/Paws/Issues/issues/6#issuecomment-26919766
<cuttle> hi ELLIOTTCABLE
<cuttle> yorickpeterse: look. say you have an expression 3 + x. if x is insane, 3 + x is also insane.
<cuttle> yorickpeterse: additionally, if some code becomes insane and calls some function, that call of that function is also insane.
<joelteon> oh so it's undefined behavior
<cuttle> joelteon: not at lal
<cuttle> all*
<joelteon> no it has the same effect though
<cuttle> you track the contagion of insanity
<cuttle> so you can retry exactly what you need to
<cuttle> yorickpeterse: it's not a question of fault and morality, so talking about using a bike and breaking their neck is entirely irrelevant
<cuttle> yorickpeterse: insanity flows only in the direction of dependencies, so if you use a bike, the bike is sane, but you become insane, the bike doesn't become insane as well
<alexgordon> cuttle: lolwat
<purr> lolwat
<cuttle> alexgordon: ...
<alexgordon> insane?
<cuttle> alexgordon: breaks invariants
<alexgordon> pretty sure that's not a compiler term of art
<cuttle> alexgordon: Something Is Wrong™
<cuttle> ...we've been calling this insanity for literal months
<alexgordon> like undef in llvm?
<cuttle> no
<cuttle> it's an error handling system
<alexgordon> like undef in llvm?
<cuttle> i don't know what undef in llvm
<cuttle> is
<cuttle> but it's like exceptions but way better
<alexgordon> it's a value that can appear in LLVM IR that denotes that the value is undefined
<cuttle> and no, it's almost entirely unlike undef
<alexgordon> a bit like undefined in javascript I guess, but internally in a compiler
<cuttle> undef is like
<cuttle> "it's ok if you give me garbage memory here"
<alexgordon> well yeah but a bit more than that
<cuttle> but the point is it's got nothing to do with error handling at all
<cuttle> you don't mark an erroneous value undef
<alexgordon> "Because the undefined operation “can’t happen”, the optimizer can assume that it occurs in dead code [and remove it]."
<alexgordon> cuttle: yeah not really
<cuttle> alexgordon: like i said it's more analogous to exceptions
<cuttle> but *way* better
<alexgordon> this is fascinating
<alexgordon> TIL that anodizing is tattoos for metal
<cuttle> ELLIOTTCABLE: when you call a library, the library itself doesn't become insane; that particular call of the library is insane
<cuttle> ELLIOTTCABLE: the thing though that may be problematic about this whole thing is that
<cuttle> once you know something is insane why not just stop it spreading all together
<cuttle> altogether*
<cuttle> unless you like find out it's insane after the fact, in which case you can't ever throw away any data ever
<alexgordon> reading this I get the impression that the reason apple is assembling stuff in the US is because jony ive wanted to make a Really Fucking Cool Factory
* alexgordon goes on youtube to look at videos of pick and place machines
<cuttle> ELLIOTTCABLE: also take a look at common lisp restars
<cuttle> ELLIOTTCABLE: restarts
<ELLIOTTCABLE> <alexgordon> TIL that anodizing is tattoos for metal
<alexgordon> did you read the description of it
<alexgordon> "Electrical current is run through aluminum in an acid bath, causing oxygen molecules to bond to aluminum producing a thin, uniform layer of aluminum oxide (basically: aluminum rust). Because this surface layer is porous, dye can be used to add nearly any color to the aluminum part before the surface is sealed."
<ELLIOTTCABLE> <alexgordon> reading this I get the impression that the reason apple is assembling stuff in the US is because jony ive wanted to make a Really Fucking Cool Factory
<ELLIOTTCABLE> Lol'ing
<purr> Lol
<ELLIOTTCABLE> So. Driving. But.
<alexgordon> ELLIOTTCABLE: the most important question is ARE YOU GOING TO BUY ONE OF THESE?!
<ELLIOTTCABLE> The library you call *may* become insane, if it has some global state that is touched/mutated by the insanity
<ELLIOTTCABLE> It's just a light-cone, guys
<ELLIOTTCABLE> Nothing to see here, move along and eat a dick
<ELLIOTTCABLE> @ yorickpeterse, cuttle
<cuttle> ELLIOTTCABLE: sure if it has global state
<ELLIOTTCABLE> Re: stop it altogether … you CAN, but SHOULDN'T
<ELLIOTTCABLE> Insanity is a bit erlangy.
<yorick> ELLIOTTCABLE: you should totes make #elliottcableacademy a thing with subjects *I* want to know
<ELLIOTTCABLE> Except instead of continuance by copious giving-up … it's continuance by copious trying-harder
<ELLIOTTCABLE> yorick: wat
<yorick> like haskell.
<yorick> or erlang
<yorick> or zfc set theory
<cuttle> yorick: ELLIOTTCABLE doesn't know any of those
<cuttle> haha
<cuttle> i know haskell pretty well
<yorick> or complexity theory
<cuttle> but not the others in any detail
<ELLIOTTCABLE> #IRCinacupholder
<yorick> dammit ELLIOTTCABLE
<ELLIOTTCABLE> yorick: wat i do
<yorick> cuttle: where am I supposed to learn these things now? do I need to read *books* or something?
<cuttle> haha
<cuttle> wikipedia is wonderful
<cuttle> and so are online things like learn you a haskell and irc and mailing lists
<cuttle> :p
<cuttle> that's how i learn
<alexgordon> yep
<cuttle> well i am going to get lunch
<cuttle> bye everyone
<cuttle> o7
<cuttle> it's ridiculous how like
<cuttle> the continuum hypothesis is such an everyday example of godel's incompleteness theorem
<cuttle> alexgordon: you know?
<cuttle> anyway be back in a bit
<yorick> the continuum hypothesis is any kind of everyday example?
<yorick> but yeah it is something you can't prove/disprove
<devyn> whitequark: it's called having my IME set to Japanese when typing English
<devyn> whitequark: oh also that's just nerdbrain disorder. :)
<joelteon> this is hard
<joelteon> we really, really need to move our corporate app away from ruby
<devyn> joelteon: how come?
<joelteon> because dynamic languages in general just suuuck diiiiiiiicks
<devyn> I've yet to find a static language that can keep up with the really quick development turnaround usually required for webdev
<cuttle> yorick: everyday as in
<cuttle> yorick: we did some extremely abstract math, godel's theorem
<yorickpeterse> cuttle: oh?
<cuttle> yorick: and in an unrelated area of math, just doing some good old number stuff about the reals and countability
<yorickpeterse> I was never a huge fun of the hardcore maths, probably because it was explained terribly by my teachers
<joelteon> devyn: i mean, yeah...
<cuttle> like, it just pops up, something we were interested in proving, and it turns out to be unprovable
<joelteon> that's the problem
<joelteon> we can work faster but shit breaks
<devyn> pretty much, but the "work faster" part is really necessary
<joelteon> yeah i know
<joelteon> :(
* yorickpeterse wonders how long he can keep going without people noticing he's not yorick
<devyn> man I don't even know who you are
<cuttle> honestly javascript replaces a lot of the slow dev time of static languages with frustrated debug time
<cuttle> but yeah i would agree it takes longer to write code in like rust or c
<yorickpeterse> devyn: I am Yorick
<yorickpeterse> but not yorick
<devyn> cuttle: JS? totally. Ruby? no
<yorickpeterse> we just happen to share the same first name *and* live in the same city
<devyn> ah, haha
<devyn> wow
<cuttle> devyn: yeah i'd agree it's not all dynamic, languages; js is particularly bad
<cuttle> ruby tends to fail a lot faster and give better info
<yorick> devyn: ELLIOTTCABLE decided to breed another yorick
<joelteon> i just wish
<joelteon> like i wish we could use a really *good* static language
<devyn> yorick: we don't need two of you >.>
<devyn> :)
<yorick> cuttle: everyday as in every day
<cuttle> joelteon: haskell's pretty static and extremely good
<cuttle> but sometimes hard to apply to things
<joelteon> yeah, i was gonna suggest haskell, but then everybody would get mad at me
<cuttle> like all the web frameworks *suck*
<yorick> devyn: well we don't need a devyn and a devin
<joelteon> yesod is okay
<cuttle> yorick: we do have one :p
<cuttle> joelteon: isn't it all monad stackey
<devyn> cuttle: yeah it's mostly that Ruby has a good exception system that people actually use properly
<cuttle> yorick: everyday was kind of tongue-in-cheek :p
<joelteon> joelteon: yea
<joelteon> er shit
<joelteon> cuttle: yes
<yorick> yorickpeterse: how do you work at a big data startup without mathematics
<devyn> yorick: how dare you compare me to dsamarin (who isn't in here o.o) ;)
<joelteon> you whore
<devyn> I love dsamarin jk
<yorickpeterse> yorick: I didn't say it didn't involve math or that I didn't know any of it
<yorickpeterse> also beyond the basics it's not often needed
<yorickpeterse> at least not in our case
<yorick> yorickpeterse: basics as in?
<cuttle> joelteon: monad stacks make me want to kill myself
<yorick> devyn: I still he should just call himself sephr
<cuttle> code written with monad stacks basically lets you use *none* of the rest of haskell
<yorickpeterse> yorick: "just basic math" really
<joelteon> cuttle: but it's not that bad
<cuttle> like i'd honestly prefer to just use a side-effecting language than haskell+monad stacks
<joelteon> once you get used to it
<yorick> yorickpeterse: as in linear algebra?
<cuttle> sure you can get used to it but it's like worse than non-haskell
<yorickpeterse> yorick: not even that
<yorick> wtf am I learning all this shit for :D
<cuttle> linear algebra is fucking cool
<cuttle> is why
<yorick> true
<yorickpeterse> the last time I actually did math was when I was messing around with some algo to determine how shit a website is
<yorickpeterse> http://www.olery.com/guest-experience-index/ <- this is our only real serious math stuff that I can think of from the top of my head
<devyn> yorick: why would dsamarin call himself sephr
<yorick> I'm trying to understand quantum computing which requires linear algebra with complex numbers
<devyn> yorick: you're thinking of eligrey
<yorick> devyn: SEE, I keep confusing them since they changed nicks
<yorickpeterse> well if you actually want to do quantum computing that makes sense
<devyn> yorick: dsamarin is eboyjr :p
<yorick> devyn: there's e**y and dsamarin who's probably sephr
<yorick> I can deal with one of them changing nicks
<yorick> yorickpeterse: no but quantum computing is the fuuuutuuuureeee
<devyn> well they both decided they wanted more professional nicks, I guess
<devyn> I've always just used my name
<devyn> never got into the pseudonym thing
<cuttle> yorick: hahaha e**y, didn't notice that
<yorick> cuttle: my client marks it the same color as "eboy", too
<cuttle> haha
<yorick> it's a mental hash collision
<devyn> probably caused by a real hash collision :P
<alexgordon> linear algebra is cool, but boring
<joelteon> you're cool, but boring
<alexgordon> thanks joelteon!
<ELLIOTTCABLE> Hi
<purr> ELLIOTTCABLE: hi!
<ELLIOTTCABLE> Craaaaaaazy moving day
<purr> <alexgordon> she sells csh by the C shore
<ELLIOTTCABLE> But stopping long enough to poop. And thus, IRC.
<yorick> ew
<devyn> can you not
<devyn> poop doesn't transmit well over IRC
<joelteon> i got an account on dressed.so
<devyn> it spreads
* devyn out
<joelteon> now complete strangers on the internet can judge my clothing
<devyn> that sounds fun
<devyn> I'm gonna go frag some noobs
<joelteon> it's da bes
<yorickpeterse> devyn: nerd
cloudhead has joined #elliottcable
<devyn> I'm actually really bad at it
<devyn> it's just fun
<devyn> :p
<alexgordon> joelteon: this is a clever concept
<joelteon> what is
<alexgordon> dressed.so
<joelteon> yeah
<joelteon> clever domain name
<alexgordon> I meant more the affiliate business model
<joelteon> yeah but the domain is too
<alexgordon> ...I've been on HN too long
<alexgordon> start to judge things by business model
<joelteon> oh no the guy running d.so is losing lots of money
<alexgordon> losing? how
<joelteon> because it doesn't make any money
<joelteon> he can't possibly make a profit
<alexgordon> well
<alexgordon> how could it lose money?
<joelteon> hosting costs?
<joelteon> you have to host somewhere
<alexgordon> takes what, a $5 digital ocean box?
<alexgordon> :P
<joelteon> ok maybe not a "lot"
<joelteon> but he's losing money
sharkbot has quit [Remote host closed the connection]
sharkbot has joined #elliottcable
<devyn> bird say: tweet tweet
<cuttle> whe
cloudhead has quit [Ping timeout: 264 seconds]