3 ms·

a new json api to be released 2016. Hopefully by that time json is still relevant. I know most likely it will but at the pace of change that tech has, im not be

a new json api to be released 2016. Hopefully by that time json is still relevant. I know most likely it will but at the pace of change that tech has, im not betting. is there any contender to json at the moment?

exelius 12y ago
We're talking Java here. Java is used by enterprises all over the world for mission-critical code. I have clients who are just now making the move to Java 7; so of course JSON will continue to be relevant for the next 10 years or more. It may fall out of favor among the Julia/Erlang/Scala crowd, but JSON is here to stay for enterprises. As far as contenders to JSON, I can't really think of any besides XML. The biggest benefit to JSON is its simplicity; which becomes a huge drawback in a strongly typed language like Java.
tonyhb 12y ago
I don't think we'll be looking at a contender to JSON for quite some time (at least, for frontend/web consumable APIs). Being able to use it in JS directly pretty much guarantees its stability. For other message protocols it's a different story. Each system has its own needs, so it's much harder to say.
Someone1234 12y ago
JSON likely will be around as it is extremely simple (technologically) and extremely light (in terms of network usage). In order for a JSON killer to appear it would inherently have to be superior to JSON, and it is very hard as for what JSON is used for it does very well indeed. JSON somewhat replaced XML, but that made sense since XML is more complex and a lot more expensive (both in terms of network AND processing). I can see people building more complex obstractions on top of JSON in the next for years (essentially re-building what XML was, but in JSON) however I cannot really see JSON being entirely dethroned for what it is good at.
justwannareply 12y ago
YAML (http://www.yaml.org http://www.yaml.org) comes to mind, though I think JSON is a much bigger improvement over XML than YAML is over JSON.
- azinman2 12y ago
  Yaml is more for humans to read than json is, and doesn't have native functions in any browser.
btgeekboy 12y ago
I'd much rather have this pace of innovation than trying to keep up with whatever the Ruby community decides to use this week.

exelius 12y ago

We're talking Java here. Java is used by enterprises all over the world for mission-critical code. I have clients who are just now making the move to Java 7; so of course JSON will continue to be relevant for the next 10 years or more. It may fall out of favor among the Julia/Erlang/Scala crowd, but JSON is here to stay for enterprises. As far as contenders to JSON, I can't really think of any besides XML. The biggest benefit to JSON is its simplicity; which becomes a huge drawback in a strongly typed language like Java.

tonyhb 12y ago

I don't think we'll be looking at a contender to JSON for quite some time (at least, for frontend/web consumable APIs). Being able to use it in JS directly pretty much guarantees its stability. For other message protocols it's a different story. Each system has its own needs, so it's much harder to say.

Someone1234 12y ago

JSON likely will be around as it is extremely simple (technologically) and extremely light (in terms of network usage). In order for a JSON killer to appear it would inherently have to be superior to JSON, and it is very hard as for what JSON is used for it does very well indeed. JSON somewhat replaced XML, but that made sense since XML is more complex and a lot more expensive (both in terms of network AND processing). I can see people building more complex obstractions on top of JSON in the next for years (essentially re-building what XML was, but in JSON) however I cannot really see JSON being entirely dethroned for what it is good at.

justwannareply 12y ago

YAML (http://www.yaml.org http://www.yaml.org) comes to mind, though I think JSON is a much bigger improvement over XML than YAML is over JSON.

azinman2 12y ago
Yaml is more for humans to read than json is, and doesn't have native functions in any browser.

btgeekboy 12y ago

I'd much rather have this pace of innovation than trying to keep up with whatever the Ruby community decides to use this week.