While playing around with my subversion repository it occured to me. If „female“ is a branch (codename: Eva) of the „male“ trunk (codename: Adam)… but was never merged back… „male“ must be the latest stable version of the project human.
This unstable version status of the female branch sure explains a lot. Oh sure, it is somewhat more advanced. The GUI for example. Looks way better than the stable male version, I’d never touch some parts of that. But this is also the first problem. For some uses, it’s more difficult to handle, hard to find all the buttons and sometimes they work better or worse than other times or even trigger a totally different event. Then there are better sensors. Being able to tell the difference between 20 different kinds of yellow is surely an advanced feature. And they are able to fork child processes. Okay, this feature is a bit buggy, since the forks don’t share a common memory with the other processes. Inheritance doesn’t work very well, too. You you still have to pass on some arguments during runtime to make it a working process. Heck, they can’t even handle buffer overflow at start. But that’s another topic, back to the „Eva“ branch. And speaking of arguments… don’t try. This feature has a messed up configuration. ‚Nuff said ‚bout that. Like most developer versions, it’s output is set to verbose mode. If you don’t watch it, the data might cause your disc or memory to overflow/crash. Unfortunally this is hard to filter. Most times you try this, it gets even worse. But the females own logs are quite detailed. The branch version can recall error events which are years back. Obviously all these features need a lot more resources. Especially a large set of themes to customize. The boot part alone can fill many racks. So be sure you are able to support upgrades for your female.
Overall you have to be careful with the unstable female version. While it has some great features and is really fun to handle… it might blow up in your face now and then…