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

AI 资讯

AI人工智能最新资讯、模型发布、研究进展

15606
篇文章

共 15606 篇 · 第 606/781 页

The Verge AI

Apple is using AI to fix Safari’s extension problem

Apple is trying to solve one of Safari's biggest weaknesses with AI. Safari has long lacked the robust library of extensions that its rivals have, mainly due to the stringent development requirements from Apple. But now, Apple is inviting users to essentially vibe-code their own extensions. In a demo shared by Apple, the company showed […]

Emma Roth 2026-06-09 06:14 👁 5 查看原文 →
HackerNews

Show HN: Command Center, the AI coding env for people who care about quality

Hi HN! We’re Jimmy and Ray. Jimmy is a Thiel Fellow with a Ph. D. from MIT who has worked on programming tools for 15 years; Ray became VP of Sales at a $2B company when he was 19 and has built side-businesses vibe-coding. Last year, we set to answer the question “If AI can write code 100x faster, then why aren’t you shipping 100x faster?” What we learned shocked us — even fairly nontechnical people and solo founders told us they were spending more than half of their development time reading the

Darmani 2026-06-09 06:10 👁 4 查看原文 →
Product Hunt

TryCase

Disposable test environments for AI coding agents Discussion | Link

2026-06-09 06:02 👁 4 查看原文 →
Reddit r/artificial

OpenAI says it has confidentially filed for an IPO

Artificial intelligence giant OpenAI says it has filed confidential paperwork for an initial public offering. In a brief statement, OpenAI says it has submitted its S-1 filing, but has "not decided" yet on the timing of an IPO, adding: "It may be a while because there are things we want to do that are likely easier as a private company." The announcement comes days after the company's chief rival, Anthropic, filed its own S-1 , and the on the eve of major AI player SpaceX's potentially historic public debut. submitted by /u/LinkedInNews [link] [留言]

/u/LinkedInNews 2026-06-09 06:01 👁 8 查看原文 →
Reddit r/artificial

AI coding agents are getting better at writing code, but I'm not convinced they're getting better at understanding codebases

I've been using Claude Code, Cursor and a few other coding agents quite a bit recently. One thing that keeps standing out is that generating code isn't really the bottleneck anymore. Understanding the codebase is. Agents can usually find the relevant file. The problems start when the change depends on: historical decisions undocumented relationships ownership boundaries files that always change together Bigger context windows help, but I'm not sure they solve this problem completely. Curious what people building or using coding agents think. Is the next step bigger models and more context? Or do agents need a better representation of the codebase itself before they can reliably work on larger projects? Been exploring this problem while building RepoWise: https://github.com/repowise-dev/repowise submitted by /u/Icy-Roll-4044 [link] [留言]

/u/Icy-Roll-4044 2026-06-09 05:56 👁 7 查看原文 →
Product Hunt

Wobo 2.0

Tinder for jobs: swipe right and AI applies for you Discussion | Link

Rohan Chaubey 2026-06-09 05:49 👁 3 查看原文 →
The Verge AI

Apple’s new parental controls are for keeping Apple out of trouble

When Apple put child safety front and center at WWDC on Monday, its stated goal was helping parents fine-tune their kids' online experiences and avoid excessive screen time. But amid a global debate over internet regulation, its latest updates also looked like a defensive move in a brewing fight against Meta and other app developers. […]

Lauren Feiner 2026-06-09 05:48 👁 12 查看原文 →
Product Hunt

AgentOS

Manage AI agents, tasks, workspaces from one control layer Discussion | Link

Kazim Akgül 2026-06-09 05:45 👁 4 查看原文 →
Reddit r/MachineLearning

How to start open source contribution [D]

hi everyone, I created a blog around how I started open source contribution, documented all minute details. Please give it a read and give review as this is my journey to do blogging for the first time. It is free! https://substack.com/home/post/p-200202050 submitted by /u/DqDPLC [link] [留言]

/u/DqDPLC 2026-06-09 05:45 👁 6 查看原文 →
Reddit r/artificial

How do you handle a simple question popping up mid-chat? Switch models or just push through?

Claude is my main tool. I delegate all the difficult tasks to him. What gets me is the small stuff. I'll be halfway through a heavy conversation and some throwaway question comes up, the kind literally any model could handle. So now I'm stuck: ask the capable model and feel a bit wasteful, or open another tab with a lighter one and lose the whole thread I was building. I do the second more than I'd like to admit. What I actually want is one place to pick whatever model makes sense for the moment, Haiku for quick stuff, Sonnet or Opus for the hard things, maybe GPT-4o or Gemini if I feel like it, all in the same chat. No new conversations, no tab-hopping. Bonus points if it just routes automatically based on the question. Half-tempted to build it myself at this point. But figured I'd ask first: does something like this already exist and I just missed it? How do you deal with it? Stick with one model and push through, bounce between tabs like me, or did you find something that actually works? submitted by /u/Stunning_Tadpole1286 [link] [留言]

/u/Stunning_Tadpole1286 2026-06-09 05:39 👁 8 查看原文 →
The Verge AI

OpenAI files for IPO, following Anthropic

OpenAI on Monday checked off a preliminary step in the IPO race that it and rival Anthropic have been competing in for the better part of a year: The company announced it has confidentially submitted a Form S-1 with the US Securities and Exchange Commission, following Anthropic's decision to do the same on June 1st. […]

Hayden Field 2026-06-09 05:38 👁 10 查看原文 →
Dev.to

Benchmarking AI Agents, Gemma 4 On-Device Workflows & AI System Security

Benchmarking AI Agents, Gemma 4 On-Device Workflows & AI System Security Today's Highlights This week, we dive into critical aspects of applied AI: practical benchmarks for controlling AI agent costs and reliability, Google's new Gemma 4 model enabling advanced on-device agentic workflows, and essential techniques for securing AI systems against vulnerabilities. Benchmarking a Kill Switch for Runaway AI Agents (Dev.to Top) Source: https://dev.to/prashar32/benchmarking-a-kill-switch-for-runaway-ai-agents-and-why-the-real-number-is-a-ceiling-not-a--4832 This article addresses the critical challenge of managing costs and ensuring control over autonomous AI agents in production environments. It introduces a practical benchmark designed to evaluate the effectiveness of 'kill switches' for runaway agents, moving beyond vague claims of cost reduction. The author argues that focusing on a ceiling for agent spend, rather than a percentage reduction, provides a more realistic and actionable control mechanism. The benchmark is presented as a runnable script, allowing developers to independently test and verify the reliability and cost-efficiency of their AI agent orchestration strategies. This approach is vital for anyone deploying AI agents, offering concrete methods to prevent uncontrolled resource consumption and ensure operational stability. By providing a tangible way to measure and enforce cost boundaries, the article offers a crucial tool for robust AI workflow automation and production deployment patterns. Comment: This is a must-read for anyone deploying agents in production. The ability to benchmark a kill switch in one command is incredibly practical for ensuring cost control and preventing unexpected resource usage. Gemma 4 12B Enables On-Device, Multimodal Agentic Workflows with an Encoder-free Architecture (InfoQ) Source: https://www.infoq.com/news/2026/06/google-gemma4-12b-local-coding/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

soy 2026-06-09 05:36 👁 10 查看原文 →
Dev.to

How I stopped hardcoding business rules in PHP - and built a rule engine to fix it

Every PHP developer knows this situation: a client calls and says "I want free shipping for VIP customers on weekends, but only if the cart total is above €100." You open your code. You find the shipping module. You add an if. You deploy. Three weeks later: "Actually, make it €80. And also for the 'Premium' group." You open your code again. This loop : client request -> find logic in code -> modify -> deploy, was costing me a lot of time. And it's not just shipping. I build custom ecommerce solutions: payment modules, synchronization systems, pricing calculators. Business rules are everywhere, and they change constantly. The obvious solution I didn't want Symfony's ExpressionLanguage exists and it's impressive. But it pulls in dependencies, it can traverse objects and call methods (which is a security concern when rules are authored by users), and when something goes wrong, it doesn't tell you why. It's a black box. I needed something smaller, stricter, and transparent. So I built php-ruler I started with the classic pipeline: Lexer → AST → Evaluator. Strict typing from the start — 1 = '1' is a type error, not true. No silent coercion. Then I added features one real problem at a time. Problem: when something fails, why? -> I built an explain mode that returns the full evaluation tree: which sub-conditions passed, which failed, which were short-circuited, and why a variable was missing. Problem: in production, the context is sometimes incomplete -> I built a safe mode that doesn't throw on missing variables — it collects them all and lets you decide what to do. Problem: customer.group.name is not user-friendly -> I built an alias resolver. As a developer, I expose what I want: $resolver = ( new AliasResolver ()) -> add ( 'customer.group' , 'customer group' ) -> add ( 'cart.total' , 'cart amount' ); Now a non-developer can write: customer group = 'VIP' AND cart amount > 100 And I control exactly what variables are available to them. A real example Here's the shipping

olivier-ls 2026-06-09 05:36 👁 13 查看原文 →
Dev.to

DuckLake Spec, pg_background 2.0, and pgsql_tweaks 1.0.3 Enhance Database Ecosystem

DuckLake Spec, pg_background 2.0, and pgsql_tweaks 1.0.3 Enhance Database Ecosystem Today's Highlights This week's highlights include DuckDB's new DuckLake specification for simplified dataframe integration with data lakes, alongside key updates from the PostgreSQL community. We cover pg_background 2.0 for safer asynchronous SQL execution and the release of pgsql_tweaks 1.0.3 for enhanced monitoring and performance tuning. The DuckLake Spec Is so Simple, Even a Clanker Can Build One for Dataframes (DuckDB Blog) Source: https://duckdb.org/2026/05/04/ducklake-dataframe.html The DuckDB team has unveiled the DuckLake v1.0 specification, a significant step towards simplifying data lake interactions with dataframes. This specification aims to provide a robust yet straightforward framework for reading and writing dataframes directly from and to data lake storage, emphasizing ease of implementation. The announcement highlights the specification's simplicity, so much so that even AI can be leveraged to generate compatible dataframe reader/writer tools. This initiative promises to democratize data lake access, allowing developers and data engineers to integrate DuckDB's powerful analytical capabilities with their data lake architectures more seamlessly. By defining a clear standard, DuckLake facilitates the creation of a vibrant ecosystem of tools and connectors, enabling efficient data processing directly within the data lake context without complex ETL pipelines. This development positions DuckDB as an even more versatile tool for analytical workloads, bridging the gap between local data processing and large-scale data lake environments. The ability to easily build data lake connectors, potentially even with AI assistance, marks a notable shift towards more accessible and integrated data workflows. This could streamline operations for data scientists and analysts who frequently work with large datasets stored in various data lake formats, allowing them to leverage DuckDB's

soy 2026-06-09 05:35 👁 12 查看原文 →
Dev.to

Diário de dev #3: o bug que só aparece quando alguém usa

No trabalho, nenhum código mudou. O que mudou foi a forma como os clientes inserem os dados. E isso quebrou coisas que nenhum teste existente pegou. O bug que só aparece quando alguém usa A motivação pra montar E2E do zero veio de um problema específico. Você precisava acessar a aplicação pra quebrar. Não era um erro de lógica isolado que um teste unitário pegaria. Era uma combinação de dados reais num fluxo real produzindo um resultado errado que só aparecia na tela. Os clientes chegavam lá antes da gente. É uma categoria de problema que teste de código não resolve, porque o problema não está no código. Está na interação entre o código, os dados e o ambiente. A forma mais rápida de pegar antes é rodar o fluxo completo do jeito que o usuário roda. Ficou com smoke tests cobrindo os principais fluxos do produto, configuração pra rodar contra múltiplos ambientes, e notificação no Slack quando o nightly quebra. A parte mais útil não são os testes em si. É saber antes do cliente reportar. Autocrop: quando nenhuma ferramenta resolve tudo Num projeto paralelo que mantenho, passei o fim de semana montando autocrop automático pra imagens. A ideia inicial era usar o imgproxy Pro, que tem detecção de objeto embutida. Não ficou preciso o suficiente pra variedade de imagens que eu tinha. Fui pro Rekognition, que retorna bounding boxes. Mais controle, mas bounding box tem um limite: é um retângulo. Objetos não são retângulos. Aí descobri o rembg, que faz algo diferente. Em vez de delimitar uma área, ele cria uma máscara pixel por pixel usando uma rede chamada U2Net, treinada pra segmentação de primeiro plano. O resultado foi bem superior — ele recorta o objeto, não uma caixa em torno dele. Colocar isso em Lambda foi onde a semana ficou mais lenta. O modelo precisava estar acessível pro processo do Lambda, coloquei em /root , Lambda não lê de lá. Movi pro /opt , chmod 755. O NUMBA tentou escrever cache em diretório read-only, defini NUMBA_CACHE_DIR=/tmp . Depois OOM em imagens mai

Daniel Porto 2026-06-09 05:35 👁 12 查看原文 →
Dev.to

Linux 7.1 Boosts Intel Arc, Flatpak Integrates ROCm, Vintage AMD Driver Refined

Linux 7.1 Boosts Intel Arc, Flatpak Integrates ROCm, Vintage AMD Driver Refined Today's Highlights Recent developments enhance GPU performance and accessibility, with the Linux 7.1 kernel providing significant gains for Intel Arc Battlemage graphics. AMD's ROCm compute platform gains broader deployment potential through Flatpak 1.18 integration, while an older AMD GPU driver sees notable code cleanups. Linux 7.1 Helping Intel Arc Battlemage Graphics Achieve Better Performance (Phoronix) Source: https://www.phoronix.com/review/intel-b580-linux-71 Phoronix reports that the upcoming Linux 7.1 kernel release is delivering superior graphics performance for Intel's Arc B580 Battlemage desktop graphics card compared to the current stable Linux 7.0. This indicates ongoing, critical optimization work within the open-source Linux graphics stack, directly impacting the gaming and compute capabilities of Intel's latest GPU architecture. Such kernel-level improvements are vital for unlocking the full potential of new hardware on Linux platforms, ensuring users receive the best possible experience from their Intel Arc GPUs. The performance uplift suggests that deeper integration and fine-tuning of the kernel's display and compute drivers are progressing, addressing potential bottlenecks and enhancing throughput. For users and developers leveraging Intel Arc GPUs on Linux, this kernel update is a significant milestone, promising more stable and efficient operation for various workloads, from gaming to professional applications. It highlights the dynamic nature of Linux driver development, where continuous collaboration leads to tangible performance benefits even before major hardware refreshes. Comment: This shows how crucial kernel updates are for modern GPUs on Linux. Early adopters of Arc Battlemage should definitely keep an eye on Linux 7.1 for a noticeable performance bump. Flatpak 1.18 Released With Integration For AMD ROCm (Phoronix) Source: https://www.phoronix.com/news/Fl

soy 2026-06-09 05:35 👁 13 查看原文 →