Edit: other comments seem to suggest 1.) it abandons support for older hardware and focuses on modern hardware, 2.) it's supposed to allow 3D UI, 3.) it has minimal software abstractions for performance.
I guess I can understand #1, but I'm not sure why existing OS wouldn't be able to handle #2. I'm not sure how #3 works in practice if there are a lot of different hardware architectures to support.
We also aim to work on RISC-V architecture as well so helps us cater to more utility.
Please Email us at [email protected] to communicate further.
Thanks, Team XENEVA.
Granted FreeBSD could have picked up more instead, but it was almost as young and not to be due to a series of 90s decisions (BSD court case; Linux name being catchy; Linux running a bit better on 386 PCs?; GNU tools being the default?; IBM deciding to invest in Linux).
- Xeneva is not intending to be Unix like, but some core principles of Unix are followed.
- Xeneva has its own libc implementation called XECLib that are attached to Xeneva's own system call interface.
- Xeneva supports IPC via shared memory, IPC via socket and IPC via its own message based communication called PostBox IPC. Xeneva currently use framebuffer for Graphics Output, no working video driver is implemented. The framebuffer is mapped onto Windows Managers address space and the Windows Manager composes the final image to framebuffer by writing to that mapped virtual address.
- Xeneva uses PE format for executable,no doubt ELF support can be implemented. XELoader is a dynamic linker and loader process which is responsible for resolving running processes symbols by linking it to its specific shared library. Whenever a new process get spawned,and an executable is loaded, the XELoader loads all required shared libraries and link them to the process.
You can refer to our website - getxeneva.com to get a hint of our future goals and vision.
Thank you, Team XENEVA.