_under_scores_

This is a bit of an uncharitable take. "It either works or it does not" is an oversimplification when you consider that code often doesn't work in the way it was intended - that's what bugs are. Are vibe coded apps inherently more buggy? Not necessarily. But the I'd argue there's more surface in a vibe coded app that requires blind trust.

Is proactivity an emotion? Surely its a behaviour?

I think the problem is is that coding is not wholly a 'writing code' problem. It's a translation from idea to outcome. Often I think the bad code generated by an LLM is less to do with it's 'ability' and more to do with an instruction that hasn't adequately accounted for the possibility of what code satisfies the criteria. I'm not sure how a newer model can improve on this per se - sure there will be imrpovement on outright mistakes but for me at least, that's been and gone with more or less with any model released in te last 6 months.

I switched to predomentantly using mimo this week, mostly out of curiosity to see how dependant I was on frontier models. Honestly I cant really tell the difference. I would say I work on pretty average codebases with well know frameworks doing pretty typical things and initial impressions is that mimo, kimi and deepseek can probably handle what I need more or less the same as gpt5.5 or claude.

I may be misunderstanding the article but doesnt the fact that all other science and understanding sits on a continuum of which consciousness has (to my understading) to real footing mean that the problem is dualitic by definition? Thats not to say that it can't be 'brought into the fold', it may well be, but until it is it has no other place that to sit outside.

That's depressing. Admittedly I was just browsing on my phone whilst waiting for something but the comment read as real.

Oh! Whats the tell out of curiosity?

Yes?

Edit: you mean op?

For me it's also in generating output that I know is right when I see it, but don't necessarily know every intricate detail of up front.

Personally I don't get the argument against enums. From what I can tell it's purely to do with the symantics of what Typescript is, rather than any inherently bad property of enums.

Honestly, I'd say around $2-5. It's not that I wouldn't value better quality search but in a world where search feels like an almost 'invisible' part of browsing the web I'd struggle to pay that much. I guess it's comparable to what I feel is a price I'd be willing to pay for a VPN say compared to a coffee subscription.

This also isn't a reflection of what I percieve the work in building a search engine to be but more my subconcious perception of what I'm getting.