ihaque's description of CDE is a bit misleading. The point of this tool isn't so that you can install applications easily. The point of this tool is reproducibility. You should only use CDE when you need to exactly reproduce your environment on a different machine.

The target audience of this tool is testing and research, not the general population.

This isn't meant to be a general install mechanism. You should only use CDE for testing/research purposes when you need to reproduce your environment on a different machine.

ihaque's description mis-characterizes the point of this tool. It's certainly not meant for everyone

CDE isn't meant to be a general install mechanism. You should only use CDE when you need to exactly reproduce your environment on someone else's machine for *testing* purposes.

The example use case of an executable bug report opens up enormous possibilities. You would no longer need to ask the user for information, you can just run the user's setup yourself to gather bug information.

CDE isn't meant to be a general install mechanism. You should only use CDE when you need to exactly reproduce your environment on someone else's machine for *testing* purposes.

The example use case of an executable bug report opens up enormous possibilities. You would no longer need to ask the user for information, you can just run the user's setup yourself to gather bug information.

Ingo's benchmarking completely misses the point of BFS though, which is probably why CK is frustrated. Ingo's benchmarks only measure throughput, they don't measure latency or responsiveness, which is the whole point of BFS.