antrix

Try the book, "Seven Languages in Seven Weeks" which covers Clojure, Scala and a bunch of other languages. I've only just got it and it looks good so far.

http://www.amazon.com/Seven-Languages-Weeks-Programming-Prog...

"They basically want to outsource their OS development."

So ship stock Android, thus outsourcing OS development to Google. I agree with what SwellJoe says, haven't heard any credible explanation of how WP7 allows differentiation that Android wouldn't.

On Android, the device specific password is used for your phone's Google Account. Which means once you set it up, all Google apps like Gmail, GReader, Talk, Market, etc. will work as usual.

If you suspect your device password is compromised, you can revoke it from your Google account settings in a regular browser.

On the other hand, the Android GMail app is so good that there's no reason to use the web version. So just setup your phone with a device specific password and you are good to go!

Correct. Google can fix the stock launcher in one of two ways: retain the old layout and just fix the bugs which prevent usage right now or come up with something new. Since the focus of Honeycomb is tablets, I am guessing they'll go with the former option.

It'll scale down just fine. Tablet size devices will see the new launcher layout. Phones will most likely see the current (Gingerbread) launcher layout. Check these screenshots of the Honeycomb SDK booting into a Nexus1 size emulator: http://forum.xda-developers.com/showpost.php?p=10942783&...

I do something similar for my resume (http://antrix.net/resume/). Started with a template by timbray [1] which I 'imported' into Google Docs by directly editing the document CSS & HTML. Finally, export from Google Docs as doc, pdf, etc.

The HTML version on my site has additional print specific CSS to switch fonts, background colour, etc. making the print output more pleasing.

[1]: http://www.tbray.org/ongoing/When/200x/2005/11/12/Template.h...

I've been running oohEmbed.com, a similar service, for more than two years now. The problem with doing this in client-side JS is that (a) the oEmbed spec doesn't specify json callbacks so oembed providers don't support callbacks making async stuff in the browser difficult; (b) dealing with SOAP APIs, html parsing, etc. are difficult to say the least within browsers.

But if you really want to do this without relying on an external service, you can take the oohEmbed.com source (BSD licensed) and run it as your own 'private' Google App Engine app. oohEmbed.com itself is App Engine hosted.

> I gather Google's phone OS have something similar

Android apps are written in Java. So the standard approach for doing this is to use Java's weak & soft references which basically tell the GC that, "hey, I've used this memory but if you really need it back, you can have it!".

http://developer.android.com/reference/java/lang/ref/SoftRef...