Group 1 - The article discusses a situation where a successful Rust project led to its eventual discontinuation within a company due to management changes and a lack of understanding of its value [1][6][9] - The company initially chose Rust for a real-time service due to its superior performance in tests compared to other languages like Ruby and Node.js [3][4][5] - After the successful implementation of the Rust service, the company shifted its focus, leading to the disbandment of the Rust development team and a lack of further investment in Rust technology [6][7][8] Group 2 - The new management, upon realizing the Rust service was stable and required little maintenance, decided to phase out Rust in favor of more familiar technologies like Ruby and Node.js [7][8][9] - The attempt to rewrite the Rust service in Node.js failed due to the inherent limitations of Node.js in handling high concurrency, highlighting the complexity of such a transition [9][10] - The article reflects a broader industry trend where successful projects can be undervalued or misunderstood by new management, leading to missed opportunities for innovation [10]