So it's not an open model while not being much better? Meh.
MAI-Code-1-Flash
51–60 of 297 posts
Re: MAI-Code-1-Flash
#52Huh, according to that model card this is a 137B total parameter model. Performance doesn't seem that good: - MAI-Code-1-Flash (137B-A5B) = 51% on SWE-bench pro - Qwen3.6-35B-A3B = 49.5% on SWE-bench pro ( https://huggingface.co/Qwen/Qwen3.6-35B-A3B ) They benchmark against Claude Haiku but Haiku is not good, it's worse than tiny open models you can run locally or via API at 10% the cost.
[deleted]
Re: MAI-Code-1-Flash
#53Shouldn’t the next model focus not be on code but system design? Seems like the work from a good system design to code is practically solved. Now it’s a matter of the design of the system. Or is that represented in these evals?
Have you tried system design with LLMs? I find them pretty good at suggesting 5 architectures for a problem and then iterating on the solutions.
Even if I had no idea, going with the default suggestion would not be a terrible mistake, assuming you did describe your requirements relatively well.
Re: MAI-Code-1-Flash
#54[dead]
Re: MAI-Code-1-Flash
#55You lost me at forced scrolling. Ugh!
Re: MAI-Code-1-Flash
#56"superintellegence team"
Why not assign them to make windows good :D
Re: MAI-Code-1-Flash
#57Huh, according to that model card this is a 137B total parameter model. Performance doesn't seem that good: - MAI-Code-1-Flash (137B-A5B) = 51% on SWE-bench pro - Qwen3.6-35B-A3B = 49.5% on SWE-bench pro ( https://huggingface.co/Qwen/Qwen3.6-35B-A3B ) They benchmark against Claude Haiku but Haiku is not good, it's worse than tiny open models you can run locally or via API at 10% the cost.
The take away is that this model is a smaller model that competes with Haiku, I would hope they come out with a "Sonnet" competing model, then Opus. I have been wondering why Microsoft is kind of "sleeping" on offering models they themselves have made on Copilot, maybe it was part of their deal with OpenAI? Not sure.
Re: MAI-Code-1-Flash
#58Earlier quoted context omitted.
It’s about bang for buck. That high a score for 5B params is pretty good, nigh unbelievable a short while ago. It is my belief that smaller models will get better and better, and even cloud SOTA models will shrink. Yet another reason the current buildout will feel like the railroads.
Yeah the future is probably a number of highly specialised small models you can run on your own hardware rather than massive frontier models in the cloud. That's what I'm betting on anyway.
MOE basically work that way already, QWEN/etc with low active params (A-number in name) allows to inference big models locally (only active params have to fit into memory)
Re: MAI-Code-1-Flash
#59It's so weird to me that the benchmarks remain so low, but the models are marketed as revolutionary. And if you say that low coding capabilities aren't a problem, say that to the token price hike and 'general use' model setup. Why not sell it as a math agent? Why do I have to set up 4 agents to check each others' work?
It’s about bang for buck. That high a score for 5B params is pretty good, nigh unbelievable a short while ago. It is my belief that smaller models will get better and better, and even cloud SOTA models will shrink. Yet another reason the current buildout will feel like the railroads.
The SOTA models will not shrink, because the problems will get bigger, from "write me a C compiler" to "clone Stripe business and run it".
Re: MAI-Code-1-Flash
#60Scroll wheel hijacked on this entire domain
Fix:
(() => {
const KILL = ['wheel', 'mousewheel', 'DOMMouseScroll', 'touchmove'];
const block = e => e.stopImmediatePropagation();
for (const t of KILL) {
window.addEventListener(t, block, { capture: true, passive: true });
document.addEventListener(t, block, { capture: true, passive: true });
}
document.documentElement.classList.remove('lenis','lenis-smooth','lenis-scrolling','lenis-stopped');
console.log('Scroll hijack disabled — native scrolling restored.');
})();