Chromebox, now for simpler and better meetings

This device addresses a lot of those issues. Walk into the room; joining the hangout booked for this meeting just requires a single button press.

The Chromebox is bound to a room (GApps resource) so it is aware of which meetings start when, and shows this to you on the screen.

Also, the Mac Mini solution involves creating named GApps accounts, and inevitably those sessions time out or people log them out. These devices also solve that problem (they are 'bound' to your GApps domain), which for a company with more than a few conference rooms can get really old.

I read this and remember back in the late 90's when Videoconferenceing was moving away from expensive ISDN lines into the internet and thoughts of H.320 and respective document sharing (slides as this does) add-ons and extensions gave a usable platform albeit not cheap. That changes, video compression and codec onto chips came to market and got cheaper and cheaper.

Now some 15 years later after many flavours, Google now offer the option but not just a feature push, but on a slow, methodical gradual feature addition which has seen the progress from VOIP/IM chat into video, into group video into a public contact phone book (aka Google+) of today. Then into a rebrand and now just polishing to the lowest common denominator of user in userbility (I personaly prefered ealier Gmail and chat clients, but that's me and other quirky geeks I suspect).

So why is this big or important more too the point. Well If you view ChromeOS and its features to a modern revamp of the `dumb` terminal (that were not that dumb and could do Various terminal standards and on mainframes even form validation for numeric and alpha feilds and size of input back in the 80's.

Now duringt he 80's a company called SInclair released there next ZX Spectrum replacement which ICL modified and released the OPD (One Per Desk). This was featurewise in mahy respects what a user today wants in a terminal, even had phone built in, though no video back in the 300baud data days.

So too me I see ChromeOS and the slow but sure feature set grow, as the new terminal for the cloud - aka cluster/distributed mainframes we use thesedays. After all everything goes in circles, even technology approach. I know people can and do view webbrowsers as the terminal of our times and yes, many would be right, but if you step back a level you would want something with a little more, though not much more and a good interface and mobiles have opened up the whole touch-screen interfacing (was around in the 80's, just not as cheap and usable) and for many tasks, work very well. But bigger screens always will help upto a point and a real keyboard (although still stuck in a layout that seems like forcing some backwards outdated layout onto new people and children even today, think keyboard-religion). It is with that all in mind for me that make ChromeOS seems like the `dumb` terminal of our times and remember `dumb` terminals are never dumb.

Now when you can add via a MCU/bridge external VC setups and studios into a hangout is when Google will be truely and finaly solidifying a technology that serves our times and needs and if anything else. Least help stop the UN and other World leaders flying around the World to lecture us mear peons why the climate is in a mess and how we should do our part about carbon emisions, whilst they then fly to the poles for photo shoots to add onto there stories of why climate change is happening.

That is what Videoconferencing can truely offer and can, but its main issue has always been taking it serious compared to a jolly/plane flight/travel for so many mentality wise, again think the same mentalities that give us QWERTY keyboard-religions.

One day, but after over 15 years I hope this keeps the momentum and slow but sure approach google has taken so far into Videoconferencing/VOIP. Until then we will always have `dumb` terminals and mainframes be they touchscreen clients or clustered machines called a cloud.

I remember trying to replace a T1 with Comcast Business Cable. It was faster in the office, but variable latency, dropped packets, less usable remote access (just ssh and scp) and more frequent maintenance outages killed it.

IIRC, SDSL turned out to be the better answer (and we really, really wanted to try FiOS, but they didn't support our building).

True enough, but you don't have to active G+ on your Google Account.

I can't fathom why this thing even needs such a high power CPU. Presumably it's running Android, so why not go with ARM + a nice video coprocessor to handle video?