249 karma · joined July 15, 2016
It's important to keep in mind that Apple, being a business, is doing exactly what the primary function of a business is - making money. Reducing tax burden is effectively making money they otherwise wouldn't have.
So while as a consumer and citizen I'm happy that Apple is being held to account, I agree with your concern that not even Apple, having gone to such lengths to ensure that such an approach is ostensibly a legal and legitimate method of doing business, can effectively have the authority turn around and say "We change our mind, you owe us fourteen billion dollars." It creates much uncertainty in the legal and administrative processes.
I would prefer to see them simply close the hole for future endeavours.
The same can't really be said of AI in most other contexts, where the goalposts continually seem to move to whatever is currently just beyond our reach.
I found the tool to be fast, comprehensive, and the partial migration was very effective.
And this is exactly why we're running out of publically available IPv4 addresses.
All the data supplied comes from Apple's records, not your phone. If your phone was destroyed one day, and law enforcement requested this information the next, Apple would have no issue supplying it. They're not going to simply "not keep" records of your iTunes transactions and account details, for example.
Your complaints regarding the inability to use their product in a meaningful manner without letting Apple collect this data have merit.
Changing Linux files that are stored in C: and are accessed in Windows from C: and in Linux from /mnt/c/ is fine.
When I started out here in Australia I asked for very little, comparatively, and got an equivalent amount of work. It wasn't until I asked for more than I thought I was worth that people actually started hiring me.
Demanding that I execute all these instructions without exception is like a subscription service sending me a newsletter in the mail and demanding that if I pick it up, I've somehow agreed to read the whole thing, beginning to end, out loud. Absurdity.
I think we're all just waiting for people to really test its performance under heavy loads and give it a chance to prove itself (or not).
Reasons to include inefficient code for compatibility reasons might include applications where maximum reach is valuable, or where the scale is so large that the "infinitesimal market share" percentage plays out into thousands of end users.
One thing I don't like is that their Android client which supports push notifications (a feature I personally valued in Gmail) also has some weird UX.
For example, the message actions bar within the "view message" pane. At first, I wasn't aware it existed. I thought you had to archive/delete messages from the inbox by swiping it! I only discovered it by accident when my finger missed a link in an email. It seems like it appears when you tap somewhere in the message itself, and it appears over the top of the bar that holds the message title and the back arrow.
Very silly in that regard, but otherwise quite solid. Their servers, service, and desktop offering are great and I found their pricing quite reasonable.
I don't believe it's accurate to say there's "no real reason", it seems like enforcing this behaviour is very much aligned with the goal you've posited.
This is under the assumption that this was indeed done for the purpose of ensuring Intel specific drivers are used for power management purposes.