3 ms·
Qwerly API Review
- Klonoar 15y agoSo this is kinda cool... I guess? Eh, I'll be honest, this is just a bit out there to me. Facebook/Twitter/etc all offer different types of data; if you really see this space as maturing, you'd realize this and not write an API that tries to be an end-all-be-all. I'd never want to use an API like this either, since I'm essentially lumped in with the usage rates of everyone else (or butt up against the alternative, which is to deal with them not having real-time data - what's the point of that?).
- Someone 15y agoOther reasons why one would be wary of using something like this: - you are designing in a man-in-the-middle. - you are adding another server round-trip (=latency) As a
- Someone 15y agoOther reasons why one would be wary of using something like this: - you are designing in a man-in-the-middle. - you are adding another server round-trip (=latency). As a library, this might be useful. As a service, it, IMO, would need to add more than combining APIs.
- hugh3 15y agoQwerly is surprisingly difficult to type.
- daviddoran 15y ago@apievangelist: I'm not sure if there's something temporarily wrong, but most of the links in the article go to empty holding pages, and there's very little Qwerly-related info.