[iends]

If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim?

To start with:

1. Label your axis, that graph doesn't say anything.

2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.

[skyraider]

In context, the graph is intended to show the dominance of REST over time and not how it's losing out to any of the other items.

[iends]

If that's the case, then his paragraph after the graph is not backed up with any data.

Instead, to me, it seems like he's trying to justify that statement with a poor microsoft office graph.

[skyraider]

The graph shows old techs that currently serve as more-or-less substitute goods for REST. He's saying the four items listed below have a much smaller or even tiny but, as of recently, nonzero following.

[JanezStupar]

What the fuck is JavaScript thing doing in there then?

[tim333]

I was puzzled briefly as to what JavaScript was doing there but thinking about it I've been doing some stuff with google maps and the API for that is mostly done with JavaScript objects.

[skyraider]

Probably talking about JSON and similar formats like JSON API.

[masklinn]

Which makes very little sense, since JSON is a content type it's mostly orthogonal to using REST, *RPC or whatever. You can do REST with JSON, XML, custom binary or ad-hoc textual payloads, and you can do RPC with exactly the same.

[skyraider]

Sure. Another way to interpret "JavaScript" is that it means using one of the various data-binding frameworks. But who knows, I didn't write the article.

[AlexanderDhoore]

Relevant xkcd: http://xkcd.com/833/