Async/await syntax doesn't guarantee what kind mechanism is servicing the async work. Consider a situation where you have limited threads (perhaps even only one servicing both sync and async calls).
Blocking that thread to wait for an async call would prevent the async call from completing and would be a deadlock.
As noted, you can run sync code from an async context. Even if you have a thread pool, blocking in sync has a chance to block and consume an async worker thread. That can also cause deadlocks.
They don't make it easy to wait synchronously because it's a bad idea. Making the syntax more amicable to blocking is a worse idea.
I've seen an interesting corollary: 4G on an airplane at the gate is much faster than the 5G microcells inside the terminal.
If I'm downloading podcasts for a flight, I do it on WiFi beforehand or on 4G on the plane. 5G in the terminal is really useful at getting you some service, but it's slow.
Probably a side effect of not enough backhaul speed.
5G outperforms wifi in crowded situations. With wifi you get increasing collisions and backoff intervals until everything stalls; with 5G you just get less bandwidth (time sliced) but no collisions, and its frequency spectrum is free of interference.
How would it have helped? Net neutrality doesn’t mean you can’t sell your customers different bandwidth guarantees.
Net neutrality is only about the connections between a provider and external networks, not about how a company handles bandwidth contention amongst its customers.
Net neutrality would fix a problem like “only Facebook is accessible inside crowded stadiums” not “AT&T customers who pay more get better connections in crowded stadiums”
Net neutrality as generally understood says nothing about being able to pay more for a higher service tier from your ISP.
It's entirely on the publisher side: net neutrality was an attempt to avoid ISPs getting paid extra---costs that would be passed onto you---in exchange for making your experience on site A be better than your experience with site B (or service, vs site).
Think: "Oh, yeah, Netflix 4k works great on your new Comcast plan! But if you want Hulu 4k, you're gonna need to pay us more, because Netflix pays us to make their shit work better than Hulu's if you don't!"
Net neutrality means that providers don't discriminate based on the kind of traffic, that you get internet access, not just access to particular services.
They can absolutely meter and limit your connection as long as one byte is one byte, no matter its origin. They can also discriminate based on the technology they provide (4G, 5G, fiber...). Net neutrality is not about preventing "pay to win", obviously, you can get a better connection if you pay more. It is about fair competition between online services.
People still believe this? Google pays their ISP. I pay my ISP. Google does not pay my ISP. Why is my ISP's response to the amount of traffic I use demanding to bill someone other than me?
To be clear, Google was doing this out of self-interest. Paying user ISPs for access to those users is not a cost they want to pay. But it's the same as any other protection racket. A local shopkeeper has personal reasons to not want to pay off the mob, but that doesn't mean their position is wrong.
ISP's spent $$$$$ against net-neutrality cause they wanted to get paid twice (Google already was paying for their side of the bandwidth as the source).
When you add the second line---pretending that that nobody funding all the anti-net-neutrality let-big-ISPs-do-what-they-want stories that pro-legacy-company Republicans ate up---it makes me think this is some astroturfing, since it goes from "maybe this person fell for the ISP claims" to straight-up dishonest intentionally-misleading-fallacy.
Google was obviously on the side of "don't get charged twice" but ultimately net-neutrality was a tech enthusiast consumer position that came out of a desire to avoid getting charged more on the basis of what sites you did or didn't want to watch, and ISP's trying to influence where you visited by cutting deals to get paid to prioritize A vs B.
(Hell, ISPs were already getting paid "twice" for the bandwidth in some ways, e.g. when your "100Mb" plan only works at that speeds if your neighbors aren't using it much. That's a different sort of incomplete-advertising trickery that helped create the whole "too many people using Youtube are saturating the network!" "problem" in the first place.)
(And high-bandwidth publishers already were making private peering/colo-of-servers deals with ISPs and CDNs that I don't believe would've been prohibited by net neutrality, so the 'protection racket' aspect of the ISP's game was maybe more arguably wanting to be paid thrice? Or wanting to be paid without providing that colo service?)
That is a very effective use case, but until we live in hive cities, stadium-level device densities are an edge case. Developing a new generation to service the 0.01% of time phones spend inside stadiums seems inefficient.
They struggle a bit on Oxford Street which as stadium like densities much of the time. I changed networks to O2 as Three became pretty much unusable in that area. Three sell a lot of unlimited data packages which their hardware seems inadequate to serve.
If you have a season ticket to a Premier League team you're going to be in that density once a week or once a fortnight. Whatever the percentage of time that might be, that seems frequent enough to not be an edge case.
reply