Archives / 2009 / May
  • Json.NET @ Twitter

    Undoubtedly I’m 6 months behind the times but I just discovered Twitter search. It is rather nifty being able to search public conversations in real time and I begin to see now why Google is interested in them.

    The nice thing about Json.NET having a unique name is that it makes it very easy to search for.

  • Woooo

    What a day, eh, Milhouse? The sun is out, birds are singing, bees are trying to have sex with them -- as is my understanding...

    A cool milestone. Not as elite as this one but a good deal more round: Fifty thousand Json.NET downloads since hosting on CodePlex a year and a half ago.

    Json.NET CodePlex Stats

  • Best. Serializer. Ever.

    Last night's 'Itchy and Scratchy Show' was, without a doubt, the worst episode ever. Rest assured, I was on the internet within minutes, registering my disgust throughout the world. I have really enjoyed some of the discussion on the Json.NET CodePlex forum recently. Lots of people have posed interesting scenarios and it has been fun coming up with solutions that makes Json.NET a better tool for everyone.

    With practically every request these days being something around serialization I have set a goal: make Json.NET the best serializer for .NET

    See that underline? That just happened. No pressure, no diamonds folks.

    Ideas Wanted

    I think the JsonSerializer is most of the way there already but I know there are places where it could do better.

    What I’m most interested in are:

    • What it is missing compared the old XmlSerializer and new DataContractSerializer (FYI I just added tracking object references)
    • What common scenarios it handles poorly
    • What popular frameworks it has trouble with
    • Anything that is already there but you think is stupid and dumb
    • General ideas or suggestions
    • Useful JsonConverters you might have written that would be worth including for everyone

    Most ideas come from you guys (I have no imagination) and all feedback is welcome.

  • Json.NET Beta versus Final

    Now I don't want you to worry, class. These tests will have no effect on your grades. They merely determine your future social status and financial success... Some Json.NET users have asked me whether it is ok to use Json.NET while it is in beta, or have asked if the a final version will be released soon because they need a recently added feature and their employer has a policy against beta software.

    For Json.NET the only difference between beta and final is completed documentation.

    Json.NET’s testing is completely automated. Approaching 400 unit tests and 90% code coverage (not 100% but good enough) they are the beginning and the end of Json.NET’s test policy. A final release is no different to beta or even a regular source code check-in when it comes to stability.

    I think one regression over 3 years and many releases is doing pretty well [:)]