> there is that CO2 on the air that we actually want to get rid of
For this reason I have long been slightly baffled that development of compostable/biodegradable bio-based plastics is such a priority in materials research. Sure, it's interesting in the very long run, but for the foreseeable future, converting atmospheric CO2 (via plants as an initial step) into a long lived, inert material that can just be buried after an initial use seems like a benefit.
Many of those big bells in other cultures are on fixed mountings (in a carillon, for instance). The idea of mounting the bell on a rotating wheel - which imposes limits on what music can be played due to the rotational inertia of the wheel, therefore leading to a unique style of composition - is distinctively English.
More likely a hall effect sensor, which is solid state and a lot smaller. And yes, older MacBooks had something like that, as evidenced by the fact you could put them to sleep by holding a magnet in the right place (just to the left of the trackpad IIRC in the models I'm familiar with)
My read of that caveat from Google is that the code that was removed was third party code that Pebble had a proprietary license to use, thus it was not Google's to release.
Good ergonomics for Perl-style quick and dirty text processing were part of the original design goals for Ruby. Those parts of the language are still there. You can write code that feels more concise than Python yet, IMO, tends to be more readable/maintainable than Perl can stereotypically be. Modern style guides, however, de-emphasize that style of Ruby since it might not be the most appropriate in the context of say a large Rails project.
Polycarbonate doesn't have any chlorine at all in its chemical formula. Maybe the usual types of Lexan contain plasticizers/flame retardants/other additives that contain chlorine?