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

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>