>Ain't it great to have a choice?
Not if the choice leads to duplication of effort, smaller community, feuds and conflicts, decision fatigue, and so on.
Not if the choice leads to duplication of effort, smaller community, feuds and conflicts, decision fatigue, and so on.
* Better feature stability, * Robust and well-defined standards, * improved security, * better debugging options, * and most importantly competitive pressure.
Just look at how LLVM pressured GCC into shape. I'm primarily a GCC user, but I'm very very grateful for LLVM's existence. Also multiple equally competent compilers disincentivise them from going rouge (e.g. .net telemetry).
Weighing the pros against the cons, I'd have to stand with GP in saying that choice is good.
Heh, yeah, let's go ask the JS frontend community about this one... oh dear.
Not if it leads to water intoxication.
Whereas the things I mentioned are endemic in many communities with such choices between different implementations.
So not an apt counter-argument. An analogy doesn't just need to be somewhat similar to the situation -- it needs to have similar ups and downs too.