Yokemate of Keyboards
Posts: 4977 from 2009/1/28
From: Delaware, USA
Quote:terminills wrote:
Quote:Jim wrote:
Quote:BSzili wrote:
Quote:Jim wrote:
Quote:BSzili wrote:
Quote:Jim wrote:
Quote:BSzili wrote:
Quote:ppcamiga1 wrote:
Quote:
BSzili wrote:
Somewhere around its inception. It's binary compatible on m68k, and source code compatible on the rest.
AROS is not source and binary compatible.
But on 68k one can add libraries and patches from oryginal Amiga Os and made 68k AROS
enough source and binary compatible.
AROS x86 is of course worth nothing shit.
AROS x86 was shit, AROS x86 is shit and AROS x86 will be shit.
It is simple.
CPU change to one that not support 32 bit big endian mode already breaks compatybility.
AROS x86 have to have all drawbacks of original amiga os removed at time of change api to not compatybile.
AROS for LE cpu should be amiga gui and graphics on top of unix.
AROS x86 with cheated SMP is set of hacks still with out memory protection.
What can be asserted without evidence can be dismissed without evidence :)
Not really, if its a fairly obvious fact.
And "CPU change to one that not support 32 bit big endian mode already breaks compatybility", isn't worded that well, but it is factual.
Endian mode does greatly affect compatibility (although, conversely, it makes porting from other little endian platforms easier).
Yawn. AROS runs on multiple CPU architectures, which includes two 32-bit big endian ones (ARM is technically bi-endian too).
I have no clue why that matters, since the post that we were discussing obviously references the X86/X64 version.
Although...when it come to compatibility, the 68K version still has a long way to go.
And ARM? I was actually one of the people advocating that ISA until the developers decided on X64.
It matters as much as the lone sentence you picked out of his rant rebuts what I said.
Right...except what he said, at least in that one instance, was correct.
And all NG OS' have compatibility issues.
Jim don't confuse speed with compatibility. AROS 68K is actually very much source and binary compatible. As for i386(Abiv1) and x64 they are both source level compatible.
So you both keep saying, but the X86/X64 versions are running on a little endian cpu which does cause compatibility issues.
And no AROS port has full support for all libraries.
Basically, every port is going to require some work-arounds.
Compatibility? By that I assume you just recompile it and it works?
And now that you mention it, AROS 68K IS damned slow.
Edit: Sorry that IS a bit inaccurate. OS friendly ports for the most part do NOT require any alteration.
AROS is certain as close to binary compatibility as we are ever likely to see.
And I wish the development team nothing but good fortune (just remembered I had friends working on this).
Just ignore the over the top BS guys.
I'd edit it out, but then the post would only serve to bolster my opinion (that a compatible X86/X64 OS is kind of pointless if you have to alter code to suit the endian structure of the new cpu).
Still, as a project, pretty damned impressive.
AND, in a fork to X64, we'll face the same challenges porting existing code (with potentially less API support).
So, AROS? Still my second favorite NG OS.
[ Edited by Jim 08.03.2017 - 17:52 ]"Never attribute to malice what can more readily explained by incompetence"