The last big poll (the one about hiding comment scores) had about ~4500 votes, IIRC. Everybody who voted is probably somewhat active on here; and I'd guess that most active users voted.
It's probably best to get yourself some books. The online documentation for both Asterisk and FreeSWITCH is shit, the IRC channels are mostly useless unless you already know a lot and the configuration files are just plain weird (Asterisk uses ini-style files with embedded programming, FreeSWITCH's configuration format pretends to be XML (which it certainly isn't)). Asterisk also has severe performance problems and AFAIR has some extremely bad code.
The entire idea with Plivo (much like Twilio and Tropo) is to simplify i.e. let web developers build telephony apps without having to learn much about a telephony engine.
And I'm just coming back to this thread because I learned something today. There are no flights from Singapore to JFK, but there is one to Newark. It's the longest scheduled air route in the world, at 18 hours and 40 minutes.
Oh, and it's in a 100-seat all-business-class A340-500. I'm guessing they couldn't do it with a fully-laden economy section. Then again I'd hate to fly 19 hours nonstop in economy.
US wars since the last decade have killed close to a million people, most of them civilians. This just cannot be justifiable. Or are you suggesting that the live of an American is far more valuable than the live of an Arab?
Of course it is justifiable. The 9/11 attack was spectacular, something which a writer could imagine in fiction. That act stole peace from the world. The following invasion of Afghanistan had and still has almost unanimous support. It also was a direct response to 9/11. So one can say, it was Bin Laden who really killed those civilians both in America and Afghanistan.
The eval throwing away context does not make any sense in retrospect. I think I made it that way because of some ghetto-scoping ideas.
You broke car and cdr somehow (these don't evaluate their arguments anymore), but I have no idea how you did this.
This was mostly a training exercise, this is why there is no significant use of monads in there: I simply haven't learned enough about them to feel comfortable using them.
Sorry, that was my fault. I didn't make lambdas evaluate their arguments and I didn't notice this in my code. I.e. car/cdr work correctly, fun doesn't.
(a) The empty list is treated as nil. (b) The scoping is in fact strange; what you saw, however, was a bug. (c) cons expects a list as its second argument.
This certainly isn't useable for anything, but I think it comes somewhat close to being lisp.
So it's really 6-12 hours. You're working on the code in the background; you probably couldn't just have written it three hours straight. Or more likely, you were sorting out the details within the 12-hour period but you had been toying around with the idea for days if not weeks.
Just guessing and certainly not trying to look down your work, it's beautiful. It's beautiful even if it had taken a week to write. The time to write it is just interesting because it is exactly this that makes programming hard to measure.
How does any explain his productivity to a boss if you get seemingly nothing done for four days and then write a nearly complete solution on the fifth day? How much is one actually working after all, counting all the time that affects the work? Does it count as work if you go biking on a Saturday but you kind of subconsciously think about your work and then you write great stuff on Monday, thanks to that?
One thing is for sure: you're much better off measuring a programmer's efforts by his accomplishments instead of the time to do them. This is backed up by the fact that an entrepreneur programmer gets rewarded much more fairly than a salaried programmer.
