> "The issue of whether or not to use Go instead of Rust seems inevitable in any organization." It is not inevitable; it barely ever happens. This single line

> "The issue of whether or not to use Go instead of Rust seems inevitable in any organization." It is not inevitable; it barely ever happens. This single line shows the extreme bias of the author. Rust is new and exciting, but it's not the best at everything nor nearly as productive as Java or Go at general webapps. Engineering needs to serve the business and get things done, not vacillate on language decisions. This was a rather big waste of effort and I blame leadership for allowing it to continue as far as it did.