News for hackers. Stuff that matters.
Re:Safe and efficient C++ interoperability via non-escapable... by tialaramex on Thursday November 14, 2024 @09:13AM (#42136281)
> how come it is still so primitive that you do not even get to know the location of the issue?

The link kind of explains why this was a difficult problem, but I think it's worth a moment to consider why this particular difficult problem just wasn't solved. Why was Apple OK with just shrugging, eh, it's hard ?

This is a Quality of Implementation issue. Quality is truly important but because Quality is hard to turn into a metric you'll see management don't like to make it a goal, after all they can't really measure if they succeeded and so when it is competing with other things which are goals it's just abandoned.

Re:Safe and efficient C++ interoperability via non-escapable... by johnisgood on Thursday November 14, 2024 @09:23AM (#42136356)
Yeah, what I wanted to know is how come that Apple has not solved this issue yet, or how their decision-making goes with regarding to adding X and Y instead of fixing this absurd issue.