Ok, here is a thread for you.
What happens when you have:
Netflix
Apple
Amazon
WarnerMedia +
Disney+
SonyCrackle (Reboot)
Verizon All Access (after they buy CBS/Viacom)
UniversalSkyMedia
By 2021
Answer? Internet Slows To A Craw and Dies.
Why?
Bandwidth.

Netflix's gets 35% of all internet traffic.
Now we all know Apple Coming to Netflix Corner.
We know that WarnerMedia Planning One
We Know about Disney+
Now how will the net handle 8 Streaming Platforms all at once?
Answer - IT CANT.
But Novid, the speed, the 4K the all everything?
NOOOOO BUDDY.
Even if you could do it and even if AWS ran six million clouds, The Net Will still slow to a crawl. 35%, goes to nearly 90% if any of the 8 or all of the 8 eat at netflix's numbers.
Oh, they wouldn't be running at once.
FOOL. You forget how bad things were when game of thrones season premieres came around. HBO SERVERS FALL DOWN GO BOOM!
Now see if a season like 2021 come around and they air shows on a same day. It gets crazy. AT&T and others gonna realize they cant build out forever. Something will give and it might be your entertainment consumption big time.
You still need networks folks. You have a promotion problem as I stated before and you can only sell enough trinkets to women as is. Men got to have something to look at too and if you deny it and the rest of the silicon valley starts censoring others...
Well, yall gonna see that entertainment crash and It will not be pretty. Thats why if yall not careful fortnite will take over prime time and late night tv too...

More from Tech

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.
There has been a lot of discussion about negative emissions technologies (NETs) lately. While we need to be skeptical of assumed planetary-scale engineering and wary of moral hazard, we also need much greater RD&D funding to keep our options open. A quick thread: 1/10

Energy system models love NETs, particularly for very rapid mitigation scenarios like 1.5C (where the alternative is zero global emissions by 2040)! More problematically, they also like tons of NETs in 2C scenarios where NETs are less essential.
https://t.co/M3ACyD4cv7 2/10


In model world the math is simple: very rapid mitigation is expensive today, particularly once you get outside the power sector, and technological advancement may make later NETs cheaper than near-term mitigation after a point. 3/10

This is, of course, problematic if the aim is to ensure that particular targets (such as well-below 2C) are met; betting that a "backstop" technology that does not exist today at any meaningful scale will save the day is a hell of a moral hazard. 4/10

Many models go completely overboard with CCS, seeing a future resurgence of coal and a large part of global primary energy occurring with carbon capture. For example, here is what the MESSAGE SSP2-1.9 scenario shows: 5/10

You May Also Like