News for hackers. Stuff that matters.
Re:Why did OKCupid write their own web server? by cheez on Thursday March 10, 2011 @01:17PM (#2310075)
I've had an opportunity to chat with some people tangentially related to OKC and I think that they have definitely done some very cool stuff. There are some things that the OKWS architecture does very well. As I understand it, there is a bit of "Rails envy" but they seem to copy good ideas very quickly. That being said, I think that if they were to start again, they would try and use commodity technology.

But, these guys are really fucking brilliant and productive. Immensely... I feel like a chump in comparison.

Re:Why did OKCupid write their own web server? by cschep on Thursday March 10, 2011 @01:24PM (#2310096)
Yes. How often do I say, "I wish this thing ____" or.. "oh that's just not possible." They just decided to write a bunch of c++ to make it possible. Awesome!
Re:Why did OKCupid write their own web server? by rubashov on Thursday March 10, 2011 @09:17PM (#2311854)
Well these days writing an http server in C++ is about 30 lines of code using POCO or boost.asio. If your business model was "serve a shit-ton of dynamic requests super cheap" it might make just as much sense as ever to build the whole thing in C++ embedded directly in a C++ webserver.
Re:Why did OKCupid write their own web server? by cheez on Thursday March 10, 2011 @11:29PM (#2312118)
If only writing a web app was that simple. ASIO is simply a socket library.
Re:Why did OKCupid write their own web server? by rubashov on Thursday March 10, 2011 @11:43PM (#2312152)
It comes with an http server implementation. POCO has a more full featured one.
Re:Why did OKCupid write their own web server? by cheez on Friday March 11, 2011 @10:00PM (#2315841)
It does? Wow, I haven't looked at it in a while then... Can you point me to a link?