News for hackers. Stuff that matters.
Re:The architecture of Stack Overflow [video] by skittles on Monday January 13, 2014 @06:26PM (#7054313)
He mentioned that they use the servicestack.text library. I've looked into servicestack recently (using the nuget packages), but then found the library to be pay-to-play. There's an older version (v3) that is BSD licensed that is being maintained. Do any of you have experience with it? I have grown tired of Microsoft pushing new solutions to the same problem (REST service with WCF and then Asp.net web api).
Re:The architecture of Stack Overflow [video] by sklivvz1971 on Monday January 13, 2014 @06:32PM (#7054355)
We used it at the time I gave that talk, we don't anymore. We only used JSON serialization and we have rolled out our own free solution, Jil.

https://github.com/kevin-montrose/Jil

Re:The architecture of Stack Overflow [video] by kmontrose on Monday January 13, 2014 @06:47PM (#7054423)
Technically we use Newtonsoft and Jil, Jil replacing Newtonsoft as we become increasingly confident in it.

I wouldn't suggest anyone use Jil in a production role unless you're at Stack Overflow. It's too untested at the moment, and the typical person can't get me on the horn to fix whatever just broke.

Re:The architecture of Stack Overflow [video] by guiomie on Monday January 13, 2014 @08:04PM (#7054706)
Why would I use Jil over Newtosoft ?
Re:The architecture of Stack Overflow [video] by JasonPunyon on Monday January 13, 2014 @08:41PM (#7054836)
You wouldn't right now (Kevin doesn't recommend it). But in the end it you'll want to use it if JSON serialization is a performance bottleneck for you.
Re:The architecture of Stack Overflow [video] by dan_b on Tuesday January 14, 2014 @07:06AM (#7056551)
ServiceStack is just plain awesome when it comes to developing web services, though it's gone commercial for v4 onward. Nancy is another popular alternative - it's basically Sinatra for .Net. Every time I go back to WCF I want to stab myself in the face.