[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] EmuTOS for ColdFire

... The CF step is unnecessary, IMHO. There is no m68k
cleaning that could be reused for a completely different CPU...

If "cleaning up" means getting rid of assembler dependencies, sure it helps!

...If I still were an active Atari developer I would
soon become bored by generating several different binaries (for m68k,
for CF, and for anything else that might appear) especially when I
wouldn't have a chance to test them out properly (I don't plan on buying

I consider myself an active developer, and this step doesn't bother me at all. Besides, the issue you mention would be the same regardless if we port the system to ColdFire first or not.

Also, the more different CPUs the worse situation is with the user base. In plain words - every time you upgrade the hardware to an incompatible one you loose part of users. And you don't gain any because there are no
newcomers on the horizon... Of course this doesn't matter if you don't
care about your potential users - if you do everything for yourself

Like Maurits pointed out, this has happened before. Using the same logic, there would be no sence in upgrading to the TT or falcon to begin with. Some of us get motivated by new hardware. Personally, if it wasn't for the CT60, I wouldn't have returned to the platform 5 years ago. New hardware could motivate me for another 5 years.

While on the subject; adding a CT60 to the system severely crippled compatibility with legacy stuff (a rough estimate says I lost compatibility with 95% of my games collection), but this didn't bother me at all. I think this is the case for most CT60 users actually; the good side tends to outshine the bad sides.

Please note that I am not in any way against ACP or any other hobby/ fun
project someone might come up with. I just can't agree with the logic
that is presented here in some mails. I think things work differently in
real world (and I am talking from my own experience when I release the
multi-platform software I happen to develop).

The real world? So the rest of us lives in happy fluffy land, is that it? :-)

Maybe I misinterpret you (again), but If I try to sum your post up, I get the impression it's all about "porting to a new architecture is bad in every possible way". But the alternative is to A: look at some FPGA softcore (which is probably not going to happen, and if it does, it will not beat the 060) or B: look at emulation (which isn't an option to some of us). Sure, porting the OS to x86 could be an idea, but then again looking at e.g. AROS (which has been in development since forever) this means being plagued with (severely) limited hardware compatibility.

-- PeP