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

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, 4:00:59 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

23 sources
The problem is that there are so many new languages that it's hard for any of them to gain enough momentum to encourage enough programmers or businesses to learn or even look at them. Not to mention that various top 10 languages are supported by huge companies that may rather snuff out or at least throw shade on up and coming languages that threaten their interests. The development pace of many of the new languages is relatively slow, despite having some great ideas, syntax, or features. Which means years before they have a large enough ecosystem and libraries, to even come near to mounting a challenge to the more established languages. For instance, another new one out there that I like is VLang (https://github.com/vlang/v). Like Red, it needs to find a sweet spot that will propel it to greater usage and recognition. Partly that can
Read the rest
be cross-compiling and cross-platform application development. Also, strong emphasis on mobile development for both Android and iOS would help, but Apple makes their part of it difficult. To stand out, it means having easy to create UIs, their own IDEs (to maximize language features), updated documentation (to help beginners), books about it, etc... Just being on Visual Studio Code, with a hundred other languages, makes it hard to get noticed. Compare Red with established heavyweights like C#, Python, JavaScript, or even contenders like Delphi/Object Pascal. Not so easy to pull attention away from those languages and the thousands of projects using them, unless something very compelling can be shown or proven.
In I can read C++ and Java but I can’t read Smalltalk (2000) [pdf]
Can you elaborate or provide any references for those statements? What in [0] doesn't work as advertised? Also, something I'ld like to know that would otherwise be really dishonest on V devs' part, is their memory management innovative? Oortmerssen, creator of Lobster language, said that in their Discord they mentioned[1] that the memory model was taken from Lobster. [0]: https://github.com/vlang/v#key-features-of-v [1]: https://news.ycombinator.com/item?id=25514198
In Why I'm donating $150/month (10% of my income) to the musl Libc project (2019)
The best bit is this excerpt from the standard library (2019): fn download_file(url, out string) { // println('\nDOWNLOAD FILE $out url=$url') // -L follow redirects // println('curl -L -o "$out" "$url"') os.system2('curl -s -L -o "$out" "$url"') // res := os.system('curl -s -L -o "$out" "$url"') // println(res) } Here's what that file looks like today: https://github.com/vlang/v/blob/master/vlib/net/http/downloa...
In Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
Looks like V author/community is on the track to rewrite the world. Expect operating system stuff next? I'm shocked by how quickly it goes along, though. Gitly is quite usable already, and I appreciate the swiftness. I'd think that Rust community is rewriting the world, but it's happening at much slower pace. Is V's basis strong enough to do this? Seeing the issues like [1] (about the basic memory management stuff) open makes me suspicious. [1] https://github.com/vlang/v/issues/6456
In Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
No reply to the autofree comment? Unsurprising. Since you want it so much, here you go: - "No undefined behavior" -> How does V prevent this? V currently can't even generate well formed C code for all valid V so how do you prevent UB in the generated C? As of now, for any reference x in V, *x and ******x are both accepted by the checker. int32.MAX + 1 is instant UB yet V does nothing to prevent this. What is your plan to prevent UB in the generated C? - Generics -> The example shown in your own docs expresses how "wip" this is (https://github.com/vlang/v/blob/master/doc/docs.md#generics). Why is `T.name` allowed? `T` can be literally anything since there is no constraint on it. You're obviously deferring type checking the function until it's monomorphized which is far more like C++ templates than "generics". How do you plan to deal with t
Read the rest
emplate bloat slowing down compilations? - -usecache -> Another one of the 20% implemented features. This was done to give V a huge boost in compiling simple programs but the implementation is so busted, you yourself disabled it on the benchmarking site. - "go" keyword -> From your docs: "V's model of concurrency is very similar to Go's. To run foo() concurrently in a different thread, just call it with go foo()". At least you've documented it but have completely buried the lede that unlike Go, `go` spawns an OS thread not a green thread. Speaking of green threads, how do you propose to keep the efficiency you claim ("within 3% of C") while still having transparent C interop? Are you going to use segmented stacks to allow 100,000s+ green threads and then run into the same issues Go has calling into C or are you going to larger stacks to make C interop feasible which limits how many green threads you can run before using enormous amounts of memory? - "immutable" references -> As shown on Discord, "immutable" references can easily by laundered into mutable ones by assigning the reference to a mutable variable and then assigning into that. - native backend -> Can handle hello world and programs that use string interpolation. Given that it can't handle the average 100 line V program, you should not be extrapolating the performance of 1,000,000 V programs.*
In Vinix – An effort to write a modern, fast, and interesting operating system in V
The initial alpha (beta?) release of the project was scheduled for public review, but the developer was accepting payments for early access. I won't comment on the state of the release that some people paid for. The devs seem to have made a few enemies. Devs of other small projects, specifically Nim and Zig aren't fans of V to say the least. Nim devs allege that the V project has made defamatory remarks about their project. Zig developer, Andrew Kelly, also had some things to say about V. [0],[1] There have been numerous occasions of the V dev deleting criticism. There are claims that the V project has been buying stars on github. The project makes very bold claims about the feature set while not having actually implemented said features. There is a popular set of blog posts that dives into the issues with claims vs reality [2],[3],[4] My
Read the rest
opinion is that I do find it disingenuous, and borderline scammy, to accept donations and at the same time claim V can do the things it claims. Ultimately, I think the dev is just not great at managing expectations. I highly doubt any of it is malicious intent. Also, somewhere in one of these, Andrew retracts his accusation of fraud, due to the V devs updating the advertised capabilities of the project. [0] https://github.com/vlang/v/issues/292 [1] https://news.ycombinator.com/item?id=20230351 [2] https://christine.website/blog/v-vaporware-2019-06-23 [3] https://christine.website/blog/v-vvork-in-progress-2020-01-0... [4] https://christine.website/blog/vlang-update-2020-06-17
In Vinix – An effort to write a modern, fast, and interesting operating system in V

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