I think he left off the most important comparison: Nim is actually available while V will be "open source mid 2019." I'm really curious about V and applaud what the author is doing, and I am eagerly looking forward to trying Volt when it's a little more stable. The comparison he wrote is is mostly based in reality, but it's also a little... optimistic.
> V's syntax is a lot cleaner with much fewer rules. Lack of significant > whitespace improves readability and maintainability of large code bases and > makes generating code much easier. That's an... interesting take on whitespace. (Particularly since all the V example code includes whitespace exactly where you'd find it in Nim or Python, whether it's required of the language or not.) There are certainly arguments to be made against syntactically significant whitespace, but those arguments aren't really being made here. > The list can go on and on. Nim is a language with a lot of features, still > developing and changing. V is not going to change much, if at all. This comes across as naive to me. It's a language that's currently used by 1 person (from my understanding) on a small handful of projects. It probably works great for those use cases as they are but once it hits the real world and other people begin to use the language there will almost certainly be changes. And if there aren't those other people aren't likely to use it. (Which is perfectly fine, except that the author wouldn't be writing these comparisons if he didn't want others to use V.) Change is neither good nor bad, it's simply a sign of evolution and growth.
