ππ @Pirlo_official talks #NapoliJuve from 13:00 CET β°
π΄π₯ WATCH LIVE on @JuventusTV!
#NapoliJuve
#NapoliJuve
#NapoliJuve
#NapoliJuve
#NapoliJuve
play like this. These are my choices based on the opponent, but the approach remains the same: command the game and press high."
#NapoliJuve
#NapoliJuve
#NapoliJuve
#NapoliJuve
#NapoliJuve
#NapoliJuve
The recap of his virtual press conference will be up soon!
#NapoliJuve
More from Sport
When thinking about who to play in DM for Leeds the word "role" is important. Let's have a think about the role:
A lot of people think Struijk isn't good enough in the build-up phase. Well, what does the DM do in build-up?
Here's a passing network from last season:
As you can see, Phillips' role in the Championship last season was largely facilitating build up in the wide area (on the left interestingly).
Per Wyscout, Phillips is putting up a figure of 7.03 long passes per 90 minutes and completes around 59%. Last season he was making 6.94 long passes per 90 mins at around 52%.
Per dribbles he's putting up similar numbers across both seasons (between 1 and 1.5 p90) and per duels he's putting up the same number (20 p90).
All of this suggests his role hasn't changed much over the last couple of seasons.
This exactly. I think the 8 and fullback roles in this system share quite a lot of common attributes, even forgetting how Bielsa looks to hybrid them in 3-3-1-3. No wonder that we've seen Dallas, Shackleton, Gotts etc play both. And these roles play to Dallas' strengths.
— Jacob Standbridge (@PocketTrumpeter) February 13, 2021
A lot of people think Struijk isn't good enough in the build-up phase. Well, what does the DM do in build-up?
Here's a passing network from last season:
![](https://pbs.twimg.com/media/EuGWLWNWgAIPg8V.jpg)
As you can see, Phillips' role in the Championship last season was largely facilitating build up in the wide area (on the left interestingly).
Per Wyscout, Phillips is putting up a figure of 7.03 long passes per 90 minutes and completes around 59%. Last season he was making 6.94 long passes per 90 mins at around 52%.
Per dribbles he's putting up similar numbers across both seasons (between 1 and 1.5 p90) and per duels he's putting up the same number (20 p90).
All of this suggests his role hasn't changed much over the last couple of seasons.
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
![](https://pbs.twimg.com/media/DrIk2JhU8AAjf_m.jpg)
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
![](https://pbs.twimg.com/media/DrIk3TjU0AAhf3D.jpg)
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.