Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Here's an image->html test for it using 2.6 Pro Ultraspeed, along with comparisons for grok 4.7 and Astra.

Design: https://image.non.io/78795662-8bfc-4e14-8d72-3738392aa6b3.we...

MiMo 2.6 Pro Ultraspeed (36min): https://html.non.io/annui-mimo/

Grok 4.7 (25min): https://html.non.io/Annui-grok/

Astra (19min): https://html.non.io/annui/

Overall this felt like the weakest of the three. Ultraspeed was fast as far as tokens per second goes, but it overthought quite a lot of things resulting it in having one of the longest build times. That overthinking didn't lead to better results either - note the statue with the cropped off arm. It's also the worst implementation of the dynamic lighting effect / displacement effect - the background especially has some significant distortion. Astra was the only one that seemed to understand that displacement should happen less the further something is in the distance.

Here's a vid of all 3 side by side with the source design: https://non.io/video/annui-comparison.mp4

 help



For me it seems like this model’s overthinking should be tamed.

Perhaps instead of giving it a one shot task with vague prompt. I wonder how it can perform with much more detailed and constrained prompt (can you please elaborate more on the level of detailness and ambiguity that the prompt is and where does this model seem to overthink the most?)

Also are there any ways to tame such overthinking of models in general?

I hope that once models start becoming smart enough (I think for me it’s already there) or becoming genuinely the Sota. They then start focusing a lot more on optimizing token usage


Astra's looks the worst to me on mobile, though

That's fair - worth noting that none of them were instructed to make a mobile variant or to test the mobile size.

I used 2.6 Pro and it seems to overthink way too much, leading indeed to very slow build time.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: