johnthuss

All your base are belong to us!

The Google Maps situation is a great example of why this will be hard. When Apple switched to their own maps it was a huge failure resulting in a rare public apology from the company. In order to switch you have to be able to do absolutely everything that the previous solution offered without loss of quality. Given Google's competence in AI development that will be a high bar to meet.

The ChatGPT integration was heavily gated by Apple and required explicit opt-in. That won't be the case with the Gemini integration. Apple wants this to just work. The privacy concerns will be mitigated because Apple will be hosting this model themselves in their Private Cloud Compute. This will be a much more tightly integrated solution than ChatGPT was.

The biggest NEW thing here is that this isn't white-labeled. Apple is officially acknowledging Google as the model that will be powering Siri. That explicit acknowledgment is a pretty big deal. It will make it harder for Apple to switch to its own models later on.

All while Waymo is expanding to more and more cities, including Detroit where it will deal with snow and ice. Waymo is years ahead of Tesla in the self-driving race. It's possible Tesla never succeeds in launching a truly self-driving car.

>>> Apple TV+ is now simply Apple TV, with a vibrant new identity.

It's not the main point of the article, but it is there.

Amazon has their own PaaS offering called Elastic Beanstalk, with support for running docker containers and other popular platforms. It's not complicated to set up and is customizable if you need to tweak things. Any idea how Flightcontrol compares to this?

This is a fantastic article! It's really eye-opening to someone like me who wasn't aware of these changes. Great job!

Finally! This is incredibly good news. I hope the adoption of this feature is fast - looking at you Safari.

The use case I have encountered was for anonymous users where the company wanted to prevent unauthorized clients (copies of the app) from relying on the same server-side HTTP API used by the official app. The point wasn't to make it impossible for an unofficial to be used, but to make it harder than "trivial".

So the app used a digital signature / request signing with a key that was obfuscated and embedded in the binary. With anonymous users I don't know how else you could avoid use of the private API.

There are occasions where you just want to make it a little harder to impersonate an official client where it can be useful to store a secret in the binary. It's still vulnerable but requires intention and actual effort.

garble actually sounds like an excellent utility to add some protection around things like keys/secrets in a binary. Is there anything like this for Swift binaries?