V Language Review (2023)
V, a young systems programming language that once marketed itself as a safer, simpler alternative to C, Go, and Rust, is drawing renewed scrutiny for overpromising features that either don’t work or remain unfinished. Commenters highlight technical gaps in memory management, coroutines, and tooling, along with accusations that the project’s documentation and marketing blur the line between current capabilities and future goals. While a few users report positive experiences and urge leniency for a volunteer-driven beta project, many others cite repeated missed promises and hostile moderation as reasons to avoid V for serious use.
Project History & Claims
- Commenters recall long-running controversy: bold promises (simple, fast, safe “better C”, best of several languages, novel memory model) and repeated underdelivery.
- Several features and side projects (UI toolkit, browser, OS, Git host, “autofree” memory, green threads) are said to have been announced with aggressive timelines and then slipped or never materialized.
- Some see the documentation and website as “aspirational sales pitch” that doesn’t clearly label WIP features, which they regard as deceptive. Others frame it as overenthusiastic early-stage marketing by a small team.
Technical State of V
- Multiple users report hitting compiler bugs quickly and finding the language unusable for serious work.
- Specific criticisms echoed from the review:
- “autofree” is broken; arenas / prealloc are global, leak, and are not thread-safe.
- Coroutines exist but IO calls block other coroutines, so many say they effectively “don’t work”.
- Binaries are large; documentation is incomplete and hard to navigate.
- Defenders note:
- The site labels V as beta; docs say autofree is WIP and recommend using the (Boehm) GC.
- It’s impressive for a mostly volunteer effort to have a working compiler, GC integration, and tooling at all, even if rough.
- Disagreement centers on whether memory management and coroutines count as “implemented but immature” or “not actually working”.
Community & Moderation
- Multiple anecdotes describe bans or hostile responses for mild criticism (e.g., recommending Go, posting critical links), and moderators insulting critics.
- Others push back, citing high volumes of unreasonable attacks on the project and arguing that some insulation from criticism is understandable.
- There is debate over whether the community is unusually toxic and defensive, or just under siege from dogpiling.
Comparisons & Adoption Signals
- V is frequently contrasted with Zig, Odin, C3, Nim, Go, Rust:
- Zig and Nim are viewed as real but imperfect alternatives; V is often labeled “vaporware” by detractors.
- Some users genuinely like V’s syntax, simplicity, performance, and C interop for small personal projects, while acknowledging it’s not production-ready.
- GitHub stars (35k+) are seen as misleading; contributors and issues offer a more grounded maturity signal. Suspicion about artificially boosted metrics is raised but remains unclear.
Tone, Anger, and Broader Reflections
- Many find the review valuable for documenting broken promises and saving others time.
- Others criticize its highly personal, accusatory tone as part of a broader “toxic feedback loop” around V.
- Several comments suggest the unusually strong anger stems from dashed hopes: people wanted V’s ambitious vision to be real, and perceived dishonesty around that feels especially galling.