All your base belong to CWD

Google App Engine

So Iv’e gotten a few minutes to mess around with the Google App Engine for Java. so far my thoughts are as thus:

• it’s very cool but there is ALOT of room for improvement though
• I like their free quota/billed model
• I like how easy it is to build local and deploy via the eclipse plugin. the less I have to leave my unified IDE to build and deploy, the better.
• the datastore is pretty powerfull in its ability to directly push your application’s object model into it (thanks JDO!)
• there needs to be a serious increase in supported JDO features. The fact that there is no OR operator in GQL is ridiculous
• there also needs to be some tools built for direct data access. right now it all has to be done programatically for the most part (can’t seem to get the dashboard data view to work)
• I haven’t played with any of the built in services yet like memcache or the image rendering service. that should be really cool
• mashing with the GWT was a clever move on their part and I will now be forced to (finally) pay attention to it and learn it.
• I love the idea of building rapidly scalable apps that will work on a pay-as-you-go model. this is especially cool if I ever get around to working with my buddy Carmen’s Tiny FB Java Taglib
  

that’s all I got for now

-CWD

Chrome

So everyone is going nuts for Google Chrome right now. Like everything else, I refuse to download it until at least a 2nd iteration.

I’ve 1 reason to like Chrome and number of reasons not
let’s start with the nots
1) it’s webkit. I mean come on…. srsly…. come on….
2) ok, processes for each tab? not to give IE props but IE had separate processes for windows (before tabs were popular) back in IE5. No one seemed to think that was novel, especially bc it killed interwindow communication with things like javascript.
3) despite their separating the tabs into silo’d processes they STILL haven’t really solved the plugins behaving badly problem… maybe bc native plugins are a bad idea? hmmmm
4) a VM for Javascript? FTW? how about this? how about we add closures to the next version of Java and just FIX THE APPLET CONTAINER? add some DOM access though the container and your gold
5) and one more gripe: another browser to test my sites against. swell

now the 1 reason I like what they’re doing. I like the grand concept.

When I was at goog IO back in May they basically said “we need to get the browser to the next level”
this is what they’re doing. the current state of the browser doesn’t do enough for us (or them with their grand plan) and is really stuck back in 1998 for the most part

Google’s over arching plan is almost like that of MS. They want to do it all. The diff is that they’re embracing opensource.

They have
-a mobile plan, though its not quite there yet
-an OS
-an offline plan with gears
-best way to find stuff on the web. to “google” is a verb now
-best in breed apps via the web (gMail, docs, calendar, gTalk, etc)
-a place to run your websites, scalably with App Engine
-ecom for your web site with Check Out
-out of the box analytics for your web site
-a way to generate ad revenue with your site
-a way to advertise your site -a place to build you web site (and more) with the code repository
…
so what’s missing???
a browser to USE ALL THOSE SERVICES!!!

and thus you have the impetus for Chrome…..

though I’m still not impressed with it…

Tweets

Android