> laptops left open just so tasks could keep running
Too real. We’re currently still sticking to local agent workflows which feel more powerful than cloud native ones. Moving that to your own cloud with no third-party control plane feels like the right middle ground. Nice work
EDIT: the adversarial two-agent review loop is really clever!
This was actually the first route I considered. Unfortunately the latency was too much.
> My first instinct was to lean on traditional automation stacks: HomeKit scenes to chain “TV on” into “receiver on” or wattage triggers via an Eve Energy plug. This kind of worked, but every extra layer added 30 seconds of lag or more.
Where I talk about the craziness that happens when more than 3 playback devices are on in my system:
> ...if the one playback device (e.g. PS5) was on, changing input to another playback device (e.g. Xbox) was impossible, I'd get a quick black screen and the input snaps back to PS5. This is wild, but fortunately I only use one console at a time so it’s not a big deal.
I remember when I wad losing my mind diagnosing this, I ended up asking ChatGPT for help with deciphering the HDMI-CEC frames when this was happening. It told me about the 3 device limit being the culprit with the line "You’re not crazy, HDMI-CEC is."
One thing that Apple hasn't addressed is if the Geekbench results [1] over-represents or exaggerates the the throttling effect. Since Geekbench pushes the iPhone to its limits for the duration of the benchmark, iOS needs to throttle performance to prevent shutdown while being tested. This results in lower-than-expected test scores every time. But how much does this map to real-life, visible performance drop?
Edit: Another question I have is how do other devices handle battery degradation? Do Android phones just let devices shutdown unexpectedly or is there also performance throttling? Or is the problem non-existent on non-Apple devices somehow?
Back in the days MS used to allow you to create a "Microsoft Account" (MSA) using any email, including an email that's already associated with Azure Active Directory (AAD work or school account).
This was a mistake and has been patched. But it looks like an MSA was created using the same email as your AAD before the fix.
Thus, from MS's perspective, there are two distinct accounts under the same email, hence the UX. It's really quite a mess, and yes the situation is weird. We're working on it make it better.
I'm super curious as well.. 3DR is the original platinum member, Intel and Qualcomm are newer. It seems like all three were collaborating on pivoting towards proprietary drone tech which obviously doesn't sit well with ArduPilot/tridge
The last item is very prevalent throughout many microsoft.com pages. https://azure.microsoft.com has gotten it right here but I'm wondering what's preventing the rest of microsoft.com to do the same.
I went through a similar experience. In hindsight the red flags were extremely obvious but I was also in extreme denial. I really wanted it to be true and was not willing to face whatever I would be able to dig up. So I didn't try. Paychecks were bouncing and I was still clasping onto the sliver of hope in order to not lose the job.
I was (am still am) a new grad with no experience but I had co-workers with families and responsibilities. We all wanted it to be true too badly and willfully ignored the warning signs.
I believe this is a new system. It's called two-factor authentication as opposed to two-step verification. To quote the FAQ:
> Is this different than Apple’s current two-step verification feature?
> Yes. Two-factor authentication is a new service built directly into iOS 9 and OS X El Capitan. It uses different methods to trust devices and deliver verification codes, and offers a more streamlined user experience. The current two-step verification feature will continue to work separately for users who are already enrolled.
Since I was already using two-step verification, I had to turn it off for the new, two-factor authentication, option to appear. I turned it on and it looks like it's working now.
I have to agree that this was very confusing.
EDIT: looks like I can authenticate from OS X now, nice. Before I had to always unlock my phone.
I understand your frustration, but I don't think products trying to compete with closed ecosystems hurts innovation. The smartphone race ushered a new era for software development. The new development process made it mandatory (in order to stay competitive) to reconsider your software for the specific hardware, which promoted some very good redesigns and innovation that would not have happened otherwise.
I think the point Apple is trying to make is a little different than how this article described it.
I don't think anybody would disagree that the tablet form shown in the 1994 video is the natural form a functional tablet would take on: thin, large screen, rectangular, etc. Including Apple.
However, Apple is not happy because, to Apple, it is the first to figure out how to deliver this "natural" form factor in a tablet, and Samsung (and subsequent Android manufacturers), ripped Apple off in the delivery process. I imagine Apple's logic is that no other companies were able to engineer the "optimal" tablet until the iPad came out and they disassembled it and, through imitation, engineered their own. The Android tablets exist because of the iPad.
Which is not unreasonable, honestly. If the thin, rectangular, and large screen form factor is the final product of natural evolution of tablets, how come nothing even came close to it until the iPad came out? How would one explain the the sudden shift in tablet design if the iPad never existed?
If I came up with a way of actually making a hover car (envisioned through countless medias) that works and everyone copied the way I did it, I'd be pretty pissed too.
I'm not good with words as English is not my first language. I hope I got my point across.
Too real. We’re currently still sticking to local agent workflows which feel more powerful than cloud native ones. Moving that to your own cloud with no third-party control plane feels like the right middle ground. Nice work
EDIT: the adversarial two-agent review loop is really clever!