If you’re curious

Lots of work done over the past week:

- I did float my own revenue project, and it got a favorable reception. Hopefully I’ll be able to unveil the plan sometime over the next few months, lest anyone think I’m just talking here.

- Rolled out a Suns Draft History in record time. I’d been working on a bell and whistle-laden version to compare NFL draftees from ASU and U of A. It was slated for August. Then someone said, “Hey there’s an NBA draft coming up, can we do something for that?” Two days later, voila.

- Wrestled with Caspio. Tried to make a Google map using instructions on site. Here’s what I got:

Caspio FAIL.

-Threw up some working Caspio nonsense, including University salaries, Gas pump violations (again. It’s always in season!) and Executive Pay. Keep an eye on those, as existing non-Caspio templates will be replacing many of them as they are approved.

My conclusion on Caspio is that they do one thing very well. But other, cheaper alternatives do it just as well. Further, to learn to make it do otherwise seems pointless, especially seeing as we would be paying for the luxury of learning to hack it.

And this is just an outright lie. It’s not even as powerful as old faithful, MySQL and PHP.

UPDATE: Wouldja lookit that! ASU salares is already free of its Caspio chains!

This entry was posted on Saturday, June 28th, 2008 at 11:21 am and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Comments so far

  1. Guess what?
    Bet you’re not surprised… but my Caspio - Google mashup didn’t work either. Maybe it’s my fault, but I’m blaming it on Caspio.
    hehe.

  2. They’re a fun scapegoat.

    I was late buying my wife’s birthday present on Monday. Caspio’s fault.

  3. [...] Other, smarter people have invested a goodly amount of space to explaining Caspio’s deficiencies, so I’ll leave that to the links. Instead let’s break out below a couple tricks that helped me at least marginally improve today’s product, in hopes they might be useful to somebody. (Though I suppose any “improvement” is a matter of opinion! Let me know what I fucked up.) [...]

Have your say

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.