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

今日精选

HOT

最新资讯

共 28627 篇
第 728/1432 页
AI 资讯 The Verge AI

Comcast is splitting in two

Comcast has announced plans to separate itself into two publicly traded companies, spinning off its NBCUniversal and Sky broadcasting arms. The shake up aims to protect the media conglomerate's profitable broadband and wireless brand, which will retain the "Comcast" company name, as its media and entertainment business - now collectively named "NBCUniversal" - faces increasing […]

Jess Weatherbed 2026-06-29 19:29 8 原文
AI 资讯 The Verge AI

The war against ‘woke’ could end US science as we know it

A sneaky rule change has the potential to blow up scientific research in the United States. But there's still time to fight it. On May 29th, the Office of Management and Budget (OMB) issued a 412-page proposal to revise federal financial assistance. The language is a combination of distinctly Trumpian attacks on "woke" policies and […]

Bethany Brookshire 2026-06-29 19:00 5 原文
AI 资讯 InfoQ

Article: Virtual panel: Security in the Machine Age: Expert Insights on AI Threat Evolution

This virtual panel brings together AI security experts to examine the evolution of AI-driven threats, from prompt injection and data poisoning to agent abuse and AI-powered social engineering. The discussion explores emerging attack patterns, incident response challenges, and the changes security teams must make as AI systems become more autonomous and integrated into critical workflows. By Claudio Masolo, Elham Arshad, Sabri Allani, Vijay Dilwale, Igor Maljkovic

Claudio Masolo, Elham Arshad, Sabri Allani, Vijay Dilwale, Igor Maljkovic 2026-06-29 19:00 11 原文
AI 资讯 InfoQ

Podcast: Architectural Patterns: Moving Beyond Cloud-Native to Local-First - Insights from Adam Wiggins

In this episode, Heroku co-founder and Ink & Switch founder Adam Wiggins argues for a 'local-first' architecture that reconciles cloud-based collaboration with the performance and data ownership of local software. He explores the role of CRDTs and version control primitives in non-code domains, and examines how a hybrid AI future might leverage local models for core productivity tasks. By Adam Wiggins

Adam Wiggins 2026-06-29 19:00 9 原文
AI 资讯 Schneier on Security

Robot Police Officers

We’ve taken one small step towards robot police officers: a drone capable of disarming a suspect: In a June 22 video posted on the Sacramento County Sheriff’s Office’s Instagram page, an officer wearing goggles can be seen operating a drone to retrieve a knife from an armed suspect hiding inside a cluttered house. “After not responding to negotiators, a drone was deployed inside the residence,” the post says. “Drone pilots located the suspect hiding in a corner of a garage” and then used a high-powered magnet attached to the drone to grab the knife out of the suspect’s hand. In the video ­ which is soundtracked by the “Mission: Impossible” theme song—the intercepted knife can be seen spinning around in the air as the drone carries it back to the deputies...

Bruce Schneier 2026-06-29 18:55 10 原文
AI 资讯 Dev.to

Describe Your JSON Query in English — Get JSONPath Instantly

You know what you want from a JSON document. You just don't want to memorize whether it's $[?(@.age > 18)] or $..users[?(@.active)] . Plain English in. JSONPath out. JSONPath Assistant on FormatList lets you paste JSON, describe what you need in natural language, and get a validated JSONPath expression plus the actual results — all in your browser. No account, no API key, no data sent to a server. How it works Paste your JSON — an API response, config file, or test fixture. Describe what you need — e.g. "get all user names" or "find products with tag tech". Generate — the assistant reads your JSON structure and maps your query to JSONPath. Validate & copy — the expression runs against your data immediately. Copy the path or the matched values in one click. If the first attempt returns no matches, the tool retries with a simpler variation automatically. Example queries You type Generated JSONPath Get all user names $.users[*].name Find users older than 18 $.users[?(@.age > 18)] Get names of active users $.users[?(@.active == true)].name Find products with tag tech $.products[?(@.tags.indexOf('tech') >= 0)] Get all order prices $.orders[*].price Get the first user's email $.users[0].email Get all pod names {.items[*].metadata.name} Get all pod IP addresses {.items[*].status.podIP} The tool ships with one-click examples for each of these — load one, hit Generate, and see how it works before trying your own JSON. What kinds of queries it understands Property access — "get all names", "list order prices" Numeric filters — "older than 18", "price under $10", "greater than 100" Boolean filters — "active users", "enabled devices" Tag / category searches — "with tag tech", "beauty category" Multi-condition — "both tech and mobile tags" Quantifiers — "the first user", "the last item" Kubernetes — "get all pod names", "pod IP addresses" It analyzes field names in your JSON — so users , products , orders , or whatever keys you actually have — and builds paths that match your sc

hito x 2026-06-29 17:44 9 原文
AI 资讯 Dev.to

Three Questions I Ask Every System. Most Design Reviews Skip All Three.

The design doc is fourteen pages. Clean service boundaries, thoughtful API contracts, a deployment story that handles rollback without incident. Six months of work. The team is proud of it, and the work is genuinely good. Three questions will tell more about this system than all fourteen pages. Not questions about implementation details or technology choices. Questions about how the system was designed to age, to fail, and to be understood by someone who didn’t build it. Most architecture conversations never reach these questions, which is part of why the gap between a good system and a great one is often invisible until it is suddenly very visible. What does this make hard? Good architecture conversations focus on what a design enables: faster deployments, independent scaling, and clearer ownership. The question that separates architectural thinking from implementation thinking is the inverse . What does this make hard? Every decision forecloses options. The service boundary that gives teams autonomy makes cross-service transactions expensive. The data model that reads cleanly under expected load makes certain write patterns awkward. The abstraction that simplifies onboarding makes some categories of refactoring nearly invisible as possibilities. These are not arguments against the decisions. They are the other side of every decision, and that other side exists whether or not anyone names it. The design doc that holds up over time is not the one where nothing is difficult. It is the one where the difficult things are named. “This approach makes distributed transactions impossible, and here is why we have decided to accept that constraint.” That sentence, or something close to it, belongs in every significant architecture document. Its absence is not a sign that the constraint wasn’t considered. Often it was. But without the name, the constraint becomes invisible to everyone who wasn’t in the room, which eventually includes the original team. When joining a system s

Saeed Habibi 2026-06-29 17:43 8 原文