Sorry, I meant /this/ spying incident. The minster of the interior already said that the documents didn't really have anything important in it. The guys received ~$25k for the documents. It's not a huge deal actually. It was very very stupid of the American to do this and if I were Obama I'd be mad at the NSA. Why? Because the risk was big but the reward was tiny. You didn't gain much from the documents, yet you now have another huge dent in your relations (again!) and it's starting to piss of German politians & Germans.
America doesn't realize it fully yet, but it's making itself very unpopular in the last 5 years and this will be a huge problem in the future when all that's left is UK, Mexico & Canada (Maybe India) as your friends.
HN/TC/... are good to show a new product to people that want to see new products. Thats it.
That did not mean that you get customers or a wider audience.
One year ago i launch http://apidocjs.com (OpenSource for RESTful API documentation), i show it to HN and got 2.500 Visitors in one day (yeah!), but the next days nearly zero.
Further development and step by step more users find their way to apiDoc -> organic growth.
API's are great, but they are not the end of development.
While i develop several projects and write OpenSource apiDoc (http://apidocjs.com) i see the advantages of API's like you did it.
Clean way of development and access, but on the other side some double work on frontend and backend (for own Applications).
Iam excited of the next evolution step of API's or what will be used after API's.
Nice little library. I think i will have a close look and implement it into apiDoc (http://apidocjs.com) Templates - for now i use crude jQuery events (quick & dirty coded).
With Ractive i think i can make the code cleaner and easier to modify.
At the moment i prefer Backbone in my other projects, but it is to "heavy" for a small single page (especially for users that did not know backbone and want to modify the templates).
All blogs and howtos only describe the change of API Access with new versions, but not how to handle different backend data versions.
One way is to use the newest version in Client and the Server has to convert old Data to new Data, then deliver to Client. But sometimes it not so easy, depend on complexity of your data.
Other way: convert all Data to new Version and change Data-Access in the old Api Version (but here is the Problem with: never change a running system, things that work before could go wrong). And if you have a huge site with many users, it is not possibly to interrupt the service.
To maintain many versions is for a short period ok, but for longer usage not practicable.
Design is nice, but "baaaam" too much for what the page is and for who the page is. Why i have to click to open the services? Better show them directly.
Hope some people write here some alternatives, i always watch for good tools too. Most of the documentation tools document the code itself (like JSDoc), but i did not found many for RESTful Api documentation, thats why i start the project :)
One such tool is Swagger [1]. The nice thing about it is that it can automatically write you a client as well. There are client implementations for many programming languages, such as Java, Scala, Clojure, Ruby, Python, PHP, Javascript and C#.
