HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vlang
v
V2019–2026
vlang / v

v

Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io

Languages & CompilersLibraries & SDKs
Explore on GitHubRead Hacker News discussions
102Distinct people
234Mentions
1Explicit recommenders
38.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

V is not vaporware - I use it daily, so do hundreds of other developers - see the commit log at https://github.com/vlang/v/commits/master . Have you tried it yourself? It takes…

delian66 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

  • vlang/vc · linked in 2 of the same discussions
  • vlang/vinix · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year234 dated mentions

Observed mentions: 2019-02-09 02:02:36 UTC to 2026-10-07 10:26:09 UTC.

0204060802019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 37 mentions; 12 submissions, 25 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 18 mentions; 3 submissions, 15 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 23 mentions; 4 submissions, 19 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 84 mentions; 5 submissions, 79 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 21 mentions; 6 submissions, 15 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 24 mentions; 3 submissions, 21 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 12 mentions; 4 submissions, 8 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC371225
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC18315
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC23419
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC84579
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC21615
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC15411
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC24321
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC1248

What Hacker News says

234 sources
baranul·Oct 7, 2026
> Alex has time and time again promised to write blog articles on various aspects of V's development. Had he done that... There are a number of problems with this statement and others made: (1) Alex (and other contributors to the V project) have written blog articles, a changelog, and a roadmap[1][2][3][4][5] (2) To not know of Alex's (and other contributors) blog posts or tweets (Twitter/X), gives the impression of only reading misinformation from specific outdated negative blogs, and not having a fair or balanced view. > independent language creators > think you misunderstood the article Others can say you are misunderstanding the perspective given by another language creator who is showing respect for how far the V project has come and what they had to overcome: (1) Real reviewers of languages, review other languages, not specifically
Read the rest
target a language or creator. (2) It is not honest or valid criticism to engage in defamation or insults because someone created a language one doesn't prefer or is competition. (3) Languages are not static. They develop, change, and fix things. Which is what the V project does and should be acknowledged for doing. (4) People will notice when a suddenly self-anointed reviewer of language is presenting outdated, unfair, misleading, or unbalanced views. As if the sky is falling by selecting a few difficult issues from a clearly developing language, while their preferred or other languages and creators have 2,000 or 20X more issues. Refs: [1]: https://vlang.veery.blog/ (blog link at top of the vlang.io site) [2]: https://github.com/vlang/v/discussions/categories/blog (blog link on left side of github.com/vlang/v/discussions) [3]: https://x.com/v_language (vlang on twitter; tweets similar to blog posts) [4]: https://github.com/vlang/v/blob/master/CHANGELOG.md (changelog) [5]: https://github.com/vlang/v/blob/master/ROADMAP.md (roadmap)
In The bizarre world of the V Programming Language
baranul·Sep 28, 2026
Looks too weird to repost an old 2023 rant about an alpha or very old version of a language, in 2026. Particularly when it's full of outdated, questionable, or outright misinformation. Languages in development are not static, they change. * VUI, Delphi-like visual editor, iOS support There is now UI2 (VUI2)[1]. Along with GUI (official alternative UI toolkit)[2], many other UI toolkits (Simple_GG[3], IUI...), and bindings for raygui, dear imgui, etc... UI2 (VUI2) has a WYSIWYG visual editor called UI2 Studio and supports both iOS and Android (along with desktop). * C2V Is used for many different V projects, like their raylib bindings, for example. * Memory Management There is flexible memory management, meaning the user is provided with various options to choose from, and where V's libraries are separate from and don't depend on any of t
Read the rest
hem. Options: GC, VGC (V's GC), autofree, ownership, arena, manual... The default is GC or VGC (for user convenience). VGC is already built and going through testing. The other options are for experts, going through their phases of development. V's Rust-like or Dlang-like inspired ownership was used to translate Rust's ripgrep to V[4]. * Documentation V's documentation is constantly updated, the language has several books written on it (available on Amazon), to include 3rd party sites with detailed tutorials or hundreds of code examples: Exercism, Rosetta Code, Codefreelance, (Codecaine)[5]... * Coroutines V has ported goroutines[6] and is a default library, in addition to having photon as a 3rd-party. Photon is still under active development and has made it clear (years ago) that they would support the Windows OS[7]. * Presenting neutral 3rd party opinions The unhinged looking ranting at the bottom of the blog demonstrates it's not neutral, shows odd personal issues against an entire community, involves specific targeting for dubious reasons, etc... * Neutral, more recent, and 3rd party opinions: The V Language: The Best Parts of Go, Rust, and Python — All in One (2026)[8] What Can I Do with Vlang? Programming Benefits Explained (2025)[9] V Language: Simplicity Made Sexy (2025)[10] Exploring V Language’s Latest Update (2024)[11] Refs: [1]: https://github.com/vlang/ui2 [2]: https://github.com/vlang/gui [3]: https://github.com/codecaine-zz/simple_gg [4]: https://github.com/vlang/ripgrep.v [5]: https://codefreelance.net/apps/vlang.html [6]: https://github.com/vlang/v/tree/master/vlib/goroutines [7]: https://github.com/alibaba/PhotonLibOS [8]: https://levelup.gitconnected.com/the-v-language-the-best-par... [9]: https://pythongeeks.net/tutorials/what-can-i-do-with-vlang-p... [10]: https://medium.com/@connect.hashblock/v-language-simplicity-... [11]: https://medevel.com/exploring-v-languages-latest-update/
In V Language Review (2023)
wk_end·Sep 17, 2026
If I go to the vlang releases page, I see literally hundreds of releases https://github.com/vlang/v/releases They haven't had a stable 1.0 release yet, but they've had many pre-1.0 releases. It's not some personal experiment that's been sitting in the dev's Github that people are piling onto; the author has gone out of their way to promote it, beg for donations, and lash out at any criticisms. The issue has never been the quality of the language per se, the issue has been 1) wildly misrepresenting the quality of the language in the present tense; 2) not even having any kind of a realistic roadmap towards achieving the kind of outsized and implausible claims about the quality of the language; and 3) using these outsized, implausible misrepresentations as a way of soliciting hype and funding for the author.
In Vinix – A modern operating system written in V
baranul·May 7, 2026
The issue is there are a number of Golang alternative languages. Solod has a lot of competition (from most to least GitHub stars): 1) https://github.com/vlang/v (Vlang) 2) https://github.com/odin-lang/odin (Odin) 3) https://github.com/goplus/xgo (Xgo, formerly Goplus) 4) https://github.com/borgo-lang/borgo (Borgo) 5) https://github.com/mitchellh/gox (Gox) 6) https://github.com/MadAppGang/dingo (Dingo) 7) https://github.com/ivov/lisette (Lisette) 8) https://github.com/anzellai/sky (Sky) 9) https://github.com/halcyonnouveau/soppo (Soppo)
In Solod v0.1: Go ergonomics, practical stdlib, native C interop
baranul·Jan 14, 2026
Vlang compiles to human readable C too, like Nim, not Odin and Jai. Here's a post to read on V's rational for doing so[1]. Incredibly, some vocal competitors mocked V's developers for its decision, then years later, have been quietly trying to copy or "steal" other ideals without giving credit (that they previously made fun of). V's approach is to have various backends, in addition to native (to be focused on from 0.6); C, JavaScript, WASM, etc... [1] https://github.com/vlang/v/discussions/7849
In Zen-C: Write like a high-level language, run like C
baranul·Jan 13, 2026
> 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 version (or production release) will have. > 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)
In VLang 0.5 Released
aw1621107·Dec 22, 2025
> 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
Read the rest
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, which is a very different claim.
In Rue: Higher level than Rust, lower level than Go
freakynit·Dec 22, 2025
"none of those stand out as "memory safety without GC" to me" ... can you explain why you believe they are not memory safe without GC? Im more interested to know the points in relation to autofree. Regarding the details, here is a pretty informative github discussion thread on same topic: https://github.com/vlang/v/discussions/17419 It is also accompanied with a demo video (pretty convincing in case you would like to watch). V-lang is not shiny as other languages are, but, it does have a lot to learn from.
In Rue: Higher level than Rust, lower level than Go
aw1621107·Dec 22, 2025
> Check out V-lang ... it has the details. Does it? From its docs [0]: > There are 4 ways to manage memory in V. > The default is a minimal and a well performing tracing GC. > The second way is autofree, it can be enabled with -autofree. It takes care of most objects (~90-100%): the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via GC. The developer doesn't need to change anything in their code. "It just works", like in Python, Go, or Java, except there's no heavy GC tracing everything or expensive RC for each object. > For developers willing to have more low-level control, memory can be managed manually with -gc none. > Arena allocation is available via a -prealloc flag. Note: currently this mode is only suitable to speed up short lived, single-threaded, batch-like
Read the rest
programs (like compilers). So you have 1) a GC, 2) a GC with escape analysis (WIP), 3) manual memory management, or 4) ...Not sure? Wasn't able to easily find examples of how to use it. There's what appears to be its implementation [1], but since I'm not particularly familiar with V I don't feel particularly comfortable drawing conclusions from a brief glance through it. In any case, none of those stand out as "memory safety without GC" to me. [0]: https://docs.vlang.io/memory-management.html [1]: https://github.com/vlang/v/blob/master/vlib/builtin/prealloc...
In Rue: Higher level than Rust, lower level than Go

Showing the 15 most recent of 234 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.