<katlogic>
10 years old language, not notable enough
<katlogic>
ah, not 10, only 6
<katlogic>
I guess thats ok then.
<glowcoil>
haha
<vigs>
hey, anyone know how to stop this form from refreshing the page when I hit enter? :<
<katlogic>
IKR, ALL FORMS DO THAT, IT DRIVES ME CRAZY
<vigs>
yick
<devyn>
Nimrod looks like python + js + c
<joelteon>
i hate python
<devyn>
#rubymasterrace
<devyn>
(honestly, I agree; I really hate their conventions and feel like Ruby is much prettier to look at, not necessarily because of syntax but because the conventions are just more attractive)
<joelteon>
it just feels weird
<devyn>
the whole "there is only one way to do things" really gets in the way of expressiveness IMO
<joelteon>
in the django settings file, you define a big list of constants
<joelteon>
then you import that module and reference the constants in it for your configuration
<joelteon>
it just feels weird
<joelteon>
i can't say it's bad
<katlogic>
devyn: Nimrod is hated mostly for its pascal heritage
<devyn>
well, I don't know; if that's a common pattern in Python applications then I can see where it comes from
<joelteon>
yeah
<joelteon>
a better example would be
<joelteon>
explicit self
<devyn>
C header files as configuration and such
<joelteon>
and having a 'request' argument that has to be passed in
<katlogic>
Somehow pascal was almost always universally hated, with the exception of kids who learned tp7 at school as their first language.
<joelteon>
for every view function
<devyn>
I don't really get the hate for pascal. Never really tried it but it looks perfectly decent to me
<joelteon>
like in ruby you get the 'request' method
<katlogic>
devyn: Take a Python grammar & style nanny, throw in some type system invented in 10 days in the mix, bon apetit, Pascal.
<devyn>
surely it gets some slack for being relatively old though
<devyn>
if someone did that *today* it would be like, pff, whatever
<katlogic>
indeed it does, they didnt know better back then
<devyn>
fuckkk Guilty Crown has such a good soundtrack
mcc has joined #elliottcable
<devyn>
katlogic: > The only escape from this infinite regress is to define a family of routines with a member for each possible string size, or to make all strings (including constant strings like 'define' ) of the same length.
<devyn>
EW
<devyn>
but I thought the term "Pascal string" came from something like struct { unsigned int len; char *ptr; }
<katlogic>
Well, half of that was fixed with various bandaids.
<katlogic>
Basically by making pascal more C-like, thus making it stray from its roots (being easy to learn).
<katlogic>
devyn: Too bad that other than production values, the series are far from memorable :(
<katlogic>
IIRC it attempted to ripoff noein/bleach and failed spectacularly
sharkbot has quit [Remote host closed the connection]
sharkbot has joined #elliottcable
mcc has quit [Quit: This computer has gone to sleep]
<devyn>
katlogic: oh god I was like what the fuck are you talking about. Guilty Crown. eh, it wasn't bad. the music and art definitely made up for it, I think; music and art that beautiful just overwhelm everything
<devyn>
not everything has to be well-balanced :p
<devyn>
I can appreciate a series just for the art and music, just like I can appreciate a song based on how well it all fits together instead of complaining about the use of autotune when it actually fits the style
<devyn>
(I bring this up because I had that discussion with someone last night)
<devyn>
hint: when the autotune is obvious, it's probably because it's being used stylistically and not because they're trying to make up for crappy singing.
<vigs>
I'm violently and vehemently opposed to autotune
<devyn>
okay, rationalize your position to me
<vigs>
It's usually used to make up for terrible singing. When used stylistically, that comes down to personal preference: I hate overproduced music. The closer to how it'd be if the band were performing IRL, the better.
<devyn>
I agree when it's being used to make up for bad singing, yes
<devyn>
but it's a bit more subtle then, and just kind of annoying
<vigs>
I generally don't like too much tech used in music, which is a weird stance for me to have. I also don't like *too* many guitar effects pedals in music. Really all you need is your standard distortion and a clean tone, and you're solid.
<devyn>
that's a perfectly fine view to have
<devyn>
I can appreciate that too
<vigs>
lol I'm glad it's devyn approved :P
<purr>
lol
<devyn>
:p
<devyn>
no, but I mean, I can appreciate more physical/natural music like that as well
<devyn>
I love acoustic songs
<devyn>
however
<devyn>
I don't think there's anything wrong with production
<devyn>
like, lots of it
<devyn>
I think it makes much more sense when you think of the production as the art form being demonstrated
<devyn>
music production is not easy either
<devyn>
it takes talent
<devyn>
and skil
<devyn>
skill*
<devyn>
and so I think it's cool if songs are demonstrating more "physical" talent
<devyn>
but I think it's also cool when songs are demonstrating talented production
<devyn>
but of course the artists who actually play/sing usually get most of the credit and the fame, and when we're talking about music that's mostly about production, that's lame
<devyn>
because it's really the producers that are doing the hard work
<devyn>
and being really creative
<vigs>
Right, but I feel like production takes the "skill" away from music (bear with me here); I think that because it removes the performance aspect. That's really important to how I place value in music.
<devyn>
it seems to me that a lot of people feel that way, but, why? why does music only have to be about (live) organic performance? why can't it be about well-prepared, organized, synthetic sequences?
<vigs>
A lot of people hold that belief? LOL as if. I feel like I'm in the minority.
<purr>
LOL
<vigs>
It's all about EDM or whatever these days. Yuck.
<vigs>
"aw man check out this sick beat" yeah okay where's the SUBSTANCE? (I put a lot of weight in the lyrics and intent of a song)
<devyn>
honestly I'd say it's just as common, it's just that "mainstream" is not necessarily controlled by what a large majority thinks but what record companies *want* you to think, and publicize
<devyn>
and I see it so much and most of the people who feel that way feel that they're underrepresented because they don't see what they like on the radio and on TV and in popular culture
<devyn>
but... when you've got a whole group of many thousands of people all talking about how much they hate music these days, I don't think that you can really call it "uncommon"
<devyn>
:p
<vigs>
Dude, I'm super into punk. lol if that's ever on TV or the radio
<vigs>
Sure, it had a little stint with popularity in the 90s, but that left us with pop punk, which stripped the punk sensibility away, and just kept some exaggerated elements of the aesthetic (from fashion to the actual sound of the music)
<devyn>
exactly, but I feel that people who are into alternative/non-mainstream music really try to emphasize their non-conformity and how uncommon what they like is
<devyn>
just because it isn't the cultural "mainstream" doesn't make it uncommon :p
<devyn>
it means it doesn't sell as well, sure
<devyn>
which can mean less incentive for people who are just in music for money anyway, but then you get people who actually respect what they produce, and that's not such a bad thing
<vigs>
I can't speak to the others, but I really do feel in the minority. Most people I know are into either electronic music of some sort, or country.
<vigs>
In high school, expressing literally any contrary opinion to music labeled you as a "hipster" and people assumed you liked shit like Neutral Milk Hotel or whatever.
<devyn>
circles and location. most people really don't like country music at all here, except for pop-country Taylor Swift kinda stuff
<vigs>
The country nonsense is definitely kinda localized to the central coast: it wasn't as popular back in the bay area
<devyn>
EDM... sure, but I wouldn't say it's as huge as even just plain pop/rock stuff
<vigs>
Here, there's a bunch of agriculture stuff, so country is p popular
<vigs>
EDM, dubstep, and other electronic music genres have always been popular since I was in middle school
<vigs>
I've had exactly two peers who like the music I do. It's pretty bullshit.
<devyn>
they're popular, but I wouldn't say they're nearly as mainstream as pop/rock (which isn't really fair because it's a genre with a pretty loose definition)
<vigs>
examples of things in that genre? Because I'm inclined to disagree with the "rock" part of that
<devyn>
you will almost certainly disagree with the rock part of it for most songs
<devyn>
but that's just what it's called
<vigs>
yick
<vigs>
Anyway, the whole electronic culture has prevailed in the places I've been. Gloving, glowsticking, the whole nine yards.
<vigs>
Also includes things like longboarding.
<vigs>
That seems to be part of that culture, too.
<vigs>
Which is super strange, because the whole skating thing got bastardized from a "fuck you I'll skate where I want" thing to a "yo man let's just chill and cruise around town" thing
<devyn>
it's... here, but I wouldn't say it's that prevalent
<vigs>
It's basically all I see.
<devyn>
so I think you may have some bias just due to where you are
<devyn>
:p
<vigs>
where are you, devyn?
<devyn>
Vancouver
<vigs>
gotcha
<vigs>
But yeah, even a bunch of people I know online are into the whole electronic thing. Maybe it's because a lot of them are devs?
<devyn>
nah, I know devs who are into anything from classical to jazz to rock to whatever so I don't think that really has any bearing on what kind of music people like :p
<devyn>
I enjoy electronic music, but I also enjoy like... everything
<devyn>
though I could never really get into pure rap or country
<vigs>
Yeah, I used to be like that. At one point, I was just super sick of the music I had.
<vigs>
I started by sifting through the music I had, tried to pick out what I enjoyed, and came up with similarities they shared.
<devyn>
other than that though, my music library is extremely varied in genre and mostly in Japanese because, well, what.cd
<vigs>
Then I went off to find more things like it. Thanks to Pandora, I quickly found The Ramones and the Sex Pistols, whose stations introduced me to some of my favorite bands.
<vigs>
Yeah, I used to have a bunch of Japanese music, too. Things from anime openings/closings to some random stuff I found online, including vocaloids
<devyn>
I would say there are things I definitely don't like that much in my library that I kinda regret downloading in the first place, but my tastes are definitely very varied
<devyn>
and I do like most of the stuff in there, I think
<vigs>
Yeah, I was totally in the same boat. Not sure what snapped in me, but I'm glad it did. Analyzing my library (and myself, I suppose) really helped me get my shit together :P
<devyn>
haha
<devyn>
ehh I don't really think I'm the same way :p sometimes I feel like classical, sometimes I feel like jazz, sometimes funk, sometimes boring pop
<devyn>
really depends on my mood
<devyn>
but I usually know what I want'
<devyn>
I don't find myself shuffling through my entire library most of the time
<vigs>
Yeah, I mean, I'm not EXCLUSIVELY into punk, but my tastes do usually depend on my mood. I spent a few hours today listening to classical, which was pretty chill
<devyn>
you should check out veniceclassicradio.eu
<vigs>
When I had my "I like everything but rap" phase, I did like some electronic music. My friend told me recently that the stuff I really liked from that is "happy hardcore," so that's a thing ¯\_(ツ)_/¯
<katlogic>
Yeah, rave/happycore is indeed a thing, though only with high dosages of caffeine
<katlogic>
otherwise it sounds just way too frantic
<devyn>
not even return false, since jQuery provides a compatible preventDefault()
<devyn>
I believe
<devyn>
(preventDefault() is now part of DOM too)
<katlogic>
still its weird, it almost looks like he never hooked the event in the first place
<katlogic>
perhaps forgot domready?
<devyn>
you can't hook submit() on a text field
<devyn>
that definitely won't work
<devyn>
so that's part of it
<devyn>
lol
<katlogic>
yeah, that too :)
<vigs>
yeah >_<
<devyn>
"Did you know the Old Spice "I'm on a horse" commercial used no green screen? They actually built a rig to slide a man off a boat onto a horse."
<joelteon>
i hate working with javascript libraries
<joelteon>
15,000 lines of javascript in total so that i can use tipsy and selectize
<joelteon>
oh and bootstrap includes some
<vigs>
lol
<purr>
lol
<ELLIOTTCABLE>
whitequark: Wow. That guy spectacularly-well misses the point.
<ELLIOTTCABLE>
/cc alexgordon
<ELLIOTTCABLE>
*most* of his points are very salient, and I agree pretty strongly overall with that article.
<ELLIOTTCABLE>
also, it led me to some great reading about concurrency; I'm *still* going down that informative rabbit-hole. (see: twitter)
<ELLIOTTCABLE>
but I stopped short and wanted to remember to come back here and comment before I go back to reading all this
<alexgordon>
ELLIOTTCABLE: he misses the point about concurrency
<katlogic>
does he?
<ELLIOTTCABLE>
no, disagree
<alexgordon>
katlogic: yes
<ELLIOTTCABLE>
he *nails* the point about concurrency.
<alexgordon>
threads are a shitty model for concurrency
<ELLIOTTCABLE>
disagree.
<katlogic>
The first offputting experience I had with nodejs was exactly that
<whitequark>
ELLIOTTCABLE++
<purr>
Let it be known that whitequark loves ELLIOTTCABLE.
<ELLIOTTCABLE>
threads are a well-studied and adequate model for concurrency.
<alexgordon>
ELLIOTTCABLE: double disagree
<whitequark>
alexgordon: threads or lightweight threads?
<katlogic>
concurecy as in none, because no coroutines
<ELLIOTTCABLE>
they are not *the best*, but they are truly good.
<alexgordon>
whitequark: either
<whitequark>
don't think of threads in his articles as "pthreads"
<ELLIOTTCABLE>
truly good. not shitty.
<whitequark>
or even "green threads"
<whitequark>
alexgordon: think "lwt"
<ELLIOTTCABLE>
oh shush everybody, ELLIOTTCABLE has things to say.
<whitequark>
monadic threads.
<ELLIOTTCABLE>
#importantpersontalking
<ELLIOTTCABLE>
#guisereallylisten
<alexgordon>
whitequark: ANY kind of threads are a bad model for humans
<ELLIOTTCABLE>
#please?
* whitequark
glares at ELLIOTTCABLE
<ELLIOTTCABLE>
#v.v
<joelteon>
ok but some threads are a pretty good model for servers
<whitequark>
alexgordon: programming is a bad model for humans
<whitequark>
and math
* whitequark
shrugs
<purr>
¯\(º_o)/¯
<alexgordon>
joelteon: threads are a good model for implementing concurrency libraries
<ELLIOTTCABLE>
whitequark: you already know how much I disagree with that point of view :P
<ELLIOTTCABLE>
OKAY BUT THAT'S ALL BESIDES THE TOPIC.
<katlogic>
alexgordon: Said no node.js apologist ever. Meanwhile EVE online runs stackless python and microsoft uses gunicorn.
<alexgordon>
threads are not what people should be using day-to-day
<alexgordon>
katlogic: ?
<ELLIOTTCABLE>
the article, despite alexgordon, nails concurrency. Node.js is Not Good for Concurrency(tm).
<alexgordon>
katlogic: I don't care what people use, I care what's right!
<ELLIOTTCABLE>
EVE Online <3
<ELLIOTTCABLE>
katlogic: you play?
<katlogic>
alexgordon: :)))
<katlogic>
ELLIOTTCABLE: dropped it long ago
<alexgordon>
threads are hard to reason about, threads don't make sense
<alexgordon>
the callbacks in node, while the syntax is shitty, they're easy to reason about
<whitequark>
you're trolling
<alexgordon>
I'm not
<ELLIOTTCABLE>
katlogic: EVE online was my monetary playground. I learned half of what I know about managing investments and influencing people from my father, and then the other half from attempting to apply that in a giant spreadsheet- / marketing-simulator.
<whitequark>
then you're inane
<alexgordon>
heh
<alexgordon>
inane or insane?
<ELLIOTTCABLE>
I was damn near a trillionaire before I quit that game, and very happy with it :P
<alexgordon>
maybe both
<whitequark>
inane
<ELLIOTTCABLE>
careful with "insane"
<whitequark>
I'm not *that* bad at english
<ELLIOTTCABLE>
that's nearly a compliment in this room
<ELLIOTTCABLE>
whitequark: you're not bad at English at all. You're extremely competent.
<alexgordon>
ELLIOTTCABLE: nah he said inane
<ELLIOTTCABLE>
ANYWAY
<alexgordon>
threads are dumb
<katlogic>
ELLIOTTCABLE: Never had chance to permeate into that. We've just goonswarmed a titan once a while.
<ELLIOTTCABLE>
alexgordon: yah, I saw. Was just commenting on the side.
* katlogic
used no dark jewish magic
<ELLIOTTCABLE>
katlogic: I never really got into the combat too much.
<whitequark>
ELLIOTTCABLE: tell me what that guy missed already
<katlogic>
but honest to god TI until everyone gave up
<whitequark>
and screw alexgordon, he's trolling but doesn't say it
<katlogic>
*TD
<ELLIOTTCABLE>
I mean, in the sense that I could afford to fly faction battleships as my primary craft, but other than that, meh
<alexgordon>
whitequark: I am 100% serious
<ELLIOTTCABLE>
whitequark: I doubt he's trolling. I understand at least part of his points, and do agree with him in the small.
<alexgordon>
whitequark: apple, microsoft and rust all agree with me too
<ELLIOTTCABLE>
here's my point of view:
<katlogic>
ELLIOTTCABLE: But yeah, I can tell you're quite well spoken.
<ELLIOTTCABLE>
A) whitequark's right. Threading is great.
<katlogic>
exactly the sleazy EVE corp guy type
<ELLIOTTCABLE>
B) alexgordon's right. Threading is terrible.
<katlogic>
neithers right
<katlogic>
because threading has horrible locking issues
<katlogic>
coroutines \o/
<whitequark>
...
<alexgordon>
ELLIOTTCABLE: obviously you can't get anywhere without threads, but they should not be your bread and butter
<whitequark>
katlogic: you do realize coroutines are unrelated to concurrency?
<whitequark>
like, at all
<alexgordon>
ok
<ELLIOTTCABLE>
C) You're both wrong, because A.1) threading is only *great* instead of just "good", because it's so well-understood; and well-understood is never a meaningful argument for **anything**, so screw that point, and B.1) threading is only *terrible* because it's unintuitive; it's a perfectly "good" model once you've gotten informed about it.
<joelteon>
i thought the problem with nodejs was that you *can't* write sequential code
<ELLIOTTCABLE>
what katlogic said.
<alexgordon>
say you want to start a web server, read a file from disk, and return it in the response
<joelteon>
not that you shouldn't
<katlogic>
whitequark: Concurenncy in node.js lingo means deferred execution and voluntary preemption.
<katlogic>
whitequark: Since duh, V8 knows no threads, eva.
<ELLIOTTCABLE>
actually, There's A Plugin For That(tm),
<whitequark>
oh god
<ELLIOTTCABLE>
but it's terrible and terrible and also evil and somewhat terrible
<ELLIOTTCABLE>
and stuff.
<ELLIOTTCABLE>
so
whitequark has left #elliottcable [#elliottcable]
<ELLIOTTCABLE>
lolnokthx
<purr>
lolnokthx
<vigs>
V8 is that tomato/vegetable juice thing, right? Yeah, that's p neat
<ELLIOTTCABLE>
OKAY SO, regarding the original argument, despite Eastern European Ragequit,
* katlogic
counts, this is his 3rd
<katlogic>
2 times coz of me
<ELLIOTTCABLE>
it's fine we're used to it much love etc
<katlogic>
2:1 yay me
<ELLIOTTCABLE>
I mean, all of you love me despite *my* failures, so I daily try hard to love each and every one of you despite *yours* <'3
<ELLIOTTCABLE>
(You *do* all love me despite my failures, right?)
<ELLIOTTCABLE>
(... right?)
* ELLIOTTCABLE
crickets
<ELLIOTTCABLE>
He nailed every point, until he tried to address the argument of JavaScript on the frontend and JavaScript on the backend.
<ELLIOTTCABLE>
when it gets to that, he *only* addresses the failures of that model for enterprise-scale (or lol"webscale") purposes.
<ELLIOTTCABLE>
yes, at some point, your giant important website is going to want native clients. Or, to generalize the argument and examine it well, we'll just say, at some point, your "website" may evolve into a "platform".
<ELLIOTTCABLE>
and it's obvious that, as a remote-server-side-host for an entire platform, Node.js is far from perfect.
<ELLIOTTCABLE>
(for many of the reasons he addressed.)
<alexgordon>
node.js is 1 syntactic sugar and 1 static type system away from a good concurrency model
<joelteon>
what's the first chunk
<ELLIOTTCABLE>
if you're going to simply be hosting an API to be consumed by divers user-experience hosts (website(s), mobile devices, IoT integration points, some dude's Pebble, you name it.),
<alexgordon>
joelteon: syntax proposal
<joelteon>
ok
<ELLIOTTCABLE>
then you'll want to move away from Node.js. (Not necessarily you *will*, but you'll definitely feel the pressure to. There are much better API-hosting languages than Node.js.)
<ELLIOTTCABLE>
WE BUILT THIS CITY~
<ELLIOTTCABLE>
WE BUILT THIS CITY, ON ROCK 'N ROOOOOOOOOL~~~
* ELLIOTTCABLE
breaks down
<alexgordon>
click the link ELLIOTTCABLE!
<ELLIOTTCABLE>
irccloud, dude
<ELLIOTTCABLE>
can read it without looking away
<joelteon>
ooh, and then with warp it's this
<joelteon>
run 80 $ responseFile "index.html"
<alexgordon>
lightweight threads are too concrete
<ELLIOTTCABLE>
oh shush joelteon
<joelteon>
what's up
<ELLIOTTCABLE>
can't compare code at two different abstraction-levels.
<alexgordon>
a language should be able to express parallelism and sequentialism
<ELLIOTTCABLE>
I could say with Rails, it's `rails generate new_project`.
<alexgordon>
those are the correct units of abstraction
<joelteon>
alexgordon: so does readText run in a separate thread
<alexgordon>
joelteon: THAT is an implementation detail
<joelteon>
ok, but isn't it important?
<joelteon>
threads are evil
<alexgordon>
no
<joelteon>
why not?
<alexgordon>
I didn't say threads are evil
<joelteon>
ok let me scroll up then
<alexgordon>
joelteon: I said it's evil for threads (or lightweight threads) to be the user-facing concurrency model in a language
<alexgordon>
behind the scenes, implement it however you want
<joelteon>
ok threads are dumb, is what you said
<joelteon>
that makes more sense
<joelteon>
ok, now i agree with you
<alexgordon>
I mean
<alexgordon>
what do you think node uses to implement concurrency?
<alexgordon>
threads!
<alexgordon>
:P
<joelteon>
yeah, that's why i was curious why you said threads are dumb
<ELLIOTTCABLE>
devyn: also, since it's on my mind: did you ever get into the execution model, in your Paws work?
<alexgordon>
joelteon: it doesn't just have to use threads
<joelteon>
no, we're good now
<joelteon>
i was just confused
<joelteon>
surprisingly
<alexgordon>
ha
<alexgordon>
usually you have some sort of run loop
<alexgordon>
where you process nonblocking IO
<alexgordon>
and also a thread pool
<joelteon>
i still think callback-based apis are gross and should not be necessary, or used
<joelteon>
especially the way node does it
<ELLIOTTCABLE>
also: Sublime Text is surprisingly cool.
<ELLIOTTCABLE>
I'm not head-over-heels, but I've never seen emulated vi support this thorough.
<ELLIOTTCABLE>
on the downside: it seems unable to hilight Coffeescript. I've no idea why. ddis
<alexgordon>
callbacks are by far the most obvious way of marrying runloop-based and thread-based concurrency into a single API
<alexgordon>
node's failing, if it has one, is that you have to write all the callback stuff yourself
<alexgordon>
but that a compiler away from being a solved problem
<joelteon>
callbacks are dumb and should not be the user-facing concurrency model in a language
<alexgordon>
*that is
<joelteon>
in my opinion
<alexgordon>
joelteon: wellll
<alexgordon>
joelteon: notice I used a callback in my code
<joelteon>
i sure did
<alexgordon>
I was talking with someone, I think glowcoil about this
<alexgordon>
joelteon: a callback makes sense in cases where you want to do multiple things in parallel
<alexgordon>
wrong words
<alexgordon>
but
<alexgordon>
example:
<alexgordon>
say I wanted to start three web servers
<alexgordon>
you have a combination of "things to do now" (start three servers) and "things to do later" (process requests)
<alexgordon>
you need nesting for that
<alexgordon>
in your syntax
<alexgordon>
you can't write that sequentially because it's too muddled - you would have to separate both things that are to be done at different times
<joelteon>
okay, but you don't need callbacks for that either
<alexgordon>
ehhhh
<alexgordon>
need to separate two things
<joelteon>
mapConcurrently id [server1, server2, server3]
<joelteon>
well
<alexgordon>
callbacks are a united way of doing something asynchronously
<joelteon>
unless the function argument to run is indeed a callback
<alexgordon>
so you do need callbacks somewhere
<joelteon>
which really
<alexgordon>
*unified
<joelteon>
i suppose it is
<alexgordon>
you can CHOOSE to not expose the callbacks in the user-facing language
<ELLIOTTCABLE>
ಠ_ಠ ooo that worked yay
<purr>
Let it be known that ELLIOTTCABLE disapproves of ooo that worked yay.
<joelteon>
what's what i'm saying
<joelteon>
that's*
<ELLIOTTCABLE>
-- ooo that worked yay
<purr>
Let it be known that ELLIOTTCABLE hates ooo that worked yay.
<ELLIOTTCABLE>
++ ooo that worked yay
<purr>
Let it be known that ELLIOTTCABLE is indifferent to ooo that worked yay.
<joelteon>
i think the node philosophy of the giant callback chain is possibly *the* worst way to write async code
<alexgordon>
joelteon: for sure
<alexgordon>
joelteon: but the opposite is bad too
<joelteon>
what's the opposite
<alexgordon>
never using closures in an API
<joelteon>
agreed
<alexgordon>
they should be used when they make sense
<joelteon>
the thing is, i still think the callback usage in your example is unnecessary
<joelteon>
each request is a separate entity
<alexgordon>
joelteon: in the user-facing code or in the translated code?
<joelteon>
oh, is that what the top thing is?
<alexgordon>
"http.server("*:80") do req" is furrow
<joelteon>
okay
<joelteon>
no, then that looks nice
<alexgordon>
http::server("*:80", [](const HTTPRequest& req, Callback<HTTPResponse> resp) { is the equivalent C++
<ELLIOTTCABLE>
the GitHub apps are realllllllly fucking beautiful