Planetary: First Smithsonian curation of code created using C++ and Cinder-- S Chan & A Cope
The first piece of code acquired by the Smithsonian's Cooper-Hewitt National Design Museum -- "Planetary", written in C++.
Planetary: collecting and preserving code as a living object
Posted by Sebastian Chan & Aaron Cope on Monday August 26, 2013
From the article:
Cooper-Hewitt has just acquired its first piece of code. Although the collection has objects that are the end result of algorithmic processes, notably Patrick Jouin's 3D printed chair, Solid C2, this is the first time that code, itself, has been collected.
Almost all contemporary design practice involves digital processes -- from the ubiquitous Adobe design software to CAD packages used by product designers and architects, to the simple day-to-day office management and accounting software -- it would be difficult to find a designer who lives entirely 'off the grid.’ Despite this, design museums have been slow to start to add software to their permanent collections.
Some of this reticence to collect digital objects stems from deep uncertainties as to how to preserve and present such objects to future visitors and future scholars. But for Cooper-Hewitt these uncertainties have been a strong driver to experiment.
So, here we have Planetary.
Planetary is an iPad application written in C++ using the Cinder framework. Planetary offers an alternative music player application for the iPad that visualizes your music collection as a series of celestial bodies. Songs are moons, albums are planets, artists are suns—and the orbits of each are determined by the length of albums and tracks. Their brightness represents their frequency of playback.
Continuing Koenig's series on move semantics:
I've been looking at the BlackBerry 10 NDK the last weeks, and did write about it to share some thoughts and results.
Danny Kalev wrote a nice article yesterday about a new C++ feature -- actually, two related C++14 features -- that were just added to the draft Standard in April and will be coming to real compilers in the near future.
We keep hearing about C++'s "as if" rule, but what does it really do? Fundamentally, it enables optimizations. A modern compiler never produces an executable that's identical to the program you actually wrote; it produces an equivalent program that's probably a lot better.
A nice piece of writing on a C++11 feature:
Here is a nicely accessible description of synchronization in the C++ memory model: