Timeline for Functional programming pattern for async JavaScript code
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 12, 2014 at 19:08 | vote | accept | zumalifeguard | ||
| Nov 12, 2014 at 18:55 | comment | added | Karl Bielefeldt | Yeah, I think that's the main difficulty with programming. The most elegant solution is only obvious after you've seen it. Anyway, posting on a blog is a great way to gather comments along the line of, "You idiot, everyone knows to do that you use x function from y library." :-) | |
| Nov 12, 2014 at 18:44 | comment | added | zumalifeguard | I'll probably just post this solution on my blog or something. Thanks for your response. | |
| Nov 12, 2014 at 18:44 | comment | added | zumalifeguard | That's a really good point. But you know as I was reading what you're wrote there with regard to the effort involved in implementing it, it occurred to me that it really isn't at all about the effort to do it but more about knowing that it needs to be done. For instance, if I pick up a new programming language and it didn't support, say, strings, I would end up composing something over time that ends up looking what we know as strings today. But for someone who is not really sharp on async programming, may not think of something like that. | |
| Nov 12, 2014 at 18:31 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |