Isn't the "advanced data protection" option already making it impossible for Apple to comply in cases where this is enabled? Of course this is not a perfect solution as it has to be explicitly enabled (and it has some usability drawbacks), but imagine that people who care about this stuff have this enabled already.
This article spawned because the UK is purportedly issuing a secret order under the Investigative Powers act for Apple to implement a backdoor encompassing Advanced Data Protection. Because these are secret orders it is illegal for Apple to disclose the fact they received any and what the content of the order is.
It is interesting to note that the UK is asking for this superuser privilege while also infamously silencing a literal epidemic of child sexual abuse for fear of its optics (i.e., Rotherham). It’s a difficult sell for me that the police need this to do their job when they wouldn’t do it with full knowledge of these horrible crimes being committed against literal children.
You do realize it is called a scandal _because of_ the lack of response?
> Failure to address the abuse has been linked to factors such as fear of racism allegations due to the perpetrators' ethnicity; sexist attitudes towards the mostly working-class victims; lack of a child-centred focus; a desire to protect the town's reputation; and lack of training and resources.[25][26][10]
> You do realize it is called a scandal _because of_ the lack of response?
There's a difference between a lack of response due to incompetence and uncaring officials (which this clearly was) versus "silencing" which suggests not only a deliberate ignoring of the problem but active steps to hide it - neither of which is the case because people kept bringing it up! Yes, higher-ups were incompetent and stupid and uncaring and probably hoped it would go away if they ignored it but that's a whole world away from an active conspiracy to "silence" things.
One thing to note is that the panoramica usually has very little traffic and zero trucks, so while it might take a bit more time it's usually a less stressful experience.
Meg White is widely regarded as a great drummer by her peers. "Unskilled" is definitely not true: she just plays in a style that is devoid of virtuosity, and it fits the music very well.
Fair assessment. A very skilled artist could use an unskilled style - see Nirvana's cover of Where Did You Sleep Last Night or even John Travolta's dancing in Pulp Fiction.
If you're very much into art, you've probably seen the simple stuff already, and you would prefer to see something that surprises you or makes you think instead of the nth iteration of the same tropes.
But PHP is a tool, and you want your tools to be boring and reliable. (Whether PHP fits the description is a different discussion.)
You'd be surprised. A lot of programmers want complex tools because they are more interesting. They also tend to write unnecessarily complex code.
For example instead of just doing something there are multiple levels of indirection and instead of simply operating on a variable they tend to setup overly complex types that get passed around. Obviously sometimes you need that, but I'm talking about adding this complexity when it's not necessary.
Of course those people exist, and they also exist in PHP land because as soon as you start using its more advanced features it is as complex as the other mainstream languages.
But I would guess that a majority of developers that are not CS researchers value simplicity over complexity, at least in theory. After all they’re just trying to get shit done.
I would argue it’s actually easier to serve content to logged out users as you can cache the whole response and serve it at the edge. Then it “just” becomes a cache expiration problem.
Correct, we push static assets to the edge. However not all SASS products are the same, there is a spectrum of features that can be pushed to the edge and some cannot. The engineering comes from cost, usability, reliability, etc...
The rind can definitely be eaten, and it’s delicious. If you put it in soup like you said it becomes soft and chewy, but you can also grill it or eat it raw on its own (I do sometimes, after cleaning the surface with a knife). My grandma used to say it’s good for your teeth, which is probably not true.
Most people I know (European here) use a mobile banking app. For my bank, the mobile app also serves as 2fa for the website, so it’s impossible not to have it.
In these discussions I rarely see Apple Maps mentioned, but I just checked and MapKit JS includes 25,000 requests per day with a $99 yearly Apple Developer subscription. Considering the cost of the alternatives, even if you don’t care about iOS development, it might be worth it to get one just for MapKit.
I edit metadata for Apple Music stuff all the time, so it is consistent with the other non-Apple Music stuff I have in my library. I also fix capitalization (this is more common in non-English songs, which inexplicably adopt English capitalization standards), the occasional error in old songs (by comparing to scans of physical copies), useless metadata on song/album titles (looking at you, “(2013 Remaster)”), and sometimes the year (for re-releases, I put in the original release year). Then of course sometimes Apple Music overrides my corrections because someone at a record label decided to change the metadata on some song, so I also have to keep track of it using a separate app (“Music Tracker”) that tracks changes to my library (which is also useful to know when something disappears from Apple Music).
I don’t expect normal people to do this, but for me the ability to edit metadata and mix streaming songs with ripped songs is a huge advantage of Apple Music over other streaming services. Unfortunately Apple Music has a lot of other issues, especially with syncing, and I still can’t understand why there’s no dedicated “featuring” metadata field (everyone pollutes the song title: Spotify solved this), but for me there’s no other possible alternative.
