Yeah, I tried to switch ISP. Was thinking everything was fine, then tried to watch on ClaroTV+ here (similar to Youtube TV, Hulu Live, etc), and it was... awful. Then I figured out, the IPv6 route was going from Brazil > US > Argentina, or some other crazy crazy route. While IPv4 was just inside Brazil.
So I tried to complain to the ISP, and they just said they couldn't do anything, and if I wanted, they could disable IPv6 for me...
Of course, I canceled the ISP.
Sadly it's pretty common for several ISPs have smaller peerings with IPv6, so this is not uncommon.
My other other ISP worked super fine, but even then, they had two ASN. One for IPv4 and the other for IPv6, just to show how different they were...
Here in Brazil most ISPs provide IPv6 by now... But what happens a lot, when field technician are installing your broadband, they just... don't configure IPv6. As if IPv4 (CGNAT!) wasn't enough. With bigger ISPs this is less common.
With mobile carriers this is even worse. For some reason, some default config are IPv4 by default, while literally all of them supports IPv6.
This is not related to Google or Apple. And this extreme alert, it's sent even to cable TV automatically.
In a few countries, it's sent even on Fax lines.
.NET Native was experimental in WP 8.1 and W8. On 10, it becomes mandatory and you couldn't even publish a JIT .NET app to Store.
WP 8.0 didn't even had WinRT, only Silverlight apps, and all JIT. If you wanted native in 8.0, had to go with C++.
About Desktop, C++ was rarely used. Most apps were either .NET C# (JIT) or WinJS. JIT WinRT .NET was super slow, WinJS apps were even faster, which is why many apps were all WinJS, including inbox Windows apps, like the MSN apps.
Windows 8 Inbox apps a lot of them where WinJS actually. But on Windows 8 even web tech was fine (speed-wise).
And WP 8.0 < didn't offer AOT for .NET apps. AoT only came as experimental on WP 8.1 with WinRT apps if I recall right. And on W10 and W10 Mobile, it comes as default for all UWP .NET apps.
WinUI made sense when windows actually had a proper design guideline, and touch was also the focus. So using WinUI was just easier as the controls were all following the guidelines, and if you wanted to offer a native experience, that was the best choice.
But it's been long gone that time where Windows had a minimum cohesive guideline.
Because TED is not the only way to send money now...? It's basically legacy, although yes, still used.
Very rare you'll see Person to person/business using TED. Basically business to person...
And yes, literally banks had to "talk" with each other. Which is why it was paid and slower in first place and didn't worked 24/7.