正在加载视频...

视频加载失败

Not every new model needs to be the biggest model. Sometimes I'd rather have one that's fast, reliable, affordable, and actually pleasant to build with. That's the impression I got after using Tencent Hunyuan Hy3. I threw a mix of coding, reasoning, and agent tasks at it throughout the...

56,379 次观看 • 1 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Tencent just dropped Hy3, and it's worth a look if you're building AI agents. I spent some time putting it through its paces today. A quick rundown of what makes this release notable: → 295B total parameters (Mixture-of-Experts), but only 21B active at inference — a real efficiency play → 256K context window for handling large codebases or long documents → Purpose-built improvements for coding and multi-step agent tasks → Fully open under Apache 2.0 — no restrictive commercial terms → A free two-week API window currently live on OpenRouter On the practical side: prompts involving layered instructions and coding tasks came back fast and coherent. Tencent says this release builds directly on feedback from 50+ internal product teams following an earlier preview, with reported drops in hallucination rate (12.5% → 5.4%) and commonsense errors (25.4% → 12.7%). Those are Tencent's own numbers, so treat them as a starting point rather than gospel until third parties weigh in. For context: Tencent's own comparisons put Hy3 behind GLM-5.2 specifically on coding benchmarks — GLM is a much bigger model (~744B total), so the trade-off makes sense. Hy3's pitch isn't "biggest," it's "efficient enough to actually deploy." Bottom line — if you're evaluating open-weight options for agent workloads, this is a solid one to add to the testing queue while the free window is open. Try it here: Tencent Hy #Hy3 #Hunyuan #TencentAI #AICoding

Felix

36,925 次观看 • 1 个月前

hy3 vs fable 5 vs opus 4.8 vs sonnet 5 Tencent Hy just dropped hy3 – their new open-weight model under apache 2.0. following the april preview they scaled up post-training, and it now rivals flagship open models with 2-5x the params. api pricing: ~$0.15 in / ~$0.59 out per 1m tokens. built for coding, office work, frontend, agentic tasks so we ran a test: hy3 vs fable 5 vs opus 4.8 vs sonnet 5 three prompts, one-shot each: • ocean wave crumbling a sand castle (canvas) • looping factory assembly line (html/css/js) • interactive 3d city with three.js + orbitcontrols self-contained files, no libraries beyond the cdn where asked totals across all three prompts: 1. hy3 – 1231 loc / 14m34s 2. sonnet 5 – 1373 loc / 18m55s 3. fable 5 – 1546 loc / 18m32s 4. opus 4.8 – 1904 loc / 27m21s hy3 is the fastest and the leanest by a wide margin we had opus 4.8 analyze hy3's code. the read: - sand castle: checklist-complete but the crumble is parametric, not physical. it shrinks and slumps the towers and fades alpha instead of dissolving into grains. the cheap-but-plausible interpretation. the tell of a smaller model - factory line: the arm-to-part sync is actually causal, not faked. it triggers each robot early by exactly the arm's descent time, so the tap lands right as the part arrives. it also pre-seeds the belt so it never cold-starts empty. clean state machine. one latent bug – a part gets marked processed before checking if the robot is free, so at a faster spawn rate a "laptop" could ship missing a part. never fires at current timing, but the invariant isn't enforced - 3d city: genuinely frontier-adjacent. correct modern setup (pcfsoft shadows, srgb, aces tone mapping, damped orbit + auto-rotate pause). clones the window texture per building and scales the uv repeat to each building's dimensions so windows don't stretch. downside: no instancing – ~800 texture clones across 200 buildings. runs fine, not optimized. roads are implicit gaps, not explicit planes our observations: • hy3 is quite fast • its animations are simple but you can see it trying – it adds detail, and the 3d render sits at the same level as the frontier models • sonnet 5 is weak here. hy3 beats it on the sand castle and the 3d render, level on the conveyor • opus 4.8 is anthropic's best model after the fable 5 nerf – it beats fable on the conveyor and the 3d render net: hy3 runs clean and well-formed across all three with zero syntax errors, even version-matching the three.js core and examples build. it's economical rather than ambitious – it does the minimum viable version of each hard requirement well, and only reaches for the expensive interpretation on the 3d task a very coherent profile for a cost-optimized open-weight model follow thehype. for 24/7 ai news, analysis and breakdowns

thehype.

34,961 次观看 • 1 个月前

I have been testing DeepSeek-V4-Pro with the Pi coding agent. I am mindblown by how well it works out of the box. A few notes: I spent a few hours building an LLM wiki with an agent powered entirely by DeepSeek-V4-Pro on Fireworks inference. This is the first time I feel like there is an open-weight model that can reason at the level of Claude and Codex. And it does this in a cost-effective way with support for 1M context length. To be clear, I am using DeepSeek-V4-Pro inside of Pi without any special configuration. It works out of the box. It's exciting that there is a model that can just be plugged into a basic harness like Pi, and it just works. I've never seen that before. Most models require lots of configuration and setup. DeepSeek's DeepSeek-V4-Pro is clearly good at agentic coding (probably the best from the open-weight models), but the model is also great on knowledge-intensive tasks where reasoning matters. The agent pulled agentic engineering best practices from different company docs (Anthropic, OpenAI, Google, Stripe, Meta, Modal, DeepSeek, Mistral, Cohere), searched and digested Reddit and HN threads, summarized arxiv papers, and surfaced trending GitHub repos. Then it distilled everything into actionable tips across categories. I love the Wiki it built. The quality is really good. Here is a snapshot of what the wiki looks like: DeepSeek-V4-Pro handled the task without breaking stride. Multi-step research queries, code generation for scaffolding, context-heavy reasoning across disparate sources. For coding specifically, this is the first open-weight model that genuinely feels like a Codex or Claude Code experience. It compares in capability and actual multi-turn agentic work. What made the loop feel so responsive was Fireworks' inference speed (the fastest in the market) and the fact that they actually validate models at the systems level before shipping. No corrupted reasoning traces. Just fast, reliable iteration. The hybrid CSA and HCA attention design cuts KV cache to just 10% and inference FLOPs by nearly 4x at 1M-token context. This is what makes the agent loop actually fast and cheap enough to run in practice. For devs who've been watching open-weight models close the gap but haven't found one that actually delivers in practice, this is the closest I've seen. Try it here:

elvis

60,091 次观看 • 3 个月前

NOBODY wants to send their data to Google or OpenAI. Yet here we are, shipping proprietary code, customer information, and sensitive business logic to closed-source APIs we don't control. While everyone's chasing the latest closed-source releases, open-source models are quietly becoming the practical choice for many production systems. Here's what everyone is missing: Open-source models are catching up fast, and they bring something the big labs can't: privacy, speed, and control. I built a playground to test this myself. Used CometML's Opik to evaluate models on real code generation tasks - testing correctness, readability, and best practices against actual GitHub repos. Here's what surprised me: OSS models like MiniMax-M2, Kimi k2 performed on par with the likes of Gemini 3 and Claude Sonnet 4.5 on most tasks. But practically MiniMax-M2 turns out to be a winner as it's twice as fast and 12x cheaper when you compare it to models like Sonnet 4.5. Well, this isn't just about saving money. When your model is smaller and faster, you can deploy it in places closed-source APIs can't reach: ↳ Real-time applications that need sub-second responses ↳ Edge devices where latency kills user experience ↳ On-premise systems where data never leaves your infrastructure MiniMax-M2 runs with only 10B activated parameters. That efficiency means lower latency, higher throughput, and the ability to handle interactive agents without breaking the bank. The intelligence-to-cost ratio here changes what's possible. You're not choosing between quality and affordability anymore. You're not sacrificing privacy for performance. The gap is closing, and in many cases, it's already closed. If you're building anything that needs to be fast, private, or deployed at scale, it's worth taking a look at what's now available. MiniMax-M2 is 100% open-source, free for developers right now. I have shared the link to their GitHub repo in the next tweet. You will also find the code for the playground and evaluations I've done.

Akshay 🚀

50,323 次观看 • 9 个月前