OneLake is Fabric's lake-centric architecture that provides a single, integrated environment for data professionals and the business to collaborate on data projects. Think of it like OneDrive for data; OneLake combines storage locations across different regions and clouds into a single logical lake, without moving or duplicating data. Data can be stored in any file format in OneLake and can be structured or unstructured. For tabular data, the analytical engines in Fabric will write data in delta format when writing to OneLake. All engines will know how to read this format and treat delta files as tables no matter which engine writes it.
any possibility that the apple rep screwed up and unpaired/replaced the wrong pod? i.e your "pair" would now have two pods, neither of which are actually associated with the hardware you have access to
to clarify what I mean: GP lost the right one, but is it possible the replacement pod was never actually associated as the "right" one due to a mixup? In this situation, the charger case would have left and right pods, but neither of them would be associated with the "pair"
The whole timer/alarm app experience in iOS is also the worst of all mobile OS's I've ever used. The best one was in Jolla SailfishOS. In 2014. It was so easy to add/remove/enable/disable multiple timers and alarms. And when they triggered, you could snooze or dismiss it with a simple gesture.
In iOS, you can't even have more than one active timer at a time. Like wtf???
Also, when the timer or alarm clock triggers, you are presented with view containing two buttons (yellow and purple). One of them snoozes, one of them dismisses. Which one is which, you ask? You see, to keep things simple and consistent, the button actions (and labels) switch places depending on whether the view was triggered by an alarm or a timer. Oh! and the label text color is white, which makes it reeeeeeally difficult to tell which of the fucking buttons is which, especially in a rush or in the morning when your eyes are foggy.
I would have replaced this shitty ass app in a heartbeat, except Apples strict controls kneecap all third party apps by preventing them from running in the background...
10 years (?) later, when an alarm goes off in iOS, and I tap/swipe/shove it away, i still never have any fucking idea if it got snoozed or cancelled/stopped, or what I was supposed to do, or what I'll do next time. I mean, yeah, clearly I could spend 2 minutes to research it and try to remember to do the 'right' one next time, but it just never made it into my muscle memory, so I'll keep fumbling with it.
The problem is probably that you don't get immediate feedback of having done the 'right' thing. 9 minutes later, when your alarm goes off again, and you realize "oops, I snoozed it rather than dismissing it", you sure as hell won't remember which action was the 'wrong' one. Especially because you were half awake at the time.
iOS 17 has multiple and named timers, why make a rant when a major part of it is already a non-issue?
To fix your confusion:
Timers - generally considered one time. If you swipe away the notification the timer is finished. If you press the circular arrow button it will restart the timer. Pretty obvious. On the Lock Screen they are clearly labeled as "Done" and "Repeat"
Alarms - by default alarms are set with snooze on. Swiping away will snooze. There is a "ZzZ" and "X" button on the notification. On the Lock Screen they are clearly labeled as "Snooze" and "Stop". If the snooze function is disabled on an alarm the only option is to stop the alarm.
When I posted the comment, iOS 17 had been out... ~1 week? You really think everyone upgrades in lockstep on day 1? I've been annoyed by this for all the 4 years I've used an iphone.
I haven't upgraded yet, so I'm not sure what to make of your comment. But for pre-iOS17 the lock screen notification/dismissal view is anything but "clear" or "obvious"...
1000 cores?? I don't have 100 cores! What do you even need 10 cores for? Well, here's 4 cores. Give 2 to your brother. Don't go wasting all those hyper threads all at once!
The change I suggested is backwards compatible - probably a relatively small change to a single method in parsing.
You, on the other hand, took the pre-existing syntax and contemptuously threw it out the window - and completely ignored the advantage of widespread tacit understanding.
enum Color { green, yellow };
struct Leaf { Color color; };
std::vector<Leaf> tree = {
{ .color = green },
{ .color = yellow },
};
which has the benefit of requiring a massive compiler suite, a specific language version, but it compiles to 0 bytes because it's not used (how great!!)
while that works, it does not fully document what is expected from caller. And AFAIK using tuples like that is not very common. I'd prefer something like: