Seems like this article conflates threads C# with asynchronous operations a little.
The way I see it, threads are for parallel & concurrent execution of CPU-bound workloads, across multiple CPU cores. And typically use Task Parallel Library. Async/await won’t help here.
Whereas async/await for IO bound workloads, and freeing up the current CPU thread until the IO operation finishes. As mentioned, syntactic sugar on top of older callback-based asynchronous APIs.
>My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why.
Let's be real though, Apple didn't enforce this to save user's the small annoyance of 'use browser X' popups. Instead it gives them full control over what web APIs are available on iOS devices, so they can avoid implementing those APIs that would impact on their App Store revenue. They have a clear financial benefit in not supporting the PWA technology that would move the 'simpler' apps off their app store and into web - where they wouldn't receive their developer license fees, a cut of paid apps and a cut of paid subscription fees (outrageous). Also, I believe it was Steve Jobs who first shared the vision of web applications on iPhone “that look exactly and behave exactly like native apps” ?
> Instead it's web developers, who are just annoyed that they have to actually respect the conventions of the platform they're building for.
Developers already get around this to some extent with cross platform tools such as React Native, Xamarin, Flutter. Native apps will always have a place, PWAs are not going to replace sufficiently complex app experiences, much like on Android or Windows.
Not because it’s Apple, but rather because Apple are exploiting their position as iOS App Store gatekeepers to require developers to add Sign In With Apple. Mozilla don’t have this position / power.
I think people would have the same issue if Google required ‘Sign In With Google’ in play store apps that have Facebook login, and returned throwaway / proxies email addresses.
There by, when apple passes a [email protected] address back, it won't match the existing account's email address = Sorry, matching account not found ?
The way I see it, threads are for parallel & concurrent execution of CPU-bound workloads, across multiple CPU cores. And typically use Task Parallel Library. Async/await won’t help here.
Whereas async/await for IO bound workloads, and freeing up the current CPU thread until the IO operation finishes. As mentioned, syntactic sugar on top of older callback-based asynchronous APIs.