I think the more appropriate analogy is there's more to a drill than the drill. When you buy a Milwaukee drill, because it shares a battery with other Milwaukee parts, it's easier to buy more Milwaukee tools.

So it helps to choose a drill brand with the ecosystem you like, not just one that's a serviceable drill.

(Or you could argue that a language's ecosystem is part of the dang language. Which I agree with).

▲

giancarlostoro an hour ago | parent | next [-]

I still attribute a rich OOTB standard library for Go’s success. You have an OOTB production capable web HTTP server baked into the standard library since practically day 1?

	▲	purplemoonx an hour ago \| parent [-]
		Have you never heard of Node.js where they got the idea from

▲

purplemoonx an hour ago | parent | prev [-]

Fair points, but those preferences seem more grounded in reality than the abstract reasons people say they love a language beyond its interface

▲

oblio an hour ago | parent [-]

Libraries and frameworks and package management absolutely matter. They're not some abstract thing, they could be the difference between something being done in 6 months or in 2 years.

Why do you think people put up with Spring?

	▲	purplemoonx 19 minutes ago \| parent [-]
		1000% that's why I said "Fair points" I consider npm to be part of "the interface of JavaScript" and to your point it's one of the strongest reasons beyond performance to use Node over some other dynamic language like Ruby or PHP. Python earned its keep mainly because of its library ecosystem (again to your point) but also due to its simple, teachable syntax. My point is that Python is not used because it's highly performant - it's basically the slowest language there is. But because people like the syntax and the library ecosystem (AKA the interface to the language)