Come on now. Network support including SAMBA is available on the AmigaOS, Virtual memory is simply not required when the code is so compact, efficient and elegant.
Platform Independence and multi-user security would certainly be added very quickly.
So the only issue is the GUI built into the kernel. Which is not built into the kernel. It resides in libraries loaded if desired. AmogaOS from 2.04 up can certainly boot without launching the WorkBench(tm). You can even unload the Workbench without reloading, just be sure to leave a CLI running before loading WB.
Limiting Amiga to just one box and one OS at this point would be like offering the world a better horse and carriage at the dawn of the automotive age.
Actually, the simile is just wrong. Limiting Amiga to one (Better) box and one (Better) OS is like offering a V-8 Cadillac when everyone else is still driving percherons and drays.
Slashdot Mirror
Come on now. Network support including SAMBA is available on the AmigaOS, Virtual memory is simply not required when the code is so compact, efficient and elegant.
Platform Independence and multi-user security would certainly be added very quickly.
So the only issue is the GUI built into the kernel. Which is not built into the kernel. It resides in libraries loaded if desired. AmogaOS from 2.04 up can certainly boot without launching the WorkBench(tm). You can even unload the Workbench without reloading, just be sure to leave a CLI running before loading WB.
Limiting Amiga to just one box and one OS at this point
would be like offering the world a better horse and carriage at the dawn
of the automotive age.
Actually, the simile is just wrong. Limiting Amiga to one (Better) box
and one (Better) OS is like offering a V-8 Cadillac when
everyone else is still driving percherons and drays.
Amiga Architecture was always very efficient with the use of RAM. My Amiga 2000 has 32 MB which is more than enough for any application.
If the new machines are well designed, 32MB should be sufficient for almost everybody.