Skip to main content

How To Not Open Your API Enough

So, I didn't see any opening for contributing in any useful way to the discussion about Google's new Chart API, until I read this post. How dare they call this service open. They should have been clear that their greed has lead them to secretly hide abilities of the service from the public, in an obvious attempt to corner the market on really cool graphs in web sites.

My theory is that they hope everyone uses their "Open" Chart API, which doesn't include the full service's abilities, so that their own charts, using the entire breadth of charting power, are inherently better than yours. Beware the wickedness of the corporate greed, my friend.

My sarcasm drips onto the floor. Now, I mean no disrespect to Marty, but this kind of post really does get under my skin from time to time. Maybe it just struck me at the wrong time. So what if Google has features they didn't document? So what if they use a different URL to access the API? Maybe the undocumented features are still in flux. Maybe they like to see how many people outside Google are using the charts. There are plenty of good reasons for everything he talks about them doing with this and claims it to have some anti-open nature, but I just don't see any of it.

For Google's Motivations This Means...

None of it really matters, in the end. Use the API or don't, but I don't see a gain for them in the parts of the API they are letting us use, nor do I care if they do gain. Gaining from something doesn't negate your ability to do it for the reasons outside your gain. My job involves writing software for a company that helps low-income families find affordable housing. I get paid for my job, so does that mean I can't lay claim to any good nature behind it?
Labels:

Comments

Jeremy Cantrell said…
When I read Marty's post, I felt the same way. The lack of documentation for certain elements of their charting API does not indicate to me that google is trying to falsely portray themselves as "open". It simply tells me that there are parts of it that may or may not be finished to their satisfaction. I think we will likely see these (and other) features slowly trickle in to the documentation.
3:30 PM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...
Post a Comment
Read more