[coldtea]

>but having all those things go would become another C++ with a different syntax.

Haskell and CL have "all those things" and they are not "C++ with a different syntax".

I don't know why people repeat these cliches... It's not like a language can't have many features and be designed well at the same time. It just takes preparation and effort instead of ad-hoc additions (like with C++).

[duaneb]

I'd argue either are just as bad as C++ if you actually use all those features, just like NOT using all those features turns your C++ readable.

I'd also argue that Haskell does NOT support all the features directly but implements them through the language, which is a Good Thing.

I consider CL a mess, so I probably shouldn't comment on it.

[geodel]

But then there need not be raging debate about Go/Generics. As pragmatic developers can move to Haskell etc if Go has no value add to them.

[coldtea]

That reminds me of the "If those books say something worthwhile, it will be in the Kuran, too, so it's ok to burn them. If they don't, they it's ok to burn them anyway" argument -- something a sultan is alleged to have said as the justification for burning the library of Alexandria.

The thing is, it's not just the feature set, different languages have lots of different things going (or not going) for them too.

One might like Go's syntax over Haskell's.

Another might not like Haskell's purity.

A third might not like Haskell's heavyweight platform installation and tooling.

Another might be forced to use Go because of his work but still hate the lack of Generics.

Yet another might prefer Go over Haskell just for the fact that you can find Go jobs, where Haskell jobs are too few and far between.