According to their roadmap, they will do 0.5 and then go for 1.0. Which at their pace, seems like it will be this time next year, if not earlier. They are coming along quite quickly and nicely. Seeing V people doing lots of nice things and projects with it.
https://github.com/vlang/v/commit/ba38c94a403b72222508a85704...
Let's add some context here, because a lot of times people that don't use the language, can interject drama. That's not what my post was about.
The gap between version 0.3 to 0.4 appears small and haven't experienced any issues so far (0.4 just came out). "vfmt" should handle those without issue. V became beta with 0.3, so if talking 0.2 and below, it was still in alpha.
If talking 0.1 or 0.2 to 0.3 or 0.4 (alpha to beta), that becomes a depends type of thing. For simple(r) programs, likely no issues. For more complex and very large programs, the difference can mean its better to rewrite. One of the reasons can be to take advantage of newer features. This can also be a non-issue for various people that didn't start using V until version 0.3 or later, so don't have anything written in 0.1 or 0.2 nor use libraries from that far back.
It should also be noted, that 3 years ago, would mean 2020. The alpha of the language came out in 2019 (4 plus years from today), so there is going to be a natural "time gap", that is not covered.
Additionally, I rather wait for the language to be a little more stable, as to be clear what the more definitive feature set and syntax is, before using in production. Be that as it may, enjoy using the language, and have various programs using V that run without issue.
Going to try it out.
On the fun front, it seemed a bit like my earlier simple uses of D, although D is complex or at least big, overall, compared to V.
Also in fact, I was thinking what the name V stood for. Now I think it may stand for Vibe, because it vibes with people, or should that be the other way around? Heh.