What color is your function? (2015)
journal.stuffwithstuff.com
What color is your function? (2015)
1–10 of 63 posts
Re: What color is your function? (2015)
#2Re: What color is your function? (2015)
#3Re: What color is your function? (2015)
#4All my functions ... every one I have ever written in my entire life: the color ass or doo doo brown.
It's especially important not to post unsubstantive stuff to a fresh thread, because threads are super sensitive to initial conditions.
Re: What color is your function? (2015)
#5What Color Is Your Function? (2015) - https://news.ycombinator.com/item?id=23218782 - May 2020 (85 comments)
What Color is Your Function? (2015) - https://news.ycombinator.com/item?id=16732948 - April 2018 (45 comments)
What Color Is Your Function? - https://news.ycombinator.com/item?id=8984648 - Feb 2015 (143 comments)
What Color Is Your Function? - https://news.ycombinator.com/item?id=8982494 - Feb 2015 (3 comments)
Re: What color is your function? (2015)
#6Re: What color is your function? (2015)
#7Re: What color is your function? (2015)
#8Nitpick aside, I have got to the point where I care little! Every language has its boilerplatish things, be it Elm’s JSON parsing, GO’s “if (err != nil)” or Haskells myriad language extension declarations. I don’t think asyncs on a chain of functions, or converting a callback function into a promise based one is that bad.
Re: What color is your function? (2015)
#9Re: What color is your function? (2015)
#10You can call an async from a non async function of course. You just can’t return it’s result synchronously. Nitpick aside, I have got to the point where I care little! Every language has its boilerplatish things, be it Elm’s JSON parsing, GO’s “if (err != nil)” or Haskells myriad language extension declarations. I don’t think asyncs on a chain of functions, or converting a callback function into a promise based one i…