No, lack of semantics lets you choose your own semantics. Like untyped languages let you choose your own type system.
-
-
I read it, this is just the kind of hole that gets dug when code makes class-global decisions, as is often the case in Ruby.
-
it can be configured per instance. The person didn't want that. Configuring json per stringify is hardly simple.
-
it's not the encoding's fault that the library works this way
-
the library has to choose something and there's no good answer. No good default argues against "trivial xform to many langs"
-
sure, the real answer to that original problem is to have a library that understands the domain. No different than with XML.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.