
"Disagreement is inevitable, but division is a choice." youtube.com/watch?v=J-bNlt7H…

Dad. Husband. Commercial Pilot. Engineer. Productivity Applications at .

"Disagreement is inevitable, but division is a choice." youtube.com/watch?v=J-bNlt7H…

They .keyx format spec and Python library also now live! github.com/apple/creator-stu… Use it in Python with: pip install creator-studio-doc-format
Live now in the App Store!

Exciting new updates in Apple Creator Studio are here! 🎥 MotionVFX in Final Cut Pro 🎶 Redesigned Browser in Logic Pro 📷 Generate Fill in Pixelmator Pro 💡 Intelligent assistants in Pages, Numbers, and Keynote … and so much more!

Live now in the App Store!
Huge day for Creator Studio today. Our new in-app assistants can help you get things done in record time. MCP allows you to bring your own agent if you want. And an open source format for Keynote (and Python library!) so you can create Keynote documents programmatically on any platform. Super proud of the team. Hope you love it!

Omg the first two paragraphs are insane!
Good morning! Grand Theft Auto VI is one of the greatest games I have ever played. Review: bloomberg.com/news/features/…



Wow. Talk about a bad day.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.

You're not gonna believe this, but @SpaceX caught their Starship rocket at 4:20 PM ET 😂

THEY DID IT!
Starship landing burn in 8 min: x.com/i/broadcasts/2brajgZlO…

Starship landing burn in 8 min: x.com/i/broadcasts/2brajgZlO…

security.apple.com/blog/secu… Please read about the secure OS that we worked on for many years. I am very proud of our work here. We are pushing memory safety and components based OS architecture further here to achieve better security.

it's shocking that software engineering has transitioned to 100% AI written in such a short time. it's more shocking that somehow we, the SWEs, are all just continuing on as if nothing happened. It writes C++ better than I ever could, but the problem of making sure it works didn't magically disappear. we are just shipping enormously more volume at higher quality.

They've genetically traced these ants back to a single colony in Argentina. A couple of the queens were shoveled up in soil that was used for ballast in ships that got dumped in Mobile. And now all fire ants in the US are part of that same family.
The spread of fire ants in the US. You can thank someone from Mobile, AL for bringing this into our country in 1918.

18 of the 20 best open models today are Mixture-of-Experts. Dense is basically over. And yet the know-how to train a good MoE still lives mostly in the heads of a handful of teams. So we spent 800k GPU hours running the experiments ourselves and wrote everything down. Super happy to finally release "The Ultimate MoE Training Handbook", free and open, organized around the questions training teams hit: - how many experts, how big, shared or not? - why is half my step spent in all-to-all, and how do I hide it? - why is my run 25x slower with no error in the logs? - softmax, sigmoid or sqrt(softplus) router, and why keep it in fp32? - aux loss or DeepSeek's loss-free bias? - upcycle a dense checkpoint or train from scratch? - can I serve with fewer experts per token than I trained with? ⚠️ Warning: it's long (~70k words, budget a few days, sorry) but with 55 interactive figures, code you can run and numbers from our own runs. Read it here: huggingface.co/spaces/huggin…

Omg such a good moment
L’une des scènes de l’année. Merci Christopher Nolan pour ce banger.