Skip to main content

India's Finest

In the backdrop of US arm-twisting India on the Dow issue, it becomes extremely important that the government remains much more careful while passing the Nuclear Liability bill. Alas, this is not the case. Manmohan Singh and Co. seem determined to sell Indian lives at throwaway prices for benefit of US companies.

India has an ambitious and indigenous nuclear power program to achieve the goal of 20,000 MW electricity produced by nuclear energy by 2020 which will be further increased to 60,000 MW by 2032. Thus India will produce 25 percent of its electricity from nuclear power plants by 2050. To meet these projections, India would need a major FDI in nuclear energy. This would be provided by US companies like General Electric and Westinghouse by way of supplying and building the nuclear power plants while the operator will be government controlled Nuclear Power Corporation of India Limited (NPCIL).

All over the world, the Nuclear Liability bill (or its variation) caps the financial damages to be paid in a case of nuclear accident to victims without any legal tussles. In India, it was merely Rs. 500 crores. After much opposition by Left and other parties, it is now raised to Rs. 1500 crores (nearly 300 million dollars). This is still a pittance if we compare it to other major nations.

Country
Nuclear Liability
United States
10 billion dollars (plus up to 5% if required for legal costs.)
United Kingdom
1 billion dollars
Switzerland
1.3 billion dollars
Japan
1.2 billion dollars


It becomes more interesting if you look at the fine print. This liability is only limited to the operator, in this case the Indian government. Thus in spirit if there is any disaster due to defective equipment or faulty construction by the supplier. it would go scott-free while the Indian government would be left footing the bill.

The extent to which government has gone to shield the US companies is evident by their changing of clause 17 .
Clause 17 of the bill allowed the operator of the plant to seek damages from the supplier if:
A) There's a pre-existing contract on liability between them
B) Or if there's gross negligence or willful act by the supplier
But in the final draft, the word "and" was added between Part A and B. This, the BJP and Left say, makes supplier liable only if there's a pre-existing contract with the government.
It makes me wonder whose interest is this government serving - India's or US? If these are the India's finest leaders, even God will not be able to save India.

Comments

Popular posts from this blog

Pi Hole - Ad blocking (Turbocharged!)

The entire internet is now made up of ads. To easily navigate it and find the information you are looking for, most people use ad blocking software. It improves page loading times and also uses less data (sometimes by up to 10 times!)
Google Chrome is the de facto browser of choice for most people. Google's main business is advertising. So you can see how ad-blocking software collides with Google's business objectives. When Chrome was trying to be popular, it started allowing plugins like AdBlock Plus etc. Then slowly it started partnering with them for "Acceptable Ads Program" for a lot of money. Now after cementing its position as the most popular browser, Google is now coming down hard on ad blocking software. It is turning off a Chrome API (webRequest API) which most ad blocking plug-ins use to block ads.
Enter Pi Hole. This is an amazing use of Raspberry Pi which blocks ads before they enter your network. It keeps a blacklist of most popular ad serving domains …

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 Configuratio…

IoT on Google Cloud Platform

Google wants people to use its Cloud Platform for connecting and managing IoT devices through IoT Core and use other GCP components like BigQuery to analyze data produced by those devices. While these products are fantastic, they also have some real world challenges.
IoT Core provides a managed service for connecting IoT devices. It talks with both HTTP and MQTT protocols and features one-click integration with Cloud PubSub easing most of the infrastructure tasks. However there are some limitations:
You cannot use any random MQTT topic to send/receive messages as you would expect on a custom MQTT bridge. There are special topic formats to send messages and also to receive commands.IoT Core uses Public-Private Key cryptography to secure devices. All IoT devices must first authenticate using the Public Key in a JWT token and then start sending and receiving messages. While these may seem like reasonable restrictions, one has to keep in mind that hardware vendors are still stuck in the 9…