You might be better of looking in to google earth and sketchup, as thats what google seems to be promoting sketchup for (at least it was last time i checked, been out of the loop for a while.)

@michaliszissiou said:

What is this? A joke? Go tell this to people who are working in mines, in industry, in hospitals. Tell it to policemen, to firemen, to professional soldiers, to non professional solders. To seamen.

All industries where a degree of risk is inherent (its never going to be safe to send people thousands of meters underground to operate heavy machinery in confined spaces, and the workers accept this.) Whereas its very easy to eradicate the risks caused by smokers to resteraunt workers. Just because theres risks inherent in every part of life theres no need to exasperate them where its easily controllable.

http://www.bbc.co.uk/news/world-us-canada-11657376

edit: if you insist chris

4 year old kid being sued for crashing in to an old woman during a bike race, causing injuries that led to the womans death. Its just plain old stupid. Im sure the kids going to feel guilty enough as it is without dragging them through a lengthy legal process that will ultimately change nothing.

http://www.rawstory.com/rs/2010/10/wikileaks-founder-julian-assange-walks-cnn-interview/

It really pisses me off that the reporter is so short sighted as to try and turn it in to an interview about the accusations levelled at one man when the real questions are around the tens of thousands of civilians who have been killed.

in case you forget what goes where?

theres instructions on how to install it at the bottom of the first post.

thats awesome boo

@unknownuser said:

Protocol Buffers are a way of encoding structured data in an efficient yet
extensible format. Google uses Protocol Buffers for almost all of its internal
RPC protocols and file formats.

This library has two components: a compiler to turn <tt>.proto</tt> definitions
into Ruby modules (extension <tt>.pb.rb</tt>), and a runtime to use protocol
buffers defined by these modules. The compiler relies on Google's C++ based
compiler (+protoc+) for much of the heavy lifting -- this has huge advantages in
ensuring compatibility and correctness.

This library is heavily optimized for encoding and decoding speed. There is a
small C extension available in the ext/ dir that will improve performance even
further, but it is currently disabled to avoid rubygems having to compile a
native extension. TODO: anybody know if we can make this optional?

Because this is a tool for generating code, the RDoc documentation is a bit
unusual. See the text in the ProtocolBuffers::Message class for details on what
code is generated.

Certainly sounds interesting.