Skip to main content

Gott ist tot!


"Uska religion mere religion se jyada secular kaise!", may well be the new punch line for ads for religions. Scientology, the religion practiced and promoted by the likes of Tom Cruise, has already started advertising itself. Soon other religions will follow suit resulting in an all-out war (like the Cola war) with each religion calling other names. Christianity may even throw in some free goodies for those convert, "Become a Christian and get a chance to touch the Pope! (Warning: You are allowed to only touch the Pope. He should not be knocked down.)". If you are wondering how dare I say such things, all this is courtesy the recent HC decision to allow individuals to criticize religions.

After hearing about this judgement, Praveen Togadia, Varun Gandhi and the entire RSS clan are jumping with joy. So are the mullahs of Jama Masjid, who are known more for issuing fatwas at the drop of a hat than for anything else. They can now do mud-slinging at each other with gusto and without any fear, not that they had any of it earlier. They can now shamelessly defend themselves behind this HC judgement in case someone dare complains.

Bollywood is also relieved. Till now they could only make movies which bring out the best in a religion as shown in this video of "Purana Mandir". Their attempt at criticising God remained limited to the old mother/unwed sister/blind father complaining, "Hey Bhagwan! Yeh tune kya kar diya!", much to the amusement and surprise of God. And who can forget Amitabh Bachchan fighting with God, "Khush toh bahut hoge tum!". Let's hope that atleast now Bollywood makes movies of substance.

Personally I am both happy and sad by this judgement - happy because it has come after such a long time and sad due to the fact that we have to wait for a court judgement to exercise even our basic rights. May this judgement bring relief to all of us from the biggest man-made catastrophe - God.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo