HyperionMP wrote:
Which doesn't mean that you haven't even looked at it, >which would be really hard to believe (in other words, I >wouldn't believe you if you told me that you never ever >LOOKED at the AROS source code).
Quite frankly I could care less what you believe.
I wouldn't have expected anything different, and, quite frankly, I don't care that you don't care.
Why would we look at the AROS codebase when we have the entire OS 3.x codebase sitting in a CVS barring a few minor additions by H&P themselves?
Just because it exists, and many issues that you've certainly had to face have been faced by the AROS developers. Come on, dude, people are not stupid like you want to believe they are.
If you are Fabio Allemagna,
Nope, I'm Fabio Alemagna. Learn how to spell my name correctly, thanks :-)
the self-styled GPL Warrior who doesn't even understand the GPL himself,
LOL :-) There he goes with his personal attacks and bullshit :-) For one who doesn't understand the GPL, it's a quite big achievement to obtain the guilty modules to be removed from the guilty software. But I really want you to PROVE your claims, for once, so I'll wait for you to show me what you're talking about.
I'm not surprised to see that contrived reasoning you come up with next.
Yeah, right... :-) Did you even think for a moment that I was waiting for other kind (which means "reasonable") answers?
Get a life Fabio.
How nice of you to suggest me that... but thanks, I already have a pretty happy one. I don't think the same can be said about yours, though. (DaveP, still defending Hyperion after such words? Shame on you, if you are).
You know as well as I do that AROS is not fully binary compatible with OS 3.1.
Dude, that's not what you said. You said that AROS is not
MEANT to be binary compatible with AOS, which is an outright lie, and the AROS webpage contraddicts your very same words. There's only
one place where AROS is not compatible by
design and that place is 99% of the times not touched by applications, but only by the shell and by filesystems (which hasn't stopped us from porting filesystems from AmigaOS without almost changing one line of code in them). But even if it was
that what you were referring to, you're still in contraddiction with your very same words, because it seems that this incompatibility hasn't stopped MOS from using AROS
and be binary compatible with AOS.
Now, dude, what about you getting some clue and even a better life?