3 ms·

Maybe the author started this project some years ago, before parsing and network libraries were common? Because if you don't have libraries, he's right. Starti

• nkassis 12y ago
  It would have to be extremely old for that to be true. All the problems he mentioned have had some form of solution for decades. Some uses cases needed significant changes in those solutions (ex: need for NoSQL DBs) but most development have stayed in a zone where the available patterns existed for the things he mentioned.
  • jakub_h 12y ago
    Perhaps, but the "solutions", when put together in a single project, probably resemble the "30 quicksorts in a single binary" syndrome. Lots of code doing conceptually the same things.
  • hyperpallium 12y ago
    hmm, JSON is only a decade and a half old, so not "decades" for that particular one. And it's only really taken off within the last few years. You're right about it being conceptually solved for many decades, but we here developers like to reinvent everything every decade or so. For example, back when XML was gaining in popularity, around 2000, there were new parsers/serializing libraries launched all over the place - even standards like SAX and DOM. Many people rolled their own; many had to.
    • groby_b 12y ago
      It's not like JSON is the first serialization format ever. (I still have XDR & CDR nightmares, and that was the early 90's) So, yes, decades. Not necessarily solved well, but yes, people shipped data over the network before JS ;)