Enterprisey usually means high-overhead, tuned to require many developers to achieve what would be done by one on a less enterprisey system.

This quality is attractive to managers who benefit by increased headcount, and prefer to have their "reports" or "resources" less generally capable, and more easily replaced or shuffled. Total cost is much higher, but individuals' salaries are lower, which makes managers look good.

Java and .Net are both very enterprisey platforms.

> high-overhead

You understand that all the things done in Java and .NET’s “enterprisy” way can be done is most languages right?

This is a programmer problem not a programming language one. Today you have to write less in C# than GoLang, to do the same tasks. Does that mean GoLang is enterprisey now, just because you have to write more?

Not "just because". Go is exactly as enterprisey as Java and C#, and for exactly all the same reasons.

And, it is not a programmer problem. It is a management problem. None of them would exist without management demand for minimally-productive languages.

What a weird hill to die on. I have a hard time believing “management” woke up one day and said: “how can we make the most minimally productive language”.

Tell me about this secret non “enterprisey” stack you are using.

Management does not make languages. They use what exists that satisfies their need for large head count. Sun and Microsoft were happy to provide it for them.

Again tell me what you think is not enterprisey then. I would like to open my mind to it.