... since I don't really know all that much about them. (Yes, my nerd-fu is weak.) I can, however, give some features and behavioral descriptions of what I'd like to see in a "FrankenOS".
1.,"It just works". Really good hardware detection and a set of generic drivers that will at least grant basic functionality for all essential hardware.
2. Robust documentation and error messages. When something breaks, I want to know what happened in real language, even if it's just an approximation, not some string of gobbledygook that I need a degree in CS to begin to parse. I also want clear documentation on what every part of the OS *is*, and does. Configuration options, running processes, services, threads.. the whole bit.
3. Windows level gaming capacity. Dx-whatever-the-latest-and-greatest-is.
4. A "no-bullsh*t" UI. I don't want any fancy-schmancy crap like transparent windows and animations, or retarded nonsense that tries to make my desktop look and act like a phone. No stupid behaviors like if I drag a window up to the top of the screen, it changes the size/orientation of the window.. none of that. Just let me set a picture as a background, and give me good configuration options so that other things could be added in as "plugins" if I should ever, for some godforsaken reason, decide I want them. Just make them easily unpluggable for when I come to my senses. Multiple desktops are reasonable.
"Under the Hood:"
1. Native multi-level sandboxing with encryption. "The issue isn't whether you're paranoid, but whether you're paranoid enough." Nothing that accesses the internet should get within 2 layers of the core OS. Options should exist to lie to the "internet layer" about every aspect of what the system is, does, is running, etc. from window size to OS version. Nothing accessible by a browser should remotely be able to see anything outside the box the browser is contianed in, inclduing memory spaces and the like. Ability to handle encrypting everything from file systems to memory to the bootloader. I don't care if it slows things down a bit. I want "paranoid about privacy" function.
2. Modularity by design. Components should be compartmentalized, and as independent as possible. I should be able to strip out, or not include, any element of an install that isn't explicitly necessary for the funtionality I require. Do one thing, and do it well, but that's it.
3. The ability to set hard memory limits on a per-application basis, and a really nice memory management system that polices those looking for crud and cleaning.
4. Comprehensive versioning management relative to the OS itself, and the ability to "roll back" updates that make a mess due to being broken. Similarly, an in-built VM that lets you test out any prospective updates in its own sandbox prior to them being allowed to go live.
5. The ability to "hard kill and purge" any app that is found to be misbehaving. As in "immediately brute force stop it from doing what it's trying to do, and completely flush the memory space." Preferably by some keystroke combination that doesn't involve needing to have some kind of task manager always running to execute.
6. A good, intuitive, logical/physical drive management system for all OS functionality and components. Specify what drives/segments are used for OS files, swaps, temporary files, sandboxes, etc.. each with versioning control, journalling, etc.
7. Specific update management sorting. Deliberate blocking of "schedulers" and "auto-update tools" and the like.. permissable only maybe in certain areas of sandbox nests. It's manual and requries explict user enaction, or it doesn't happen, period. Same with "helpers" or any other of these bullsh*t "always on in the background" programs that companies love to infest systems with these days.
1. "Free as in Freedom, not necessarily as in Beer. But beer is good too if it can be swung."
2. "F*ck DRM"
3. "F*ck advertising and tracking anything, and f*ck companies that support such evil."
4. "The system belongs to me, and it does what *I* tell it to, not what some asshat from some big company thinks i ought to want to do with it."
Yes, I realize that this will probably wind up being bloated, slow, and crufty... but I'd gladly pay for more powerful hardware to handle functionality like this.