SShortSingh.
Back to feed

The bitter lesson of browser agents

0
·1 views

Article URL: https://browser-use.com/posts/bitter-lesson-browser-agents Comments URL: https://news.ycombinator.com/item?id=49713637 Points: 4 # Comments: 0

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

MCP Python SDK v2.0.0 Silently Breaks Projects by Renaming FastMCP to MCPServer

The Model Context Protocol Python SDK released version 2.0.0 on July 28, 2026, renaming its core FastMCP class to MCPServer and relocating all related submodules, with no deprecation warning or backward-compatibility shim. Projects using loosely pinned dependencies in requirements.txt automatically resolved to the new version on fresh installs, causing silent import failures rather than clear error messages. The break only surfaced at runtime, often in CI pipelines or on new contributors' machines, as confirmed by a GitHub issue filed against the jupyter-mcp-server project. A secondary silent change also altered the server's default client-visible name from 'FastMCP' to 'mcp-server' without raising any exception. The incident highlights a broader ecosystem risk, with studies suggesting 20–28% of minor and patch releases introduce breaking API changes, underscoring the importance of strict dependency version pinning.

0
ProgrammingDEV Community ·

Local LLMs Now Viable for Coding and Summarization Tasks via Ollama

Recent advances in local large language models have made them significantly more capable for tasks like code generation and document summarization, reducing reliance on cloud-based AI services. Models such as Google's Gemma 4 and Alibaba's Qwen are now recommended for coding tasks, with Gemma 4 12B requiring around 6.7 GB of VRAM in its quantized form. Ollama has emerged as a widely used platform for deploying these models on Windows, Mac, and Linux, integrating with tools like Visual Studio Code and JetBrains AI Assistant. To get the best results, users are advised to carefully select a model suited to their hardware and intended task, and to fine-tune runtime parameters accordingly. While cloud-based models from providers like Anthropic and OpenAI still hold an edge in overall capability, local alternatives have become practical enough to merit serious consideration for personal and developer workflows.

0
ProgrammingDEV Community ·

NVIDIA and Phasecraft Achieve 15x Quantum Simulation Speedup Using AI Hardware

Phasecraft and NVIDIA have jointly achieved a fifteenfold improvement in quantum simulation speed by combining hardware-adaptive algorithms with NVIDIA's Hopper architecture, hosted at the University of Nottingham. The collaboration produced a database of over 3,000 molecular emulations spanning 13 molecular systems, making it the largest known dataset built using the Variational Quantum Eigensolver method. The work bridges the gap between today's limited quantum hardware and the demands of real-world applications by leveraging classical high-performance computing to emulate quantum environments. A key motivation is accelerating drug discovery, enabling researchers to model how potential medicines interact with human cells before physical lab testing begins. The datasets and algorithms developed now are designed to transfer seamlessly to future large-scale quantum computers as that hardware matures.

0
ProgrammingDEV Community ·

Vibe Coding Is Not Engineering, Experts Warn About Mislabeling AI-Assisted Code

A commentary published on DEV Community by Giorgi Kobaidze on September 13 argues that vibe coding should not be equated with software engineering. The author contends that while AI-assisted code generation represents an evolution of IDE tools like autocomplete, it addresses only a narrow slice of what engineering involves. True software engineering encompasses architecture, design decisions, library selection, trade-offs, testing, security, and long-term maintenance. Kobaidze draws a clear distinction between prompting an AI for code and conducting rigorous code review. The piece warns that mislabeling vibe coding as engineering risks undermining the broader responsibilities and accountability that professional software development demands.