3 ms·
> Of course, writing a JSON parser should take less than a day, so the cost is essentially negligible. Writing a JSON parser that parses my examples correctly
by dllthomas 14y ago
> Of course, writing a JSON parser should take less than a day, so the cost is essentially negligible.
Writing a JSON parser that parses my examples correctly is a couple hours at most, yes. Writing a JSON parser that I am confident is correct and robust and efficient takes somewhat longer.
- ams6110 14y agoIt's really more of a case of porting a JSON parser because many working examples of JSON parsers already exist, as do complete sets of test data that your parser must be able to handle. There's really not a lot of original thought that has to go into recreating something that's already well-established elsewhere.
- dllthomas 14y agoFair point. There can still be a lot of work to ensure robustness and efficiency in the new setting (especially so if the execution model is particularly different).
- jfoutz 14y agoHaskell, and BoS, i think, are both special cases. First, Haskell is actually pretty old. There are changes, of course, but the core language is '98. IIRC, Brian O'Sullivan wrote a high performance parsing library, attoparsec. In general, I think i agree with the article. In this specific case, it's a fantastic example of leveraging your strengths to do something amazing.