EU chief negotiator Michel Barnier has briefed Europe Ministers from EU member states that progress continues to be made in negotiations with the UK but not significantly when it comes to key sticking points: level playing field, fish, governance of deal /1
More from Brexit
1/ A challenge in parsing Brexit news is that businesses are facing overlapping types of challenges that can be difficult to separate.
The key questions are:
1⃣ Given the model of Brexit chosen, could this have been prevented, and by whom?
2⃣ Can it get better?
2/ To put those another way:
"If you knew everything you needed to know and did everything right, is your existing business and delivery model still viable and competitive?"
The answer to that question determines if for you the problem is Brexit, or how Brexit was delivered.
3/ Some of the challenges at borders could have been prevented while still having the exact same model of Brexit (No Single Market, No Customs Union, but an FTA).
That they're appearing is an implementation failure and you can fully support Brexit but still be pissed about them.
4/ Examples include:
1) Government guidance and IT systems being ready earlier and/or easier to navigate;
2) More support for businesses, and more affordable bespoke help;
3) More time to prepare and better government communication about what preparation actually requires.
5/ This thread you've all seen from Daniel Lambert the wine merchant (primarily) deals with problems in this category.
There's no policy reason he can't export his product, but the procedures are a nightmare to navigate and he's badly under-supported.
The key questions are:
1⃣ Given the model of Brexit chosen, could this have been prevented, and by whom?
2⃣ Can it get better?
#Brexit & #fishing: True to their word, it looks like British #seafood exporters are taking their concerns around #trade to the streets of London #Brexality pic.twitter.com/CIqmDQR69d
— Bryce Stewart (@BD_Stew) January 18, 2021
2/ To put those another way:
"If you knew everything you needed to know and did everything right, is your existing business and delivery model still viable and competitive?"
The answer to that question determines if for you the problem is Brexit, or how Brexit was delivered.
3/ Some of the challenges at borders could have been prevented while still having the exact same model of Brexit (No Single Market, No Customs Union, but an FTA).
That they're appearing is an implementation failure and you can fully support Brexit but still be pissed about them.
4/ Examples include:
1) Government guidance and IT systems being ready earlier and/or easier to navigate;
2) More support for businesses, and more affordable bespoke help;
3) More time to prepare and better government communication about what preparation actually requires.
5/ This thread you've all seen from Daniel Lambert the wine merchant (primarily) deals with problems in this category.
There's no policy reason he can't export his product, but the procedures are a nightmare to navigate and he's badly under-supported.
Over the past 15 days I have not only been running my company as normal but I have been faced with largest threat to its future since it began in 1992. This is #Brexit & here is my thread on just how bad things are getting. 1/26
— Daniel Lambert (Wines). \U0001f1ea\U0001f1fa\U0001f1eb\U0001f1f7\U0001f3f4\U000e0067\U000e0062\U000e0077\U000e006c\U000e0073\U000e007f\U0001f347\U0001f942 (@DanielLambert29) January 16, 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.