JSON VS Eno

JSON mentions (13)

• The Last Breaking Change | JSON Schema Blog

  The YAML 0.1 spec was sent to a public user group in May 2001. JSON was named in a State Software internal discussion. State Software was founded in March 2001. json.org was launched in 2002. Therefore you’re just wrong: YAML came out before JSON. Source: about 1 year ago

• Why does wine give warnings about using 64bit prefixes, or has 32bit packages? Hasn't the world moved on from 32 bit a century ago?

  How come that doesn't apply to other libraries? For example, when I write Java or Node.js programs, I don't need to make sure packages like json.org or express.js have a 32bit or 64bit environment. What makes windows libs different than NPM libs? Source: over 1 year ago

• “Ignore the f'ing haters ” And other lessons learned from creating a popular

  The first two sentences of the text on http://json.org are "JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write." It's a primary goal of JSON, it's fair to question whether it's successful at it. Personally, I'd much rather write TOML or S expressions. I don't like YAML at all, the whitespace sensitivity drives me nuts. - Source: Hacker News / over 1 year ago

• Recording your JSON data to MCAP, a file format that support multiple serialization formats

  To help you make the transition, we’ve written a tutorial on how to write an MCAP writer in Python to record JSON data to an MCAP file. Source: over 1 year ago

• replace \" with "

  What you need to probably do is to step back and learn the format for JSON, and the core data structures that you will find in most languages:. Source: almost 2 years ago

Eno mentions (0)