Only 1 hospital chain has these all packed in to 1 entity, IMHO. That chain also is the only chain in the world that trades near 1x replacement cost. But how can we buy it? It makes losses! -ve RoE!! Doesn't appear in quant filters, ignored due to RoE = Moat rhetoric. PAT is God.
How many hospitals in India have globally comparable healthcare quality and high end molecular diagnostics, genomics diagnostics, AI/ML, Robotics for timely, accurate diagnosis and best possible prognosis, treatment at affordable cost?
— Sajal Kapoor (@unseenvalue) June 21, 2021
Any thoughts @tusharbohra @AdityaKhemka5 https://t.co/6Mhpu5Dru1
More from Uvlearnings
There's more to disclose!
Waiting for business to perform before i share more as too much talking is deemed 'pump and dump' by the elite Twitter activists (who have to pay their advisory staff's salary and bills - so free knowledge sharing hurts their interests)
#Biotechnology
Waiting for business to perform before i share more as too much talking is deemed 'pump and dump' by the elite Twitter activists (who have to pay their advisory staff's salary and bills - so free knowledge sharing hurts their interests)
#Biotechnology
@unseenvalue mentioned this in his seminar https://t.co/kGS9jHuBYx
— Sishya of Highly Respected Sunaka (@JpackJack) June 19, 2021
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.