Hacker News Reader

Comment by Almondsetat | Hacker News Reader

Go and Rust have much worse tooling for enterprise-level collaboration

I'm not sure what enterprise-level collaboration means. In my experience, "enterprise" usually means: "Let's use tools that are 10 years behind, buggier than average, and have lots of half-baked features, none of which we need".

I'm not sure what kind of tools you mean, but unless you're looking for something that just works exactly the way EJBs do for some mysterious reasons, I don't see why you can't do most "enterprisey" things with Rust or Go. Or Python or TypeScript for that matter.

> Let's use tools that are 10 years behind

Yes and that's exactly what modern tooling is missing. Try to develop for node.js 0.2.12 on today's update of Visual Studio Code. See? No enterprise-level collaboration for ya.

I've found the challenge of running a non-existent version on a tree that was EOL 16 years ago is typically keeping it up with internal security standards, and not one of new collaborative development.

> internal

Exactly. Never updated, never discussed, never challenged. Set in stone.

Do they?

It felt like every dev that worked on our Java behemoth at a previous job was elated to switch to Go.

I don't think they do. I work in a maven shop and half of the people don't even know what to do when maven fails inexplicably

Haven't they heard of Gradle or Bazel?

Most likely because it was a behemoth, not because it was in Java. Would be curious to see how they like dealing with a golang behemoth instead (golang is much less suited for dealing with large codebases).

Reply on news.ycombinator.com