3 ms·
Go and Rust have much worse tooling for enterprise-level collaboration
by Almondsetat 19d ago
Go and Rust have much worse tooling for enterprise-level collaboration
- doublepg23 19d agoDo they? It felt like every dev that worked on our Java behemoth at a previous job was elated to switch to Go.
- unscaled 18d agoI'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.
- egorfine 18d ago> 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.
- dwaite 17d agoI'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.
- egorfine 17d ago> internal Exactly. Never updated, never discussed, never challenged. Set in stone.