Google's two new announcements: integrating a Twitter-like service into Gmail and a goal of a real-time speech translation service shows what direction they're taking the company: Into the space between you and every other human being on the planet.

To be fair, these two developments are really far apart in their delivery dates. The Gmail status update could come as soon as tomorrow, whereas the the speech-to-text-to-speech translation system is still a ways out. You can definitely see just how much work Google needs to do by trying to read your Google Voice voicemail transcriptions. (Voice search works better on Android 2.1 because you're talking slower and enunciating.) But both these features point in the same direction many of the company's other products have been hinting at. Here's a list of Google's major products, in case you forgot, and which sector of communication they want to dominate.

Google Voice: This is a big one, and it'll be the most natural interface for Google to slot in the voice-translation into. If you're using it the way Google wants you to use it, you're already piping all your voice calls and SMS through Google's tubes. And refining speech to text gives them a good idea of your interests and what you're talking about, allowing them to better serve up the relevant ads to you during calls.

Gmail: Having access to at least one end of everyone's email conversations, outside of business emails, gives Google the ability to be a gateway for most of your written communications. But that's not enough for Google, which is why they developed...

Google Wave: It's email, message boards, chat rooms and collaboration software all in one, except every participant needs a Google account. This closes that "openness" loophole that email has, and forces everyone into Google's biosphere. So this, and Gmail, should make sure that every medium-length communique passes through Google's maw for analysis. But what about shorter and longer forms? Update: Thanks commenters, for reminding me that Google made Wave open, so people can create their own Wave servers to talk to each other with the Wave protocol. The point still remains, that if you were going to use a service, wouldn't you rather use the service from the company that created the protocol, for performance and feature reasons?

Google Docs: For longer documents.

Google Talk: For short blasts of instant messaging, video chats and some audio chatting.

Picasa and YouTube: Communication doesn't have to be all text-based, you putting your photos and videos online count too.

Android and Chrome OS: By getting you down at the operating system level, Google can theoretically know every kind of communication you perform. It knows who you talk to, how you do it and when you do it. It can even shape the how by delivering the experience themselves.

Everything else. There's Checkout, Finance, Maps, Reader, News and other apps, which fill in the other forms of communication or expression that aren't quite covered by the major products above. One major missing piece is social networking, where Google basically failed before with its Orkut service (except for Brazil), so this new Twitter/Gmail hybrid might be their next entrance into the space.

But why do they want these things? Why would Google want to be the middleman between you and the world? To sell you ads, of course. And don't think Google is going to stop at just helping you talk over the internet or over the phone, they're going to reach into meatspace as well. How? One step is making that speech-to-speech translation portable, so you can do a sort of near-field communication with someone else with the same device while at the same time being able to look them in the face. Then, blast you two with the appropriate ads on the billboard next to you.

You hear the 9.7-inch iPad has a screen resolution of 1024x768, and you think to yourself, that's not so bad! And it's not. But when you later hear that a new 4-inch smartphone will feature a resolution of 1280x1024, well...

...it's just tough to be floored by anything less.

The Qisda (you also know them as BenQ) QCM-330, expected to debut at the upcoming CeBIT tradeshow this March before being available through Vodafone, features a 4-inch, 1280x1024 screen that could be sharper than life itself, along with HSDPA and Wi-Fi.

We don't know much else, other than that it will most likely run Android given the Home key (which makes the prospect of importing a phone for its hardware alone so much more appealing). But if you're one of those people who doesn't like to use the same phone as other people, the QCM-330 might be a decent handset to watch. [Unwired View via SlashGear]

They come in short spurts and are unannounced; even I am unaware they are about to occur. I'm speaking of blogging blackouts, periods of time where some unknown force keeps me from blogging. Has is it ever happened to you?

These stretches of time find me allergic to the keyboard. I suddenly don't have much to say, and that my (temporary) preference for real-life interaction outweighs the desire to write.

If might be my post-Super Bowl hangover, but I think these periods are happening with greater frequency, and I'm not sure what to make of it. I can only compare it to an old high school girlfriend. It starts out hot and heavy. You guys spend every waking moment together. Next thing you know, you take a weekend for yourself. That's usually followed by ONLY seeing each other on the weekends. Then every other weekend. And then, of course, the imminent breakup looms over your head for several weeksat least until someone has the courage to step up and call it off.

In most cases, the boyfriend or girlfriend will move on to another person to date. But if I am getting tired of dating' blogging, who should I move on to? Does blogging have a sexier cousin I should know about?

The thing I find ironic is that these blogging blackouts always come at a time when I NEED the extra income. At a time when I am relying on blogging to open up new doors. Perhaps I am putting too much pressure on myself. Blogging wants a ring and I'm not ready to take the plunge.

So how's your blog dating going? Please tell me I'm not the only one with trouble in paradise.

• It's based on Android 2.1. The build currently being circulated is identified as 2.1 version 1, mirroring the update just pushed to the Nexus One last week.
• Google Goggles is now pre-installed (no matter how unhelpful it may be).
• The browser's now multitouch enabled, just like Google Maps 3.4. Huzzah! No Flash, but then again, we weren't really expecting that.
• Interestingly, the home screen's still got the same look as 2.0.1, meaning it doesn't adopt the Nexus One's rotating 3D grid of app icons -- it's still got the pull-up drawer tab at the bottom.
• No active wallpapers. Bummer!
• The news and weather widgets introduced on the Nexus One are included. Maybe certain capabilities of 2.1 are going to be restricted to devices with minimum performance benchmarks?

Motorola Droid's next update to be Android 2.1, includes multitouch browser originally appeared on Engadget on Mon, 08 Feb 2010 09:05:00 EST. Please see our terms for use of feeds.

To support electric vehicles like the Leaf, which will be available in Houston toward year's end, the city and Reliant are working to create an infrastructure that places charging stations in convenient locations. Reliant will also be developing a system of support, including home assessments, for people installing home charging stations. The stations will be compatible with other plug-in vehicles as well.

Kindle dev kit now rolling out in limited beta originally appeared on Engadget on Sat, 06 Feb 2010 23:24:00 EST. Please see our terms for use of feeds.

The web is becoming more dynamic, context-aware and personalized by the day, and the amount of information consumed by each person is increasing exponentially. But while hardware performance is improving, except when it comes to the simplest of parallel programming tasks, software infrastructure is not keeping pace. We need to develop new data processing architectures ones that go beyond technologies like memcached, MapReduce, NoSQL, etc.

Think of this as a search problem. Traditionally, there was an index of every document in which every word occurred. When a query was received the search engine could just look up the precomputed answer to which documents had which word. For a personalized search, an exponentially larger index is needed that includes not only factual data (words in a document, brand of cameras, etc.) but also taste and preference data (people who like this camera tend to live in cities, be under 40, love Napoleon Dynamite, etc.).

Unfortunately, personalizing along 100 taste dimensions leads to nearly as many permutations of recommendation rankings as there are atoms in the universe! Obviously there isn't enough space to precompute what recommendations to show every possible type of person that queries a site. Additionally, precomputing the answer to queries is too slow. People expect real-time results, not hours- or days-old precomputed answers. If I tell Amazon I don't like a book, I want to immediately see that reflected in my recommendations.

We're at a turning point in how we need to build web sites to handle these sorts of personalization problems. While first-generation distributed systems split the application into three tiers web servers, application servers and databases second-generation systems build large non-real-time back-end clusters to analyze huge amounts of sales data, index billions of web documents etc.

A third generation of systems is now emerging, with the computation shifting from those back-end clusters into front-end real-time clusters. After all, you just can't build a back end that precomputes personalized results for millions of Internet users. You have to compute it in real time.

Adding complexity, many personalization problems are more difficult to parallelize than a lot of traditional back-end applications. Indexing the words in web pages is actually a lot easier to parallelize than are the long sequence of matrix calculations required to optimize a user's recommendations.

Matrix calculations tend to involve complicated data access patterns that mean it's hard to partition calculations and their data across a cluster of computers. Instead there tends to be a lot of sharing among many different computers, each of which holds a piece of the problem and updates the others as data changes. This back-and-forth data sharing is both incredibly hard to keep track of for the programmer, and can significantly degrade application performance.

The systems we've built at Hunch to solve this started off using distributed caching with memcached but very quickly veered into something more akin to distributed shared memory (DSM) systems, complete with multiple levels of caching, coherency protocols with application-specific consistency guarantees and data replication for performance. With an abundance of processing cores at our disposal, the real challenges tended to revolve around getting the right data to the right core.

I think that in a few years we'll look back at this time as an era in which a slew of new large-scale programming challenges and their solutions were born. Hopefully we'll also see more open-source solutions along the lines of memcached and Hadoop, so that building personalized and real-time web applications is easy for everyone.

Tom Pinckney is the co-founder & VP of engineering of Hunch.com.

Related GigaOM Pro content:

• What's Next for the Cloud? Distributed Architectures
• Infrastructure Winners and Losers of 2009