202 karma · joined April 27, 2016
From what I read, it doesn't yet support stuff like async/await, LINQ, lambdas (and few other things). And those are used a lot in modern .NET apps.
Still a great improvement in the right direction.
It also tells you how you should write your components, which is another sign that it's a framework and not just a library.
Because on one hand, you do pick up hotfix patches, but on the other hand, you are possibly bit more exposed to supply chain attacks.
Any ideas on how to balance that out? Or should we just not consider supply chain attacks to be a real threat?
I don't know how valid it is though. But it could contribute to the whole thing I guess...
I'll be forced to update when enough apps (not Apple, but third party) stop working because they no longer support iOS 12. Currently, there are only 7 apps out of over 200 that I have installed that don't support iOS 12. So I have to run an older version of these apps. Eventually there will be many. And the older versions of the apps will eventually stop working as well (if they connect to some web APIs that will be deprecated). This is what forced me to upgrade from iPhone 3GS to iPhone 6 last time.
Apple now cannot reject apps because they have "Buy" links that redirect users elsewhere. And that's still a big deal.
Maybe they have seen so many red herrings that they don't even trust that the error message could contain something useful and relevant? Or maybe they just learned to skim through everything, and don't actually read stuff.