Sugar #stocks have been rallying heavily over the past few weeks. And it seems like this has a whole lot to do with a chemical compound that's been all over the news lately.

We're talking about ethanol.

(thread...)

👉Ethanol is a complex derivative that can be extracted while processing sugarcane. It can be extracted from sugarcane juice and even from the likes of corn, bamboo, & rotten potatoes.
💡But what is really unique about #Ethanol is- it has high levels of oxygen, it burns cleaner than your everyday fuels like petrol or diesel. And thankfully for us, India has consistently had a surplus sugar production.
However, the surplus sugar also had its downside in that it sometimes caused the prices to dip. This forced the govt to provide export subsidies to help the farmers & sugar cos.
👉But now the government hopes to kill three birds using one stone. They see an opportunity in using ethanol and to make cleaner fuel, reduce oil imports as well as help our sugar industry.
💡The plan is to create ethanol-blended #petrol as part of its ‘E20’ policy, wherein by 2025 as much as 20% ethanol could be in petrol.

But to meet the target, we need to ramp up the current capacity of ethanol & set up new plants.
👉Also, a report by Expert Committee On Roadmap for Ethanol Blending in #India pointed to the fact that main ethanol-producing crops like sugarcane & paddy use up ~70% of irrigation water, leaving little water for other crops. This accentuates the need to look at other sources.
👉Then there’s another problem. Ethanol comes under the purview of GST which works out to between Rs 2.28–3.13/L, while petrol doesn’t.
And the central excise duty on petrol is approximately Rs 33/L. Blending will lead to losses of ~Rs. 10,000 Cr for the govt, because less petrol will be used.

So there’s still a long way to go but it seems like we’re on the right track. Let us know your thoughts.

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.