🎙 @Pirlo_official's virtual press conference has begun: "@sampdoria_en is a good team, they come off the back of a positive run, they have added quality to the squad. And it's never easy to play against Coach Ranieri, whom I respect a lot."

#SampJuve

🎙 @Pirlo_official: "How do you get to the first team? You have to be good... Fagioli joined after Portanova's departure, he will be a part of the group but will still be able to play for the #Under23s."

#SampJuve
🎙 @Pirlo_official: "Today everyone should be able to train with the group apart from @PauDybala_JR, but we hope he is on the right track too. We have a tour de force of matches coming up, it will be necessary from time to time to see who is better."

#SampJuve
🎙 @Pirlo_official: "Tomorrow, @federicochiesa will start from the beginning. @WMckennie? He is guy who has a great desire to improve, and can do it. He has good room for growth and has the right mentality."

#SampJuve
🎙 @Pirlo_official: "Against tight defences you need to be patient - we know that Sampdoria will try to be compact. Ranieri keeps the lines very tight, we will have to try to widen them."

#SampJuve
🎙 @Pirlo_official: "@AlvaroMorata is recovering well. He is a guy who thrives on enthusiasm and we want him to be at his best. I am convinced that he will continue at his level. The backline? We will have rotations based on the matches scheduled."

#SampJuve
🎙 @Pirlo_official: "Tomorrow's formation choices will not be influenced by the #CoppaItalia. We will field the best team both tomorrow and Tuesday, thinking of one match at a time."

#SampJuve
🎙 @Pirlo_official: "Tomorrow, @Cristiano and @AlvaroMorata will start in attack."

#SampJuve
That was the final response from @Pirlo_official!

Catch a recap on https://t.co/whCoAoQLEi soon

#SampJuve

More from Sport

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.