As we don't yet know December demand, I'll report back with my estimate later. Expect 24-28k.
1/ 8 #Tesla ships have sailed to EuropeЁЯЗкЁЯЗ║ this quarter, and it's unlikely that there will be more.
With inventory, that means they will have ~30k M3's available for delivery in EU. Compares to 31.8k last Q4.
$TSLA $TSLAQ
1/ \U0001f1ea\U0001f1fa weekend update.
— fly4dat (@fly4dat) November 14, 2020
TL;DR: #Tesla will likely lag 19Q4 by a wide margin.
There have been 8 ships to Europe for ~28.2k in 19Q4 and 6.2k in opening inventory, so $TSLA could deliver a record 31.8k M3's.
This year they are at 6 ships with a 7th being loaded.$TSLA $TSLAQ https://t.co/xJ31lqvAHN
As we don't yet know December demand, I'll report back with my estimate later. Expect 24-28k.
Tesla US sales should be booming, or there is some other problem. Some might whisper "demand".
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.