0.OS should be as fast as possible.
1.OS should use the least memory, unless it hurts #0.
2.OS should have the most security, unless it hurts #1,#0.
3.OS should have the most compatibility, unless it hurts #2 , #1,#0.
4.OS should have the most features, unless it hurts #3,#2,#1,#0.
Name:
Anonymous2013-08-07 9:50
Operating systems are essentially deprecated, I can already do 99 percent of what I want from within a web-browser.
Name:
Anonymous2013-08-07 9:59
>>2
A web browser is just a layer which utilizes OS resources. You're still using an OS.
If you're making an embedded system like Rockbox, your rules are the best. If it's connected to the Internet, security is king. If you can get rooted just by connecting to the Internet, it's crap. If it automatically downloads and runs executable code a la ActiveX in IE 4, it's crap. If every program has raw access to every device as an ordinary user, it's crap. If there's no memory protection (per-process address spaces, segments, a VM, or type tags), it's crap.
Name:
Anonymous2013-08-08 17:09
>>9
For embedded systems reliability and predictability become the most important rules. For practical reasons, you often also have to prioritize resource consumption over speed.
Name:
Anonymous2013-08-08 18:10
5. OS should allow for the easiest getting of dubs, even if it hurts #3,#2,#1,#0.
Name:
Anonymous2013-08-09 0:05
0. OS should be like Unix
Done.
Name:
Anonymous2013-08-09 0:20
OS should have the most security, unless it hurts #1,#0.
So basically no encryption at all.
Your design sucks. It would be fast, memory wasting and insecure.
It should be written in C.
It should use lightweight C library like musl.
Everything should be statically linked.
The tools should work efficiently together.
The base system should be minimal.
The file system hierarchy should be simple and minimal.
It should be combine the best features of BSD and GNU/Linux.
It should have package management and trusted software repositories.
It should use rolling-release.
Everything should be well documented.
It should have good hardware support.
It should have good APIs to attract developers.
At first it would be good to have emulation for dynamically linked binaries, linux binaries, linux proc filesystem etc..
Name:
Anonymous2013-08-09 5:36
lel I'm such a nerd I start my lists at index 0. *giggles*
>>25
Let's: https://en.wikipedia.org/wiki/POSIX
Let's scroll to the bottom and look at the "See also" section, which may have relevant nformation on the article that I am reading. TRON project – alternative OS standard to POSIX
why oh my, there are such things