3 ms·
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.
by skyraider 13y ago
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 13y agoIf 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 13y agoThe 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 13y agoWhat the fuck is JavaScript thing doing in there then?
- tim333 13y agoI 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 13y agoProbably talking about JSON and similar formats like JSON API.
- masklinn 13y agoWhich 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 13y agoSure. 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.