AR20-21 Notes
Praj Industries
India’s Leader in Bio-Fuel Technology
Put on your helmets & Enjoy the ride 🙂
Retweet for wider reach 🙏
~Ethanol Demand to rise from Govt push for 20% ethanol blending by 2025
~Launched BioPrism tech portfolio for producing bio-based Renewable Materials
~Identified growth areas like Bioplastics, Lignin products, specialty
chemicals, & others
~Praj continues to dominate the bioenergy sector in India
~Engg Business saw good unique opportunities
~Delivered Solutions as part of critical vaccine supply chain
~Reduced water requirement
~Enhanced plant capacity
~Increased ethanol yield
~Reduction in emissions
~Pharma Grade Ethanol
~Production of Compressed Biogas from agri-residues and pressmud
~Gained 5 Indian & 6 Foreign Patents in FY21
~Bagged awards for innovation and waste management
1st Gen Ethanol Domestic:
~Govt push to create opportunity for new 10 bn liters PA capacity
~Good traction for B-heavy molasses and sugar syrup based ethanol plants
1st Gen Ethanol International
~Traction for Pharma grade Ethanol
~Demand up for biofuels
2nd Gen Ethanol
~Has 3 orders for advanced biofuel refineries in India
~Expect demand from North Europe
Compressed BioGas
~Expecting setup of 5000 CBG plants in next 5 years
Others
~Developed process for making Isobutanol
~Scaling up SAF in India
~CPES got orders from a US-based Industrial Gases Company
~Slowdown in domestic Brewery Segment
~Got repeat orders for Zero Liquid Discharge Solutions
~HiPurity to see demand rise from pharma & personal care segments
~Joined with Institute Of Chemical Technology, Mumbai (ICT) for process development and reactor design research
~Produced breakthrough in making “Bio-bitumen” based on Lignin
~Filed for over 300 patents to date
~Ethanol demand to rise for blending
~CBG opportunity to rise
~Bioenergy to become mainstream due to focus on sustainability
More from SmartSyncServices.com
More from Praj
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.
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.
