There are a lot of Brexiters in the media this week making points about sovereignty, and about how the EU has not come to terms with the UK's independence.

I have some questions, which it might well be fruitful to ask them. 1/9

1. How do you understand the concept of sovereignty? What are the circumstances in which you might agree to make binding commitments to other independent states or trading blocs? 2/
2. What sort of commitments are you prepared to make in order to get trade deals with other states/blocs? And, to what end (why not trade on Australian-style terms with the wider world)? 3/
3. Do you accept that the EU has the right to impose its own rules as a condition for access to its market? Given the UK's involvement in the single market, and in the creation of its regulatory infrastructure, this feature should not come as a surprise. 4/
4. Do you accept that there is a need for borders (which were not needed while the UK was part of the single market) between states/blocs with different regulatory regimes? 5/
5. How are these borders going to work in January? What tariffs, checks etc are going to be required? How in particular are the unique circumstances on the island of Ireland going to be addressed? 6/
6. At the moment, Brexiter and Govt rhetoric insists that 'sovereignty' and 'unfettered trade' are mutually compatible goals. See https://t.co/vTI7qzGKel 7/
The reality is that they are not. The Govt must know this. The negotiations would not have limped on for as long as they have, had the Govt not shown willingness to agree to certain rules in return for (eg) tariff-free trade. 8/
The debate is all about the nature of the trade-offs, and the balance between rights and responsibilities.

Those who deny that trade-offs have to be made are not helping anyone. Every possible outcome will be said to be a 'betrayal'. 9/9

More from Brexit

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.