The early narrative was that it was the dispatcher's fault because she didn't relay the message (from the original caller) that the gun was probably fake. I've seen the video, it looks like he tried to pull on the cop, but the video is grainy. I'm no officer but I'm not sure why they decided to pull so damn close to him when they knew he may have had a weapon. The kid was pointing the gun at people - clearly he didn't deserve to be shot, but talking about him like he was some innocent babe laying in the sandbox is dumb. All three of these incidents in the last few months have had very big gray areas. The NYC choke out was by far the worst, IMHO. But, none of these compare to the DJ Henry case from a few years back.

I have been developing for the web since 2002, but I have only been doing Python for the last few years, the "mod_python is dead" phase. In fact with the first site that I launched in python, I was starting to setup a beta environment with mod_python when my boss told me not to use it. Looking forward to reading up on the new release.

Why not just use the webserver as a proxy to gunicorn or uwsgi?

Are you suggesting that a webserver is best used as a proxy, or that gunicorn and uwsgi are not webservers?

I don't think he was suggesting either. In the suggested setup, the webserver can still be used as a webserver, giving you the power of years of development into security, modules, etc, while proxying through certain requests requiring custom application work - which passes to your local webserver. Neither is what I'd consider the primary role of the application, though.

I'm not sure about uWSGI, but Gunicorn's default worker was designed to be behind a proxy that buffers slow clients.

Is there some low level checking by the js engine to see if it should stop processing the function if there is no return? Or, to put it another way, does adding the return explicitly tell the engine, "ok we're done here", as opposed to a small amount of processing required by the engine to determine that for itself?

How usefully useless

Was very good, reminds me of that old Asimov story - the Multivac one.

Hank Scorpio: Uh, hi, Homer. What can I do for you? Homer: Sir, I need to know where I can get some business hammocks. Hank Scorpio: Hammocks? My goodness, what an idea. Why didn't I think of that? Hammocks! Homer, there's four places. There's the Hammock Hut, that's on third. Homer: Uh-huh. Hank Scorpio: There's Hammocks-R-Us, that's on third too. You got Put-Your-Butt-There. Homer: Mm-Hmm. Hank Scorpio: That's on third. Swing Low, Sweet Chariot... Matter of fact, they're all in the same complex; it's the hammock complex on third. Homer: Oh, the hammock district! Hank Scorpio: That's right.

The fact of the matter is, this kid will be dealing with legacy type issues over the next 40-45 years of his career. 10 years from now, devs will be grumbling about supporting some technology we view as common place and whiz-bang today.

Yes, supporting IE6 is a pain in the ass (I have to do it due to my company's huge Chinese user base). But I am watching it die a slow death.

The specific experience sucks, but in general it will help him prepare for realities of web dev.

In his defense, Fabric is not django specific.Though it is pretty nice.

Honestly, as a freelancer, if you want to keep your domains and email on GD, that is fine with me. Their shared hosting is so inexcusably slow and difficult to manage,it makes me wonder why there hasn't been a class action lawsuit against them. Hyperbole, I know, but they suck at hosting! IF a potential client has space up there, the first thing I do is have them move it.