jodoglevy
Joined 14 years ago
Karma
244
Submissions
39
Member since
May 18
Recent submissions
Comment · 1 year ago
Comment · 4 years ago
> The average crypto user isn't aware that the blockchain can reject transactions, and we'll keep it that way.
Legends
Comment · 9 years ago
Seems like a great way to check confident ladder climbers, who have no idea how to actually grow a product.
Comment · 10 years ago
I recently joined this team from Azure. Lots of senior AWS and Joyent folks here as well. Send me a mail at joe dot levy at oracle dot com and I can connect you with the right folks. Same goes for anyone else interested!
Comment · 12 years ago
OP here.
I did a post comparing Gargl to Kimono actually: http://jodoglevy.com/jobloglevy/?p=146
Comment · 12 years ago
OP here.
Yes, using the generated API is the issue, not generating one.
As for authenticated sites, as long as the underlying generated module keeps track of cookies received in responses and sends those cookies on subsequent API calls, just like a browser would, it should work fine for "normal" websites that use regular cookies for remembering if user is logged in. Gargl modules generated as PowerShell, or as Javascript (and used in a WinJS project) do this "cookie remembering" today. It could also of course be possible for the user to remember the cookie themselves in their code (after it gets the raw response from the API call), and then pass that cookie into any subsequent API calls manually.
Comment · 13 years ago
Very cool, but why come up with a new API schema rather than use an open standard like OData (http://www.odata.org/)? Then Alpaca would be compatible with a bunch of APIs that already exist today. In fact, something like this (generating client libraries from APIs) may exist for OData already, but if it does, I've only seen it for .NET and OData (Visual Studio 'Add Service Reference').
This is actually pretty similar to a side project I've been working on called Gargl (Generic API Recorder and Generator Lite) (https://github.com/jodoglevy/gargl). Haven't gotten around to doing a Show HN post yet, but would love any feedback or to combine efforts. Basically it lets you generate an API for websites that don't have APIs publically available, by looking at how a web page / form submission of that web site interacts with the web server. You record web requests you make while normally browsing a website via a chrome extension, parameterize them as needed, and then output your "API" to a template file. Then this template file can be converted to a client library in a programming language of your choosing.
Very cool idea, and seems very flushed out already! Best of luck, and I will let all my friends who complain about unfair working conditions know about this!