I firmly believe Nim has a marketing problem. Nim has a very technical oriented community with a "show don't tell approach". Nim market itself as a powerful tool.
But If you want Nim to grow and be used in companies, you need to convince non-technical people as well. Non-technical are usually looking for solutions to problems tather than tools - there you need to market Nim has a solution to problems companies face instead of a tool (which won't mean anything to someone who doesn't know nor care how to use it). Having a "big name" \- company or product - you can present as a success story is also really helpful because it helps trust that the technology is not just overselling without delivering (looking at you V-lang) and also that it is here to stay. You're not gonna convince a project manager if you tell him "This technology is based on an AST macro system that allows you to easily create DSL with an easy FFI to wrap C library. Oh and there are closure iterators and a fancy syntax". You're gonna convince a project manager if you tell him "This technology allows us to build prototype faster that are easy to refactor into a product packaged as a standalone binary compared to writing a Python prototype and rewriting into a C++ app. We can reduce our time to market by 30%. Oh and there are closure iterators and a fancy syntax" (yeah project manager loves a bit of technical jargon).
