The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Never heard of it. Can't see the point of it (mind you I only spent 2 mins on the website) and anything which talks about 'The Application Programming eXperience, or APX' should probably be mercilessly destroyed! My APX is going bad-to-average today by the way, how's yours?
I've done a little bit of REST and I thought the idea of it was to simplify things. SOAP was too complicated (it is actually), and this was the answer. Now they want to create a whole new meta-language on top of it?
Well, there's another one I've not heard of. While some parts of it look quite promising, it looks to be a bit overkill to me. My RESTful APIs, nowadays, tend to be a node.js express application picking up the requests and handling them. It's very easy to use. For a moment, I was prepared to be impressed by this but I realised that the versioning they were talking about had absolutely nothing to do with API versioning - which would have been something I would be very interested in.
What do you see as the advantage to REST vs. something like SOAP? Mind you, from what I've been reading, REST is an architecture and SOAP is a protocol, so I think it's a bit like comparing apples and oranges.
But from what I've been reading regarding REST, I just don't get it. Looks like nothing more than HTTP get/post commands.
That's pretty much what it is, HTTP commands; but don't forget UPDATE and DELETE commands. I like being able to quickly test my APIs through CURL. Yes, SOAP gives you the object wrapping that you don't really get with REST, but REST provides a simpler, more ubiquitous architecture.
(Don't fool yourself, XML in .NET is leaps and bounds ahead of the rest)