No, lack of semantics lets you choose your own semantics. Like untyped languages let you choose your own type system.
-
-
Replying to @samth
works fine until GitHub chooses it's semantics and "simple" Ember code has to decide what to do with it.
1 reply 0 retweets 0 likes -
JSON is used in public APIs with general purpose clients.
2 replies 0 retweets 1 like -
-
But it's the API that doesn't specify the semantics, not JSON. They were just pretending that JSON did the job for them.
1 reply 0 retweets 0 likes -
-
Replying to @wycats
But doing it in XML wouldn't help. Number encoding issues don't go away when you pretend numbers don't exist.
2 replies 0 retweets 4 likes -
-
-
Replying to @wycats
Cross system number encoding issues are hard. But this wouldn't be easier in XML.
1 reply 0 retweets 1 like
Replying to @samth
you just have to define precision or specify bignum. In the absence of a definition, people have to be defensive, but ad-hoc
10:23 PM - 26 Oct 2016
0 replies
0 retweets
0 likes
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.