4 ms·
> In the end there is no one true best language out there. Go is great for a subset of problems and making it better at other things is a balancing act. This i
by laumars 11y ago
> In the end there is no one true best language out there. Go is great for a subset of problems and making it better at other things is a balancing act.
This is the problem though - I think many people expect there to be a "one language to rule them all". Personally I like having lots of different languages that excel at some problems even if that means they fall short at other problems. But I think some people either want to specialise in a specific language, or spend so much time looking for perfection that they miss subtle beauties amongst a forest of flaws.
- nine_k 11y agoIt's OK to see a language that has certain strengths but also some weaknesses due to the nature of the strengths. It's sad to see a language that has certain strengths but also some painful weaknesses for no good reason except that it's v.1. So far the best I've heard is something like "We understand there's a problem for certain users, and we don't rule out adding generic types some time later, but it's hard and our priorities are different". It is indeed not easy to do well (though Java has somehow managed to find a satisfactory solution). Well, I'll wait a few more years.
- gendoikari 11y agoI think the language that wanted "to rule them all" was C++, and we all know how it ended. C++ can be procedural, oop, functional, you have metaprogramming, generics, everything. Everything. C++ is everything. Every pattern, every design philosophy can be implemented in C++. How much time does it take to compile? How many developers do know every C++ feature and pattern?