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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 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

21 sources
stefanos82·Oct 3, 2023
Goroutines was the selling point for me until they decided to introduce telemetry in their toolchain; that was what forced me to stop using Golang as a whole. About GC, I would say: if you implement C++'s RAII mechanism to replace garbage collection, then I believe this project will have a bright future. My final question is the following: how `pcz` compares to V language, from a syntax's perspective [1]? [1] https://github.com/vlang/v
In Show HN: A new stdlib for Golang focusing on platform native support
Tozen·Aug 30, 2023
V has the right to exist, have its supporters, and do things its own way. The creator and developers of V, from what I have seen, have responded well to actual constructive criticism. Their language has discussions opened at their GitHub, unlike those for various other languages. They even have a thread for what people don't like and want improved about the language[1], again, something many other languages don't have. A lot of what was going on initially, was coming from obvious competitors and evangelists, to include being uncivil, inflammatory, and directly insulting. The initial "criticism" was not so much that, but false accusations of the language being a scam, vaporware, fraud, or didn't really exist. To include attacks and jealousy over donations, rising popularity, and having supporters. This was not any kind of "valid" cri
Read the rest
ticism, that the creator or contributors of the language could reason about with instigators. The "criticism" never died down, but rather V was open-sourced and established itself on GitHub. The initial series of false accusations could not stand nor could the support it was getting be stopped. So, the rhetoric and targets shifted to whatever could be found to go after on the newly released alpha version of the language and its new website. In that new mix of what was being thrown at it, there were indeed some very valid criticisms, as can be found with any new language and many sites. Constructive and valid criticism, is not the same as insults, trolling, misinformation, rivalry, or false accusations. There is clearly a difference. It's disingenuous to pretend something from one group is the same as the other, or that the intent behind what is being done is not different. [1] https://github.com/vlang/v/discussions/7610
In The V Programming Language 0.4
Tozen·Aug 29, 2023
In both the review itself and in V's documentation, from which the example came, it states that autofree is still WIP. It's arguably disingenuous to pretend otherwise or present unintended usage. The normal "day-to-day" situation would be to have the GC on or as fallback, and to do otherwise (like -gc none or -prealloc), one should know what they are doing or be prepared to deal with such issues. Those parts of the review, considered relevant in normal usage were resolved: https://github.com/vlang/v/issues/14803 https://github.com/vlang/v/issues/14787 https://github.com/vlang/v/issues/14786 But even beyond that, the intent of the so-called review was arguably malevolent. It was not done in good faith, to be helpful to the developers or community, but done to spur on drama (thus adding the vaporware link and spamming it) and knowingly lo
Read the rest
oking for ways to bash an alpha version of the language.
In The V Programming Language 0.4
delian66·Aug 28, 2023
It is very easy to verify. Just have a working C compiler + git + make: git clone https://github.com/vlang/v cd v make ./v your_program.v On a modern machine with good network, it will take you under a minute, to have your own copy of latest V, and less than 200MB, including the .git/ folders. You can also download .zip releases from https://github.com/vlang/v/releases , without needing git. The .zips there are <15MB, and contain a prebuilt V executable, so you do not even need make to use it.
In The V Programming Language 0.4
Tozen·Jul 14, 2023
This "critical review", appears more like continuous old spam often used by detractors or to troll. It has no perceived value other than that, because it's a "review" (hit piece) of an alpha version of the language. It's 2023, and V is also in beta (0.4). Furthermore: 1) The creator of it used a disposable GitHub account, launched the review/attack for the drama, then disappeared. 2) The only thing they ever published on their blog, was the hit job on V. No other reviews ever made. 3) Anything, which had any kind of substance, is already fixed[1]. 4) A search of mawfig.github, shows how it is spammed on HN, and usually used for smearing. [1]: https://github.com/vlang/v/issues/14803 [1]: https://github.com/vlang/v/issues/14787 [1]: https://github.com/vlang/v/issues/14786
In Vale's first prototype for immutable region borrowing
Tozen·Jun 26, 2023
Besides the attempted slap on V coming from "out of left field", in regards to what the above commenter was talking about, V doesn't leak memory like that. V, since becoming beta (last year), uses an optional GC and does flexible memory management[1]. Giving users choices, somewhat like D and Nim do. It provides 4 choices: default optional GC (that can be turned off), autofree (either alone or with GC), arena allocation (-prealloc), or manual memory management (-gc none). This flexibility has already been proven, like with their Vinix OS project[2]. Lastly, for developing languages going through alpha and beta phases, think that people should acknowledge how the process works and update their information. Rust or Nim, for example, aren't the same language they were 5 years ago or when still in beta. [1]: https://github.com/vlang/v/blo
Read the rest
b/master/doc/docs.md#memory-ma... (4 ways to manage memory in V) [2]: https://github.com/vlang/vinix
In Ask HN: Why did Nim not catch on like Rust did?

Showing the 15 most recent of 21 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.