TopicTracker
From HackerNewsView original
TranslationTranslation

Are browsers (fully) Opus ready yet?

The article examines browser support for the Opus audio codec, analyzing which browsers currently offer full or partial compatibility. It provides a technical overview of Opus implementation status across major web browsers.

Related stories

  • Anthropic has introduced a 1 million token context window for its Claude Opus 4.6 and Sonnet 4.6 models, representing a significant technical advancement. The company is offering this increased capacity without additional charges to users.

  • Anthropic publishes Claude system prompts as Markdown, which were converted into separate files with fake git commit dates to enable browsing changes via GitHub. This allowed for detailed analysis of changes between model versions like Opus 4.6 and 4.7.

  • Figma's dependence on non-designer seats made it particularly vulnerable to AI disruption. The launch of Claude Design further exacerbates this challenge for the company.

  • The Claude Token Counter tool has been upgraded to compare token counts across different Claude models. Opus 4.7 uses an updated tokenizer that increases token counts by 1.46x for text and up to 3.01x for images compared to Opus 4.6, potentially making it about 40% more expensive despite identical pricing.

  • The author tested Qwen3.6-35B-A3B and Claude Opus 4.7 on a "pelican riding a bicycle" benchmark. Qwen3.6 produced a better SVG illustration with a correct bicycle frame, while Opus 4.7 failed to properly render the bicycle frame. The humorous benchmark has generally correlated with model usefulness.