Re: Basic design concepts

> Well, as far as I know, we never said or wrote about Windows or POSIX
> compliance in the website.
> Unununium is about to research new Operating System Technologies and
> Techniques in order to bring a new dynamism in the operating system. So
> the
> main question is: Why having POSIX compliance ? Linux and lots of other
> operating systems already do that. Why having Windows API Compliance ?
> Windows it self and ReactOS, (and wine under linux) already do the job
> too.
> We should focus on something new, that does not follow these established
> directions, otherwise, our research does not make sense. It would be yet
> another operating system project.

Some years ago authors of BeOS tried to make a brand new system not
compatybile with other OSes and it died. I think we should have windows
compatybile like it is on Linux (a kind of emulator), but also an amount
of native apps. Of course nobody will write apps for UUU if it is not wide
used, so good idea may be writing a library for M$ Windows to run UUU apps
on it. I mean something like MSIL compiler in .NET - it gets a kind of
semi-compiled code that described the concept of an application, and
produces binary code for platform it is running on (for example adds code
that stores data in files on HD, but programmer do not have to know if
operating system his program will run on even have any filesystem, HD or
is just a lot of RAM without any storage media). Only saving files to
flashdrives, floppies and CD-Rs should be visible for programmer as
something like "filesystem". But even there an application should be able
only to call a core function that for example displays file-save dialog
box and then saves data send to it into file:

int savetofile(void *data, unsigned int length, char* mimetype);

--
Jakub Bogusław Jagiełło