今日已更新 380 条资讯 | 累计 41154 条内容
关于我们

标签:#an

找到 3036 篇相关文章

AI 资讯

In a swipe at Tesla, Waymo says ‘cameras… aren’t enough’

As Tesla gears up for the official launch of its steering wheel and pedal-less Cybercabs, Waymo is issuing a stark warning about Elon Musk's approach autonomous driving. Srikanth Thirumalai, Waymo's VP of Onboard Software, doesn't specifically call out Musk or Tesla in a blog post, published Wednesday, entitled "10 AI Lessons from Driving 200+ Million […]

2026-08-27 原文 →
AI 资讯

Insert Molding Design: How to Place Metal Inserts Without Disaster

Insert Molding Design: How to Place Metal Inserts Without Disaster — 8 Years of Structure Design Notes Every structure designer has been burned by inserts at some point — a nut seated crooked, an insert causing sink marks or cracks, pull-out force too low, an insert washed away by melt during injection. I've tripped on all of these myself. Insert molding sounds simple: drop a metal part into the mold and inject plastic around it. But metal and plastic have thermal expansion coefficients an order of magnitude apart, and every detail — shrinkage, grip force, locating method — can turn into a disaster. This article walks through the key design principles of insert molding, from insert types and locating structures to wall thickness and defect prevention. All of it is experience paid for with real money on real projects. Three Common Types of Inserts Insert molding falls into three categories by purpose, each with completely different design priorities. 1. Thread Inserts (Nut Inserts) The most common type. Tapping threads directly into plastic fails fast — fine threads under M3 strip after a few cycles — so metal nuts are embedded in the plastic. Copper inserts dominate because copper conducts heat well (fast heat dissipation during molding), has moderate hardness, and gives clean threads after tapping. We made a portable Bluetooth speaker with an ABS housing whose four corner posts needed M2.5 screws. Tapping the plastic posts directly stripped after three cycles. We switched to embedded M2.5×4mm copper nuts and measured over 45N pull-out, still stable after 500 screw cycles. The key: leave at least 1.5mm of plastic wall around the nut's outer diameter, or the area sinks and bubbles after cooling. 2. Locating / Support Inserts These locate, support, or conduct magnetism — locating pins in motor brackets, magnetic cores in sensor housings. The biggest challenge is insert positioning accuracy and post-molding offset. In 2024 we made a smart lock panel embedding a stainle

2026-08-27 原文 →
AI 资讯

How to Make Testing More Sustainable

By using a sustainable testing strategy, you can skip unnecessary tests, ensure failing fast and early, and only run tests affected by code changes. Tracking energy use per test and using static code analysis can help spot inefficiencies and guide optimization efforts. By Ben Linders

2026-08-27 原文 →
AI 资讯

Two Alleged ‘TeamPCP’ Hackers Arrested in Australia

Authorities in Australia have arrested two men believed to be members of TeamPCP, a prolific cybercrime and data extortion group blamed for perpetrating the longest running spree of software supply chain attacks ever. In a statement released today, the Australian Federal Police (AFP) said two unnamed suspects from Western Australia, aged 21 and 23, were arrested in connection with a "sophisticated cybercrime syndicate that allegedly created malicious open-source software to rob thousands of global businesses." The AFP did not name the defendants, but KrebsOnSecurity learned the 21-year-old suspect's real identity in June, and has been communicating with him ever since. This story includes interviews with TeamPCP's self-described spokesperson, and examines clues left behind by the TeamPCP leader that likely led to his undoing.

2026-08-27 原文 →
AI 资讯

Is Slate Auto’s new electric truck the EV Americans need?

EVs account for under 10% of total new-vehicle sales in the US, and the numbers are declining. From a climate perspective, that’s pretty dismal, especially because the transportation sector is the single biggest source of greenhouse-gas emissions in the country. One thing that could help turn that around? Slate Auto’s new truck—a vehicle that seems…

2026-08-27 原文 →
AI 资讯

validateHttp() Has No Async Machinery: A Trace From Signal Forms Down to fetch() 🔍🚀

Let's be honest: async validation is the part of any forms library where you brace yourself. Debouncing, cancelling the request the user just invalidated by typing another character, keeping a "checking..." spinner honest, not letting a slow response overwrite a fast one. Every library that has ever done this has grown a pile of bespoke machinery for it. So when Signal Forms shipped validateHttp() and it just worked, I wanted to see the pile. I opened the source expecting a few hundred lines of async bookkeeping, and instead found a function whose entire body is a single call to something else. That turned into a trace all the way down, from a form field to the line where bytes actually leave the browser. Six layers, and only two of them add anything you could call new async machinery. ✅ Availability: validateHttp() is @publicApi 22.0 , stable. Every source reference in this article is pinned to the v22.1.1 tag , so the line numbers stay valid even as main moves. 🧩 The View From Outside The usage is unremarkable, which is the point. You declare that a field validates against an endpoint, and you're done: const schema = form ( this . model , ( path ) => { validateHttp ( path . username , { request : ({ value }) => `/api/username-available?u= ${ value ()} ` , debounce : 300 , onError : () => ({ kind : ' server-unreachable ' }), onSuccess : ( res : { available : boolean }) => res . available ? undefined : { kind : ' username-taken ' }, }); }); Sync validators run first, the request waits until they pass, field().pending() is true while it's in flight, and typing again cancels the previous call. If you've read Part 3 of my Signal Forms series , that's the behaviour contract you already know. The question here is who implements it. 🔍 Layer 1: validateHttp() Is a Delegation Here is the whole function, from validate_http.ts : export function validateHttp ( path , opts ) { validateAsync ( path , { params : opts . request , debounce : opts . debounce , factory : ( request )

2026-08-27 原文 →
AI 资讯

EU Roam Like at Home Now Covers Moldova and Ukraine: What Businesses Should Review

The European Union's Roam Like at Home regime now extends to Moldova and Ukraine, broadening the area where travellers can use mobile calls, SMS and data at their domestic price. For companies whose staff travel, work in the field or coordinate operations across these markets, the change can make mobile spending more predictable and reduce a familiar source of cross-border friction. The extension was approved by the Council of the EU in July 2025 for application from 2026. The Council's official announcement on the roaming extension confirms that Moldova and Ukraine were set to join the EU roaming area from 1 January 2026. Follow-up EU updates recorded Ukraine's formal accession in Kyiv on 12 January 2026. In practical terms, a customer from an EU country, Moldova or Ukraine can use their domestic mobile plan while roaming in the other participating areas, rather than facing a separate retail roaming tariff. The arrangement is not a blanket promise of unlimited use abroad, however. It operates under the established Roam Like at Home framework, including fair-use policies, sustainability derogations and wholesale roaming charges. What the extension changes for cross-border work For a travelling employee, a mobile connection is part of the working toolkit. Calls with customers, two-factor authentication messages, map and logistics apps, messaging platforms and cloud services can all rely on roaming data. Bringing Moldova and Ukraine into the same roaming area gives businesses a clearer basis for planning those routine costs when staff move between the EU and either country. The change also matters for service consistency. EU communications around the extension stress that roaming customers should receive the same quality of service available at home, including access to technologies such as 4G where those are available under the domestic service. That principle is important for work that depends on stable mobile data, although real-world performance will still depend

2026-08-27 原文 →
AI 资讯

Presentation: Python, Numba, and Algorithm Design: Building Efficient Models in Financial Services

Chad Schuster discusses bridging Python's developer velocity with C-like performance using Numba JIT and GPUs. Drawing from large-scale actuarial modeling, he explains LLVM pipeline architecture, performance gains up to 750x, and essential trade-offs like OOP limits, type inference errors, and compile-time overhead for engineering leaders scaling compute-heavy enterprise systems. By Chad Schuster

2026-08-27 原文 →
AI 资讯

Fintech Shipment Fan-Out: SaaS Retention Cleanup and the Node.js Cron-Queue Boundary

Short answer: use a scheduled cleanup endpoint when one indexed, bounded pass can finish predictably; use a queue when cleanup must be divided into independently retriable batches. For a fintech SaaS that fans out shipment updates to many subscribers, latency and cost should be judged at the system boundary: a cheap cleanup run is not a good bargain if it contends with delivery or leaves retention evidence incomplete. The first design decision is to keep shipment fan-out separate from retention work. A shipment update has a latency-sensitive path. Expired subscriptions, old delivery attempts, and temporary fan-out records usually have a policy-driven path. They may share a database, but they should not share an unbounded transaction or an execution budget. This distinction matters more than the spelling of a cron expression. It also gives the team a useful test: can the cleanup be repeated safely while the shipment update path continues to make progress? How should a Node.js SaaS choose a cron or queue for scheduled cleanup? Measure the worst case first. Count eligible records by tenant, check the relevant index, estimate lock pressure, and measure a bounded pass while the database is serving normal shipment traffic. The median duration is not the decision variable; the tail is. A scheduled data cleanup is a good fit for one HTTP-triggered run when its cutoff, tenant scope, batch size, and completion state can be recorded and the run has room to finish before its execution limit. The cutoff should be computed by the application and persisted with the run. A schedule has jitter, and a paused schedule may not replay every missed invocation. “Delete records older than the cutoff captured at run start” is therefore more auditable than silently recalculating the boundary for every page. The query should also exclude legal holds, active disputes, and any retention exception required by the business policy. Keep it bounded. The boundary is operational. When a tenant can mo

2026-08-27 原文 →