@cvocain 100% agree with your bearish view on those #APIs. I won't tell the names, so hopefully ppl will get motivated to watch the whole webinar (and learn something in the process). Good stuff @VineetGala 👌
More from Sajal Kapoor
You offer me 80% cost arbitrage (discount relative to Japan/EU/US) along with low confidence / assurance on Critical Success Factors and I won't give you a single NCE/NBE to discover, develop or manufacture. Capex/opex arbitrage is too low in the disruptive-science-pecking-order! https://t.co/O2l8dK4BUv

@unseenvalue Given high capex/opex cost structures of US/Japan/EU, how will they be able to compete with Indian API companies? https://t.co/OYhC2PUZpL
— Hiren (@hiren_investing) August 11, 2021
More from Uvlearnings
Many stock specific questions on my DM or otherwise remain unanswered. Have shared my thesis, process/framework over many months and would encourage you all to find your own process that suits your very own genome. Learn to do that hard leg-work. Put that effort. Survive. Thrive.
[Free CDMO Masterclass #18] https://t.co/208eQbYKEF
— Conviction | Patience (@unseenvalue) July 25, 2021
[Free Art of Investing] https://t.co/bHvUqnpiTE
[Paid IIC Dec 2020 on SeQuent] https://t.co/3iDO438Et9
[Charity fund raise on Unseen Trends in Biotechnology] https://t.co/eNi1x1qwhH
[Q&A on APIs] https://t.co/EQGz007a9S
The comment from renowned investor was in a lighter vein. You ought to listen to the tone. He was spot on in comparing the capability and scale of two businesses, as both started around the same time - one could scale up, whilst other couldn't. Let's not read too much into it 🙂
In an example of how deeply ingrained misogyny is in the Indian system, billionaire investor Rakesh Jhunjhunwala asked the management of Jubilant Pharmova: \u201cHow can we be lower than the lady? We have to beat her,\u201d in a slighting reference to @kiranshaw.
— Dr. Kailashnath Koppikar (@koppik) June 26, 2021
https://t.co/1dkZ9JMLLr
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.