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 ?
Anyone know which Android based phone manufacturers or brands are based in the EU? Does the fine match their expected loses?
What does the EU do with the money?
Doesnt make sense, if google didn’t geoblock EU IP addresses how would the EU react? Issue another fine which Google won’t pay?
A similar analogy would be like the US blocking their citizens from traveling to North Korea. But then having direct flights from LA to Pyongyang and expecting North Korea to enforce the ban of US citizens at their customs. It’s not their responsibility..
> The problem is that when you are shopping for something, you don't want advertisers to be influencing what you see in search results. You generally want the best match to your search, not the product with the biggest advertisement budget behind it.
So they should remove advertising from google search results altogether?
Like saying TV networks shouldn't put ads/product-placements in their shows because their viewers are only interested in the shows/content.
Shouldn't need a license to prove you're an engineer unless say perhaps you're running an engineering business, where people's lives can depend on your work - e.g building a bridge.
If you have formal education in engineering, then I would think you can call yourself an engineer?
We have a smallish team working on web apps and use a trunk-based-development branching strategy. Not really to do with helping CI/CD.
The advantage we see is that new developers can start developing as soon as they clone the repository, without needing to switch to the 'development' branch. This is particularly useful when on boarding new developers who are inexperienced with Git. I found that when using Git Flow that the (stable) master branch frequently ends up out-of-date when developers are required to remember to merge into it releases into it.
I find his response to this question compelling when talking about Sarah Koenig and Serial:
" Was the name ‘Serial’ ever used?
No. Not to my recollection. She kept saying ‘This American Life,’ ‘the radio,’ and ‘a documentary.’ There was no talk of ‘Serial’ or a podcast. Then I asked her outright, ‘Are you an advocate for Adnan?’ She said ‘No,’ that she wasn’t his advocate. But she said that she had talked to Adnan, and she wanted to get more information about the case. She said there was new evidence, and I said there’s no new evidence that’s gonna change what I saw: I saw Hae dead in the trunk of the car. If Adnan wants to take the stand now and explain that away, let him. But there’s no evidence that’s gonna change what I saw. I don’t know how she was murdered, I don’t know exactly how she got put in that trunk, and I told the cops that. If Koenig wants to get into how that all happened she can go there. But that doesn’t change what I saw. And that’s the only time I commented directly on the case to her. "
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.