Before suggesting a solution to a problem, it's usually best to first describe the problem.
"Let's start keeping spare change in a glass jar on the kitchen table."
That might be an excellent solution to spare change getting lost and making the couch uncomfortable. It's a really bad solution for debugging a build problem in Rust.
Those receiving the suggestion will have a hard time responding without context. Don't assume they can deduce or guess the context. That way likes misunderstandings.
@liw I'm really tired of this at work. Lots of "I really like this technology, we should use it for something" with no reasoning behind what actual problem would be resolved. And when questioned, just respond with "but it's so great!".
Lars and friends