sched-ext: Added essential answer to a common question

Author: Aarrayy

src/content/docs/configuration/sched-ext.mdx

@@ -1049,6 +1049,14 @@ auto_mode = ["--performance"]
 
 ## FAQ
 
+### There are so many options... why wouldn't you just make one scheduler that is good at everything?
+
+- The main reason is that there is no one-size-fits-all solution when it comes to CPU scheduling. Different workloads have different requirements and priorities, and a scheduler that is optimized for one type of workload may not perform well for another.
+
+You could view CPU schedulers as different pairs of shoes, each designed for a specific activity. For example, running a game on a scheduler that is optimized for server workloads may lead to suboptimal performance and increased latency, while using a scheduler designed for gaming on a server may result in inefficient resource utilization and reduced throughput.
+
+That's the magic of sched-ext. Limitations are no longer a problem.
+
 ### Why X scheduler performs worse than the other?
 
 - There are many variables to consider when comparing them. For example, how do they measure a task's weight? Do they prioritize interactive tasks over non-interactive ones?