- AmigaOS4 don't have any form of protection from it's own tasks (any badly behaving app can kill the whole system, which is what happen frequently..means *a lot*)
- doesn't have utf8 support
- lots of documents cannot be viewed or edited (no support for this or that format).
- there's no up to date and css capable browser
- no large file support
- it use an old (1993) outdated API, thus terribly limitating
- the moderation on amiga sites is way too strong. anything that doesn't please get deleted or edited without your consent.


It's up to you (OS4 devs and Amiga sites moderators) to change theses facts and thus make Amiga world a more interesting place for potential new users.

FWIW, I am not saying that AmigaOS 4.0 is a dead end design. However, everybody with half a brain cell will agree that to evolve the current design, you need to do something about the way certain things are handled right now.

Apple did the same thing. They invented the Classic environment for binary compatibility, Carbon for source code compatibility, and Cocoa for the new stuff. This is very similar to what we want to do:

- A virtual environment to run classic OS 4 binaries in.
- A compatibility library that will allow you to compile OS 4 source code to the new system, trying to stay as compatible as possible and to go with as little changes as possible, with possibilities to narrow down incompatibilities (like with Carbon where you could "close" system structures and use new accessor functions).
- A new API for the "native" stuff.

The virtual environment may still be self-hosted for resource-limited devices, and will be continued to be developed.

If you really think that AmigaOS can be developed into a more modern system without doing this, you must clearly have a different idea about "modern" than I have. But memory protection is a must, and it simply is NOT POSSIBLE with the open structure approach that we have right now.

Our plan is to move everything up one layer, i.e. make the HAL a software implementation based on a newer kernel, with the old system running as a separate task but using services from the new system.

The compatibility break is inevitable. We've seen it again and again, last time with the pager support - the current (beta) kernel supports swapping to disk. However, there are a lot of exceptions of memory that can simply not swapped (mostly because of the memory protection issues again).

Of course, there should have been a smiley after that statement (oh, hold on - there was!). I wasn't being entirely serious.

Oh, and Mikey, IIRC you didn't even pay for your A1, so you are contractually obliged to give it away rather than sell it.

Call me weird, but I find that the crowd that runs with that system, most rude, crass, and hostile, not people I would go to a bar with. I do not like them, and if effika's MB's were $5, I WOULD NOT get one.

If you still wish to defend ACK,

Are you sure?

I was wondering, how many people that own an (m)A1, would you also buy the Samm440, or get one and sell on your (micro)AmigaOne?

Me personally, having never had trouble with mine, would want a Sam440 as well (prefer the higher powered Moana, though).

I couldn't part with my A1 as it's faster and will never be available again. (Nothing like knowing Altivec is in there.)

That FPGA is irrisistable, wish it was in the Moana too.

I haven't moved to SFS as yet. Basically because in earlier days there was no recovery action for SFS, has this changed, my FFS partitions veg out at time but can recover.
I know SFS is a lot faster than FFS but not being technical I don't want to risk things.

I've heard there's an updated version that shows colours correctly on OS4-final but where could I download it?