I think what these guys want is for developers to update their old apps to suit this new environment. Recompiling old software and modifying it so that it doesn't require an FPU is surely a good way forward.
No, that's just ridiculous. Requiring recompilation of legacy code where the source might not be available...might as well be running on ColdFire at that point.
Look these excuses are no more than that.
And if Gunnar want to implement a superset of fpu commands for new or recompiled software, I'm all for it.
But this isn't a 'new environment', its new hardware designed for old code.
If the OS required an fpu, would the development team still be dragging their heels on it or suggesting recompilation?
Is there some problem the developers aren't letting us onto?
Like maybe they've had difficulty creating a functional floating point component?
I know they claim to have something, but that so far is just a claim.
And compatibility is important, if you're talking legacy applications.
Otherwise, why wouldn't you move to NG?
Its certainly faster.
We see full support for register level video and sound compatibility.
Is there something wrong with Motorola's designs for the cpu that the rest of us aren't aware of?
Because the 'we have a better way' argument isn't proving out.