[Haskell-cafe] Slow Text.JSON parser

[Don Stewart]

utf8-string allows one to decode utf8 from bytestrings. It was built so
that we could decode utf8 strings at work from bytestrings :)

    http://hackage.haskell.org/packages/archive/utf8-string/0.3.3/doc/html/Data-ByteString-UTF8.html

Enjoy! Libraries win every day of the week.

-- Don

sjoerd:
> JSON is a UNICODE format, like any modern format is today. ByteStrings  
> are not going to work.
> 
> If everybody starts yelling "ByteString" every time String performance  
> is an issue, I don't see how Haskell is ever going to be a "real world  
> programming language".
> 
> On Jan 13, 2009, at 4:00 PM, Don Stewart wrote:
> 
> >ketil:
> >>"Levi Greenspan" <greenspan.levi at googlemail.com> writes:
> >>
> >>>Now I wonder why Text.JSON is so slow in comparison and what can be
> >>>done about it. Any ideas? Or is the test case invalid?
> >>
> >>I haven't used JSON, but at first glance, I'd blame String IO.  Can't
> >>you decode from ByteString?
> >>
> >
> >Text.JSON was never optimised for performance. It was designed for  
> >small
> >JSON objects. For things above 1M I'd suggest using Data.Binary (or a
> >quick JSON encoding over bytestrings). Shouldn't be too hard to  
> >prepare.
> >
> >-- Don
> >_______________________________________________
> >Haskell-Cafe mailing list
> >Haskell-Cafe at haskell.org
> >http://www.haskell.org/mailman/listinfo/haskell-cafe
> 
> --
> Sjoerd Visscher
> sjoerd at w3future.com
> 
> 
> 
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe