Skip to main content

Paperbecause - Compelling point or Absurd argument?

 

The site paperbecause.com, is from domat, a paper manufacturer, promoting the use of paper. For one consideration, they claim paper is physical and associates it with a emotions, features and relatively subtle nuances that cannot be attributed to electronic media counterparts.

 

Tree Huggers, Green advocates, on the contrary, try to reduce the use of paper. Reduce, Reuse and Recycle. For once, however, the use case of paper seemed to be apt. It is true that opening a paper card is much more thrilling than opening an e-card. Paper well hold well for physical and free-expressive mode of holding thoughts or expression. They press on the idea of how paper makes it easy to annotate, carry around with you – campaigning against campaigns like "Don't Print this".

 

They also claim, paper ads make a better marketing tool than emails or online campaigns. This is a little far-fetched argument, if not absurd. Google would not have made so much money if not for online campaigns and ads. If it were true Newspapers should still be the reigning destination for marketing. Point well made?

 

Also, PaperBecause's comparison with e-readers and paper books holds very little to reason with it. You can ask any kindle or iPad fan to make a case, they will persuade you enough. Holding data, annotating, emoting may still be evolving in this digital age. With time, mode of expression will only improve. And seldom it is constant. Lets recap quickly,

 

Take the case of  previous ages, for example. In earlier centuries, people used to write on stone. Literatures in India have a lot of sources on stone. As time passed by, people switched to $$$$$ Tati akulu (Leaves of toddy tree). The inscriptions lived as durable as they were on stone. Time passed by and paper was invented and lived, so far as until computer was invented. With computers, things have moved much faster, and the Paper, conversations are seeing a different way of expression :)

 

Still think paper? Come on! For a lighter moment, Here is a small conversation that may happen between PaperBecause and Computer

 

PaperBecause:

A Paper card carries more excitement, emotion.

Computer:

Do you know about face-to-face communication.

 

PaperBecause:

It archives well, remembers memories.

Computer:

You lose paper more often, Photos on Flickr live for ever :)

 

PaperBecause:

Those photos may disappear, if you press delete accidentally.

Computer:

Same risk runs on paper. Some one can tear it up, burn it down. Copies are expensive, use more paper. Soft copy backup. Free. O wait, your site, did you have enough printouts of it?

 

Disclaimer: The post is not to undermine the importance of paper. But to counter, the unreal promotion of paperbecause.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...