> Oh, and as an aside, if one page of PHP is your web programming experience, then you really should probably not be shipping an HTTP server.
I disagree. How are webprogramming skills applicable to writing a HTTP server? Seems to me the relevant skill would be network programming and my (admittedly limited) web developing experience leads me to believe the skills are mostly if not completely disjoint...
Yeah, that's absolutely true, so I overstated my case somewhat on that point (although in my defence I did say "probably"). So, in place of the mis-stated claim in my original comment, let me try that part again.
Writing robust high-load network servers is actually a little tougher than it seems, and the skillset has very little overlap with the "designing a nice language" skillset, or the "making an efficient compiler" skillset. And not only is robustness is important, but to be useful it probably needs a lot of auxiliary features like HTTPS and authentication and logging and FSM-knows-what-all (this point, on which features matter, is the only place that web-programming experience might actually be relevant). And so tacking a half-assed HTTP server onto your new-language project is, well, half-assed. And IMO, there are enough shitty toy web-servers out there already.
I disagree. How are webprogramming skills applicable to writing a HTTP server? Seems to me the relevant skill would be network programming and my (admittedly limited) web developing experience leads me to believe the skills are mostly if not completely disjoint...