Everything Apple announced at its fall iPhone event, from the foldable iPhone Duo to an always-listening Apple Watch
The main event was the tech giant's highly anticipated first foldable phone, the iPhone Duo.
Latest News Archive - Page 33
Desert Ant Labs
Small specialized AI models for speech, text, vision Discussion | Link
OpenAI gave an AI the power to block its own engineers’ code
Every pull request submitted by an OpenAI engineer now goes through an automated security review, and the AI model can The post OpenAI gave an AI the power to block its own engineers’ code appeared first on The New Stack .
“It could kill us all”: what Anthropic’s own researchers really think about superintelligence
On Tuesday evening, Anthropic pretraining researcher Jacob Coxon announced on X that he’d resigned. Within hours, two of his colleagues The post “It could kill us all”: what Anthropic’s own researchers really think about superintelligence appeared first on The New Stack .
Anthropic built an economic model that frames its CEO's bleakest job forecasts as an outlier scenario
Anthropic published an economic model with three scenarios for the US economy through 2030. In the extreme scenario, output doubles every 4.5 years and knowledge worker unemployment hits 17.9 percent. CEO Dario Amodei's own warnings from May land squarely in that most extreme bucket. The article Anthropic built an economic model that frames its CEO's bleakest job forecasts as an outlier scenario appeared first on The Decoder .
Legal AI startup Harvey reaches $15.5 billion valuation in new funding round - Reuters
Legal AI startup Harvey reaches $15.5 billion valuation in new funding round Reuters
What execs are talking about at Goldman Sachs' Communacopia: AI, data centers, disruption
CoreWeave CEO Mike Intrator spoke to CNBC at the Goldman Sachs' Communacopia + Technology Conference this week.
Vibe Eyes
Put your pets in your macOS menu bar Discussion | Link
Fold the phone: Apple's new CEO unveils a foldable iPhone
New Apple CEO John Ternus announces the iPhone Duo, which folds like a passport and is the most radical iPhone design update in nearly 20 years.
Apple's unveils its first folding iPhone
Apple showed off at an event the first major design change to the iPhone in almost 20 years.
Harvey hits $15.5B valuation, months after reaching $11B
The legal AI startup and VC darling has nearly doubled its valuation in nine months.
Kubernetes v1.37: Introducing Node Lifecycle Conditions
Kubernetes has many ways to describe what is happening on a Node. Readiness, taints, Pod state, labels, annotations, and provider-specific APIs each expose part of the picture. What has been missing is a shared, Kubernetes-owned way to say that a Node is draining , undergoing maintenance, or undergoing Graceful Node Shutdown . Kubernetes v1.37 introduces five well-known Node conditions that provide that description: DrainInProgress Drained MaintenancePlanned MaintenanceInProgress GracefulNodeShutdownInProgress The new Node lifecycle conditions Condition What it reports DrainInProgress The Node is actively being drained according to the administrator's chosen drain criteria. Drained The Node has reached the drain criteria selected by the administrator. MaintenancePlanned The Node is expected to undergo a change in the future. MaintenanceInProgress The Node is actively undergoing maintenance. GracefulNodeShutdownInProgress Graceful Node Shutdown is determined to be in progress on the Node. Maintenance can include hardware or software rollout, remediation, decommissioning, or debugging. Whether maintenance requires a drain depends on its impact. A Kubernetes upgrade usually should follow a drain, while a kernel live patch might not need one. Like other Node conditions, each lifecycle condition uses status to report whether the observation is active: True : the lifecycle state is currently observed. False : the lifecycle state is not currently observed. Unknown : Kubernetes cannot determine whether the lifecycle state is active. The reason provides a stable, machine-readable cause for the current status, and message can provide additional human-readable detail. For example, an authorized maintenance controller could publish: # Node .status excerpt status : conditions : - type : MaintenancePlanned status : "True" reason : MaintenanceWindow lastTransitionTime : "2026-12-09T12:00:00Z" message : "Hardware maintenance is scheduled for this Node" What changes in Kubernetes v1.37 The v1.37 release reserves these names as well-known NodeConditionType constants and introduces the Alpha NodeLifecycleConditions feature gate, which is disabled by default. In v1.37 the gate is effectively a no-op: it does not restrict who can set these conditions, and no core component reads them. It exists so that the built-in behavior planned for future releases — controllers that consume these conditions — can be opted into when it arrives. You do not need to enable it to start publishing the conditions today. For this release, an administrator or an administrator-authorized controller is responsible for setting and clearing the lifecycle conditions. In this first release, no core workload controller changes its behavior based on these conditions, but an administrator can publish them to communicate maintenance and drains to cluster users. How to use lifecycle conditions today The immediate value is operational clarity. Administrators and lifecycle automation can use these conditions as a common status channel for Node lifecycle work that already happens today. For example, maintenance automation can set MaintenancePlanned when a future maintenance window is scheduled, then set MaintenanceInProgress when work starts. Drain automation can set DrainInProgress when it begins evicting Pods and Drained when the administrator's selected drain criteria have been met. The GracefulNodeShutdownInProgress condition can report that Graceful Node Shutdown is in progress on the Node. The recommended pattern is to use lifecycle conditions to report status, while lifecycle operations are managed through other mechanisms. Continue to use existing Kubernetes mechanisms such as kubectl cordon , kubectl drain , taints , and workload-specific controls to change scheduling or eviction behavior. Use lifecycle conditions to make the state of that work visible to people, dashboards, alerts, and automation that choose to consume the signal. When setting a condition, use True while the lifecycle state is active. Set the condition to False , or remove it, when the state is no longer active. Use a stable reason value and a clear message so that both people and automation can understand why the condition changed. Cluster administrators should also decide which component owns each lifecycle condition to avoid conflicting writes. Why a shared signal matters Node lifecycle affects components across the cluster. The kubelet , node lifecycle controller, workload controllers, scheduler, autoscalers, storage operators, and external maintenance systems all need some understanding of what is happening to a Node. Today, each component has to reconstruct that understanding from indirect signals. One controller might look at Node readiness, another at taints, and another at Pods that are terminating or missing. Infrastructure providers and operators often add their own labels or annotations. Those signals remain useful for their intended purposes, but they do not answer the same question. A taint can influence scheduling or eviction, for example, but it does not attest that a drain is in progress or that an administrator's drain criteria have been met. A NotReady Node does not explain whether the cause is an unexpected failure, a graceful shutdown, or planned maintenance. Without shared lifecycle context, independently correct components can make conflicting decisions. A DaemonSet controller can replace a Pod that the kubelet intentionally terminated during graceful shutdown. A Job controller can wait indefinitely for a terminal Pod phase on a Node that an administrator is removing. A storage operator might learn about maintenance only after drain has already started. The new conditions provide a stable place on the Node for that missing context, as part of the larger effort to enhance Node Lifecycle management . The foundation for lifecycle-aware Kubernetes The value of a shared signal comes from what can consume it — core controllers, administrators, or the ecosystem of lifecycle projects. Follow-up enhancements can build on the conditions without every component inventing a different way to infer Node lifecycle state. Consider a long-standing DaemonSet rollout edge case. A Node that is broken or undergoing maintenance can remain unavailable for reasons unrelated to the new DaemonSet revision. That Node still consumes the rollout's availability budget, which can slow or block the controller from progressing the rollout on healthy Nodes. The DaemonSet controller knows that a Pod is unavailable, but it cannot tell whether the new revision failed or an administrator intentionally took the Node out of service. Readiness, taints, and Pod state expose pieces of the situation, but none provides authoritative maintenance context. The MaintenanceInProgress condition creates a Kubernetes-owned place to publish that context. Future work can define how the DaemonSet controller uses it for rollout ordering, availability accounting, and status reporting. Those behaviors still require careful design, but the goal is for administrators to no longer have to manually adjust the rollout. Future expansions and getting involved Node lifecycle is a cross-cutting problem. Solving it starts with components sharing enough context to make compatible decisions. The next stage is to build on Node Lifecycle Conditions to improve scenarios such as Graceful Node Shutdown, drain, and maintenance. Longer-term lifecycle coordination may require explicit ownership, locking, and potentially a dedicated API. The Kubernetes ecosystem already includes many solutions for Node maintenance, remediation, drain, autoscaling, and fleet management. The experience behind those projects is essential to building a foundation that works across different environments and operational models. The Node Lifecycle Working Group, SIG Node, and SIG Apps invite maintainers and users to share their use cases and ideas to shape the future work. Follow the work through KEP-5683: Node Lifecycle Conditions . To participate in our discussions, join one of our groups: Node Lifecycle Working Group SIG Node SIG Apps
U.S. Disrupts Xinbi Guarantee Scam Marketplace, Freezes $52.8 Million in Crypto
The U.S. Department of Justice (DoJ) on Wednesday announced coordinated actions aimed at an illicit online marketplace called Xinbi Guarantee that offered scam services, including seizing Telegram channels used to run the service, confiscating two cryptocurrency wallets, and deploying the Scam Center Strike Force to Madagascar to help disrupt 13 scam compounds run by Chinese organized crime
Air traffic failure was avoidable, says transport secretary
Heidi Alexander orders an investigation into the glitch that caused more than 2,000 flight cancellations.
Uganda to withdraw from Invictus Games ‘out of respect for King Charles’, says military chief
Gen Muhoozi Kainerugaba announces decision to pull out in post on X, citing tensions over ‘Harry-Meghan nonsense’ Uganda is withdrawing from the Duke of Sussex’s Invictus Games, the country’s military chief has said, out of respect for King Charles amid division over the “Harry-Meghan nonsense”. Gen Muhoozi Kainerugaba, son of the Ugandan president, made the surprise announcement in a post on X on Wednesday. Continue reading...
iPhone Duo
Article URL: https://www.apple.com/newsroom/2026/09/apple-unveils-iphone-duo/ Comments URL: https://news.ycombinator.com/item?id=49630964 Points: 322 # Comments: 6
iPhone Duo
Article URL: https://www.apple.com/iphone-duo/ Comments URL: https://news.ycombinator.com/item?id=49630931 Points: 1189 # Comments: 2101
Chrome for Android Update
Hello Everyone! We've just released Chrome 154 (154.0.8037.21) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here . This release includes stability and performance improvements. You can see a full list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Krishna Govind Google Chrome
19.3.0 (September 9, 2026)
Below is a list of all new features, APIs, and bug fixes. Read the React 19.3 release post for more information. New React Features <ViewTransition /> : Adds <ViewTransition /> and addTransitionType APIs to power View Transition animations in React ( @sebmarkbage , @jackpope , @gaearon : #31975 , #31987 , #31996 , #31999 , #32001 , #32002 , #32028 , #32029 , #32031 , #32034 , #32038 , #32041 , #32050 , #32090 , #32105 , #32254 , #32379 , #32422 , #32462 , #32540 , #32545 , #32585 , #32599 , #32611 , #32612 , #32617 , #32651 , #32653 , #32656 , #32664 , #32699 , #32723 , #32734 , #32751 , #32752 , #32760 , #32761 , #32764 , #32772 , #32790 , #32819 , #32820 , #32822 , #32833 , #32849 , #33094 , #33191 , #33200 , #33206 , #33293 , #33330 , #33331 , #33332 , #33357 , #33362 , #33433 , #33576 , #34374 , #34450 , #34481 , #34500 , #34502 , #34510 , #34511 , #34539 , #35567 , #35564 , #35485 , #35380 , #35063 , #35060 , #34676 , #36917 , #35337 , #35520 ) Fragment Refs: Add Refs to <Fragment /> to support composable platform behavior ( @jackpope , @sebmarkbage , @eps1lon , @Dhakshin2007 , @chirokas , @teamleaderleo , @fallintoplace : #32465 , #32613 , #32619 , #32654 , #32660 , #32682 , #32722 , #32813 , #32814 , #33056 , #33058 , #33093 , #34069 , #34103 , #34544 , #34545 , #37062 , #37061 , #37060 , #36047 , #36010 , #35642 , #35641 , #35637 , #35630 , #34935 , #37457 , #37408 , #37326 , #37251 , #37171 , #37169 , #37168 , #37167 , #37166 , #37165 , #37164 , #37163 , #37162 , #37161 , #37160 , #37125 , #37063 ) New React DOM Features browser() : a new react-dom API that returns a usable which errors during server rendering and resolves in the browser. use(browser()) inside a <Suspense> boundary marks a subtree as browser-only without reporting a recoverable error ( @gnoff : #37143 , #37241 ) Added an onBrowserBailout option to the react-dom/server APIs to observe when a subtree defers to the browser ( @gnoff #37193 ) Notable changes Enable Trusted Types API integration ( @rickhanlonii #35816 ) Transitions now render independently instead of being entangled into a single render, so a slow transition no longer holds up unrelated ones ( @acdlite #37290 ) Added a DEV-only warning when a component appears to have been unblocked by calling use() conditionally ( @hoxyq , @eps1lon : #37104 , #37203 , #37491 ) All Changes React Fast Refresh Fixes Fix Fast Refresh to find and remount edits to components wrapped behind lazy() ( @sophiebits #36965 ) Fix Fast Refresh so edits to a memo() comparison function take effect ( @sophiebits #36964 ) Fix Fast Refresh crash when an edit changes the kind of a component's type ( @sophiebits #36963 ) Unify hot reload type resolution for Fast Refresh ( @sophiebits #36962 ) Fix Fast Refresh to remount correctly when an edit changes the component kind ( @sophiebits #36950 ) Double invoke effects in StrictMode after Fast Refresh ( @eps1lon #35962 ) Performance Track Fixes Prevent crash when accessing $$typeof in Performance Tracks ( @eps1lon #35679 ) Handle non-string function names in Performance Tracks ( @eps1lon #35659 ) Use minus ( - ) instead of en dash for removed props in Performance Tracks ( @eps1lon #35649 ) Handle arrays with bigints in deep objects in Performance Tracks ( @eps1lon #35648 ) Don't enumerate typed array props in Performance Tracks in DEV ( @UditDewan #36913 ) Bail out of diffing wide objects and arrays in Performance Tracks ( @eps1lon #34742 ) Clear potentially large performance measures in DEV ( @hoxyq #34803 ) Fix missing else branch for renders with no props change in Performance Tracks ( @hoxyq #34837 ) Activity Fixes Fix useSyncExternalStore missing store mutations that happened while an Activity tree was hidden ( @sophiebits #36947 ) Hide portal contents when an Activity is hidden ( @acdlite #35091 ) Prevent metadata hoisting in hidden <Activity> trees ( @ronnakamoto #34983 ) Prevent errors thrown inside a hidden Activity from escaping to the visible UI ( @acdlite #35074 ) Don't unhide a node if a direct parent Offscreen is still hidden ( @sebmarkbage #34821 ) Don't show internal <Offscreen> component in error messages ( @rickhanlonii #35763 ) Warn in DEV when a component appears to have been unblocked by a conditional use() ( @hoxyq , @eps1lon : #37104 , #37203 , #37491 ) Render transitions independently instead of entangling them into a single render ( @acdlite #37290 ) Fix hang when updating a dehydrated boundary inside a hidden tree ( @gaearon #37135 ) Don't reacquire Host Singletons during dev effect validation ( @gnoff #37113 ) Only remove properties from Host Singletons on release ( @gnoff #37112 ) Don't invoke effects on moved children in StrictMode ( @sophiebits #36948 ) Throw a clearer error when a rejected Promise is incorrectly instrumented ( @eps1lon #36328 ) Fix context propagation into Suspense fallbacks ( @acdlite #36160 ) Fix context propagation through suspended Suspense boundaries ( @acdlite #35839 ) Fix useDeferredValue getting stuck ( @gaearon #36134 ) Update useActionState error message to say "action state" instead of "form state" ( @rickhanlonii #35790 ) Don't warn when rendering data block scripts ( @eps1lon #35953 ) Treat fibers with alternates as mounted in getNearestMountedFiber ( @sebmarkbage #35578 ) Always instrument the lazy initializer thenable ( @gnoff #35521 ) Annotate cascading updates for DevTools performance tracks in DEV ( @huntie #34961 ) Resolve the .default export of a React.lazy as the canonical value ( @sebmarkbage #34906 ) Limit owner stacks to 10 frames ( @eps1lon #34864 ) Ensure useEffectEvent reads latest values in forwardRef and memo() components ( @eps1lon #34831 ) React DOM Copy source onto the synthetic toggle event ( @lazerg #37389 ) Update HTML parser rules for the new <select> parser ( @josepharhar #34804 ) Update defaultValue for type="number" inputs to match other input types ( @sophiebits #36980 ) Avoid setting innerHTML when it hasn't changed ( @sophiebits #36949 ) Forward the nonce option in ReactDOM.preloadModule() ( @UditDewan #36851 ) Support fetchPriority for module resources ( @TheAlexLichter #36835 ) Track stylesheet preloads when explicitly preloaded to avoid unnecessary suspension ( @gnoff #36386 ) Suggest correct casing for the misspelled credentialless iframe attribute ( @vmx906 #36322 ) Add credentialless as a recognized boolean attribute for iframes ( @vmx906 #36148 ) Prevent reentrant finishedTask from calling completeAll multiple times ( @gnoff #36287 ) Update the CSS shorthand property list ( @kidonng #35636 ) Support the maskType SVG prop ( @sleitor #35921 ) Add support for onFullscreenChange and onFullscreenError events ( @chirokas #34621 ) Include submitter in submit events ( @eps1lon #35590 ) Fire onReset when automatically resetting forms ( @eps1lon #35176 ) Use the FormData submitter parameter ( @jenseng #29028 ) Fix form status reset when component state is updated ( @eps1lon #34075 ) Batch updates from resize events until the next frame ( @eps1lon #35117 ) React Server Add nonce to rendered import maps ( @mattcosta7 #37339 ) Add an onBrowserBailout option to observe subtrees that defer to the browser ( @gnoff #37193 ) Stop the caller's signal from retaining a finished render ( @unstubbable #37315 ) Construct the render lifetime controller only when it is needed ( @unstubbable #37357 ) Fix react-dom/server hanging on Deno ( @fraidev #35235 ) Extend stack overflow recovery to retries in SSR ( @jackpope #36977 ) Fix false-positive hydration mismatch on nonce attributes ( @MaxwellCohen #37030 ) Guard shell-error callbacks instead of nulling them out on the request ( @eps1lon #36916 ) Stop firing onAllReady after the shell errored ( @eps1lon #36903 ) Treat an incomplete tree as an error during error recovery ( @acdlite #36911 ) Fix non-script modulepreload tracking ( @fallintoplace #36564 ) Finalize postponed nextSegmentId after the prelude flush ( @gaojude #36779 ) Preserve referrerPolicy in image preload headers ( @ulises-jeremias #36803 ) Allow pending work to specialize abort reasons ( @gnoff #36586 ) Abort tasks that suspend after aborting during render ( @gnoff #36585 ) Finish abort in a scheduled task ( @gnoff #36580 ) Fix aborts during resumed rendering ( @gnoff #36584 ) Track abort state on the request ( @gnoff #36583 ) Model external work scheduling explicitly in the fb bundle ( @gnoff #36576 ) Continue reporting aborted task errors after a fatal abort ( @gnoff #36575 ) Disallow abort reentrancy ( @gnoff #36574 ) Stop transpiling computed property names ( @eps1lon #36542 ) Fix crash when capturing the callsite of a stalled use() of a rejected Flight chunk ( @lubieowoce #36544 ) Double invoke effects in Strict Mode during hydration ( @eps1lon #35961 ) Add additional task reentrancy protections in Fizz ( @gnoff #36291 ) Don't outline Suspense boundaries with suspensey CSS during shell flush ( @gnoff #35824 ) Push a stalled use() to the owner stack and debug task ( @eps1lon #35226 ) Fix useId tracking on replay ( @gnoff #35518 ) Correctly handle replaying when hydrating ( @gnoff #35494 ) Simplify the createSuspenseBoundary path ( @sebmarkbage #35087 ) Unify preamble-only fields to save a field on Suspense boundaries ( @sebmarkbage #35068 ) Unify prerender-only fields to save a field on Suspense boundaries ( @sebmarkbage #35067 ) Push halted awaits to the owner stack for late-arriving I/O info ( @unstubbable #35019 ) Include all Node.js APIs in the Bun entrypoint for react-dom/server ( @RiskyMH #34193 ) Detach a Suspense boundary after flushing its segment ( @gnoff #34694 ) React Server Components Keep an element pending while a referenced row is resolving ( @unstubbable #37542 ) Fix RangeError from exponential debug info growth ( @unstubbable #37481 ) Abort the cache signal when debug objects are retained ( @unstubbable #37342 ) Transfer key validation of lazy nodes when they are unwrapped ( @unstubbable #37258 ) Add pending_weak to the Flight thenable protocol ( @acdlite #37154 ) Outline and dedupe repeated strings ( @gaearon #37147 ) Port Reply Server traversal guards to the Flight Client ( @eps1lon #37144 ) Define Flight chunk .then with Object.defineProperty ( @eps1lon #37109 ) Support Turbopack's experimental array format for chunks ( @sampoder #37095 ) Limit fake JSX call site stacks to 10 frames ( @timneutkens #37086 ) Improve performance when decoding Flight replies ( @gnoff #37090 ) Recognize Node 22+ V8 frames for Promise statics in debug info ( @gaearon #36969 ) Tailor the warning for binary data serialized through toJSON (Node Buffer ) ( @unstubbable #36873 ) Resolve models before JSON.stringify for faster serialization ( @mhart #36795 ) Prune debug info when chunks error ( @gnoff #36782 ) Avoid main-thread stalls from large debug strings ( @unstubbable #36570 ) Fix stranded row content under Node stream backpressure ( @unstubbable #36516 ) Fix dropped FormData entries in decodeReplyFromBusboy ( @unstubbable #36468 ) Harden types and improve performance of Flight replies ( @eps1lon #36425 ) Add more cycle protections to Flight replies ( @eps1lon #36236 ) Transport AggregateError.errors ( @eps1lon #36156 ) Bail out early when a backing entry for Blob deserialization is not a Blob ( @eps1lon #36055 ) Clear chunk reason after successful module initialization ( @unstubbable #36024 ) Add support for transporting Error.cause ( @eps1lon #35810 ) Walk parsed JSON instead of using a reviver for faster RSC payload parsing ( @timneutkens #35776 ) Skip transferReferencedDebugInfo during debug info resolution ( @unstubbable #35795 ) Add unstable_allowPartialStream option to Flight Client ( @unstubbable #35731 ) Fix encodeReply for JSX with temporary references ( @unstubbable #35730 ) Fix debug channel flag in Node.js renderToPipeableStream ( @feedthejim #35724 ) Fix stack overflow in visitAsyncNode with deep async chains ( @unstubbable #35612 ) Allow Server Components to render context providers from client modules ( @rickhanlonii #35675 ) Allow overriding request.timeOrigin via options.startTime ( @lubieowoce #35598 ) Warn once if eval is disabled in the dev environment ( @eps1lon #35661 ) Restore original function name in dev server callstacks served with unsafe-eval ( @eps1lon #35650 ) Fix react-markup types for server references ( @eps1lon #35634 ) Add more DoS mitigations to Flight replies and harden Flight ( @unstubbable #35632 ) Allow cyclic references to be serialized when unwrapping lazy elements ( @unstubbable #35471 ) Improve cyclic thenable detection in Flight reply server ( @cvan20191 #35369 ) Add extra loop protection to Flight reply server ( @sebmarkbage #35351 ) Patch Promise cycles and toString on Server Functions ( @sebmarkbage #35345 ) Move react-server-dom-webpack/*.unbundled to private react-server-dom-unbundled ( @eps1lon #35290 ) Never parse then functions in Flight replies ( @sebmarkbage #35289 ) Patch Flight reply server with fixes from Flight Client ( @sebmarkbage #35277 ) Complete the list of Node.js internal Promise awaits ( @eps1lon #35161 ) Reduce risk of maximum call stack exceeded when emitting async sequences ( @eps1lon #35159 ) Fix pending chunks count for streams and async iterables in DEV ( @unstubbable #35143 ) Fix broken byte stream parsing caused by buffer detachment ( @unstubbable #35127 ) Fix hasReadable flag in Node.js clients' debug channel ( @unstubbable #35039 ) Fix debug info filtering to include later resolved I/O ( @unstubbable #35036 ) Cache the value when visiting the same I/O or Promise along different paths ( @sebmarkbage #35005 ) Clone subsequent I/O nodes when resolved more than once ( @sebmarkbage #35003 ) Fix hang after resolving cyclic references ( @unstubbable #34988 ) Allow passing DEV-only startTime as an option ( @sebmarkbage #34912 ) Ignore bound-anonymous-fn resources as they're not considered I/O ( @sebmarkbage #34911 ) Fix detached ArrayBuffer error when streaming typed arrays ( @unstubbable #34849 ) Exclude RSC stream if the stream resolves in a task ( @sebmarkbage #34838 ) Forward the current environment when forwarding I/O entries ( @sebmarkbage #34836 ) Look for moved debug info when logging component performance track ( @sebmarkbage #34839 ) Respect displayName of Promise instances on the server ( @sebmarkbage #34825 ) Avoid unnecessary indirection when serializing debug info ( @unstubbable #34797 ) Fix preload as attribute for stylesheets ( @unstubbable #34760 ) Don't serialize toJSON in debug path and omit wide arrays ( @sebmarkbage #34759 ) Add support for <Activity> ( @eps1lon #34697 )
Two zones or three? A design framework for zone-resilient Azure workloads
Zone resiliency isn't a single number you apply to a whole workload. The useful question isn't “how many zones?” but “how many zones does each component need to survive the loss of one?” Decide zone patterns component by component, use service-managed zone redundancy wherever it fits, and reserve three-zone designs for the components that genuinely require a third failure domain. The post Two zones or three? A design framework for zone-resilient Azure workloads appeared first on Microsoft Azure Blog .
Early Stable Update for Desktop
The Stable channel has been updated to 154.0.8037.17/.18 for Windows. Mac is coming shortly , as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log . You can find more details about early Stable releases here . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
AirPods 5
Article URL: https://www.apple.com/newsroom/2026/09/apple-introduces-airpods-5-with-best-in-class-open-ear-active-noise-cancellation/ Comments URL: https://news.ycombinator.com/item?id=49630253 Points: 379 # Comments: 305
HelmGuard Raises $7.3 Million for Agentic GRC and Security
The company will increase its US market presence and will expand its engineering and go-to-market teams. The post HelmGuard Raises $7.3 Million for Agentic GRC and Security appeared first on SecurityWeek .
Google picks Finland for its largest single investment in Europe
The US tech giant says the €13bn data centre project will create tens of thousands of jobs.