Skip to main content

Life imitates The Onion

Almost four years ago The Onion, fine purveyors of satire and parody, published an article called "Poverty-Stricken Africans Receive Desperately Needed Bibles".

Now, in the aftermath of the Haitian earthquake last week, comes news that an American faith-based organization, Faith Comes By Hearing, is sending relief to Haiti in the form of solar-powered audio Bibles:
With tens of thousands of Port-au-Prince residents living outdoors because their homes have collapsed or they fear aftershocks from last week's quake, the audio Bible can bring them "hope and comfort that comes from knowing God has not forgotten them through this tragedy", the group said.
Personally, if I were there, I'd probably probably prefer food, water, medical care, clothing, and shelter to an electronic audio bible, but that's just my own personal preference.

Comments

Post a Comment

Popular posts from this blog

Java command line app with Spring and Gradle

Many Java developers have had to build a command line app for one reason or another over the years, and there are many(!) ways to do it.  There are a bevy of command line libraries, some people roll their own when they get to this point (which is one reason why there are so many command line libraries!), and others just pull in the arguments simply and directly, eschewing a library. However, writing a tool, a developer should just focus on the meat of the problem rather than having to worry about the enabling functionality that allows it to work.  The Spring Framework very much supports this approach to development with its inversion of control (IoC) container and a myriad of other features. To support that approach for command line applications, the spring-cmdline library provides a bridge between the Spring framework and the JOpt Simple command line library. This tutorial will show how to leverage the spring-cmdline library to stand up a very simple command line ap...
Post a Comment
Read more

manifest classpath + taglib jars + Tomcat = FAIL

I found an interesting side-effect of using manifest classpaths in our application jar files as it applies to taglib jar dependencies and embedded Tomcat 6. ·          Manifest classpaths do not appear to be expanded in the URLClassLoaders that load the jars with the manifests, so only the jar file referenced directly on the classpath are included in its URLs. The taglib search mechanism in Tomcat 6 (haven't checked Tomcat 7 to see if there's a difference) only walks the classpath looking for URLClassLoaders, looking at the underlying JAR URLs. Thus, if the taglib jar is referenced only as a dependency in the manifest of the main jar file and is not specifically on the classpath, it will not be spotted and use of that taglib by the JSP engine will throw an exception. This problem won’t actually show up in tests as IDE environments and builds generally include all the jar files in the classpath, so this one will bite you at runtime. ...
Post a Comment
Read more