Wat? Because a century old device can only set a repeating alarm, the 2025 $1k smartphone should, too?! I set so many one of alarms on my android weekly, I would be infuriated if I had to use the calendar for that.
You can set as many non-repeating alarms as you like, as long as they're within the next 24 hours.
What kind of event are you creating an alarm for that's more than a day away? On Friday, do you create your alarm to wake up on Monday? Does Android have a calendar-like view of your upcoming alarms?
(Sorry for the barrage of questions, but this is interesting to me.)
I frequently use one-time alarms for early morning travel a few days away. What makes them great is that the alarms in general are much more robust in their requirements to turn them off; I can accidentally dismiss a calendar alert, but I have a much harder time accidentally deactivating the clock alarm in a sleep induced stupor at odd hours.
More importantly, alarms don't get silenced by my nightly do not disturb schedule.
Github Copilot is likely running models at or close to cost, given that Azure serves all those models. I haven't used Copilot in several months so I can't speak to its performance. My perception back then was that its underperformance relative to peers was because Microsoft was relatively late to the agentic coding game.
> Or is the performance of those models also worse there?
The context and output limit is heavily shrunk down on github copilot[0].
That's the reason why for example Sonnet 4.5 performs noticeably worse under copilot than in claude code.
You can see the difference in 4K when the bitrate is there, but most streaming platforms compress their videos too much for it to be worth it. It's definitely not the jump that 720p to 1080p is, though. I agree with everything else you said.
reply