SaaSHub helps you find the best software and product alternatives Learn more →
V Alternatives
Similar projects and alternatives to v
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
WebKit
Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
-
dagger
Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud (by dagger)
-
-
-
-
-
earthly
Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
-
v discussion
v reviews and mentions
- Solod v0.1: Go ergonomics, practical stdlib, native C interop
- GitHub's Fake Star Economy
- Vlang 0.5
-
VLang 0.5 Released
> Does anyone understand what the end objective of V is?
The Vlang site makes it clear what their objectives are[1]. "Simple, fast, safe, compiled. For developing maintainable software." They also have a roadmap[2], showing what their end objective (or production release) is.
> I've known about this language for I think 4-5 years and for some reason it's still v0.5...
They just came out with version 0.5 (2 weeks ago from this post), so obviously that statement is mistaken.
[1] vlang.io
[2] https://github.com/vlang/v/blob/master/ROADMAP.md (vlang's roadmap)
-
Zig programming language 0.6.0 release notes
Appears to be a tactic, to cause confusion with releases coming from other programming languages, because otherwise this doesn't make too much sense.
For example, V (Vlang) went to 0.5.0 (December 31st) and C3 is 0.7.8 (December 6th).
[1] https://github.com/vlang/v/releases/tag/0.5
[2] https://github.com/c3lang/c3c/releases/tag/v0.7.8
- V programming language version 0.5 released
-
Rue: Higher level than Rust, lower level than Go
> Im more interested to know the points in relation to autofree.
As sibling said, autofree is still stated to use a GC, which obviously disqualifies it from "memory safety without GC".
> Regarding the details, here is a pretty informative github discussion thread on same topic: https://github.com/vlang/v/discussions/17419
I did see that! Unfortunately it doesn't really move the needle on anything I said earlier. It describes manual memory management as an alternative to the GC when using autofree (which obviously isn't conducive to reliable memory safety barring additional guardrails not described in the post) and arenas are only mentioned, not discussed in any real detail.
> It is also accompanied with a demo video (pretty convincing in case you would like to watch).
Keep in mind the context of this conversation: whether V offers memory safety without GC or manual memory management. Strictly speaking, a demonstration that autofree works in one case is not sufficient to show V is memory safe without GC/manual memory management, as said capability is a property over all programs that can be written in a language. As a result, thoroughly describing how V supposedly achieves memory safety without a GC/manual memory management would be far more convincing than showing/claiming it works in specific cases.
As an example of what I'm trying to say, consider a similar video but with a leak/crash-free editor written in C. I doubt anyone would consider that video convincing proof that C is a memory-safe language; at most, it shows that memory-safe programs can be written in C.
- V Programming Language version 0.4.12 released
-
My Foray into Vlang
I don't think it's fine the way V does it. What V's compiler is essentially doing is that it parses the V code into an AST, then it walks the AST and tries to generate an equivalent C code on the fly:
https://github.com/vlang/v/blob/master/vlib/v/gen/c/match.v
How a proper compiler should work (and how they actually do from what I've seen), is that they first take the AST, try to remove all fancy syntatic sugar by converting it to simpler constructs, and then they generate an intermediate representation that's either stack, or SSA based. It might skip the lowering of syntatic sugar, and generate IR directly. At some point either on the AST, or the IR, you might want to do control or data flow analysis to support some of your features.
From that point on, the backend generates either LLVM IR, C or might even attempt to generate machine code itself.
The problem with targeting C is that you lose access to stuff not accessible in C, like precise variable tracking on the heap/stack (needed for a good GC), or unwinding support needed for exceptions.
- The V Programming Language
-
A note from our sponsor - SaaSHub
www.saashub.com | 9 Jun 2026
Stats
vlang/v is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of v is V.