Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

V Language Review (2023)

n-skvortsov-1997.github.io

Post reply on HN
Print view View original

51–60 of 115 posts

Re: V Language Review (2023)

#51

Post by jokethrowaway »

bscphil wrote: post #44
attractivechaos wrote: post #26

Earlier quoted context omitted.

The V devs have promised a lot, have missed a lot but have also achieved a lot. I have written a few short programs in V. IMHO, the V syntax is concise and intuitive and the performance is good. It is lightweight and easy to install and to use. The blog post is probably right that V has many rough edges but I would say the core features in V are well planned. I actually prefer it over some other more popular language…

Yeah, when the article skipped over the first two memory management strategies to point out issues with manual memory management and an "automatic" strategy that is unfinished or broken, it really struck me that it's quite impressive for a single author to have a functional, fast language with a working garbage collector and arena allocator (with some issues) in only a few years. The criticisms in the article, which…

I wouldn't say it's impressive.

I've seen tons of computer science graduates hooking up gc to their languages in uni when they learn about compilers and programming languages

Re: V Language Review (2023)

#52

Post by dequan »

dvc24 wrote: post #47
chrisaycock wrote: post #7

Some highlights: - autofree doesn't work - memory arenas (prealloc) isn't thread safe - compiler produces large binaries - coroutines invoke blocking calls - community behavior is, uh, "unwelcoming"

[flagged]

"outdated article" the commit tested is 3 months old.

This is a standard V community tactic: all negative feedback is "bashing", anything older than a week is "outdated", anything up to date shouldn't have been written and posted on the issue tracker to be ignored instead.

Stop trying to control everyone else's speech and just work on fixing the long list of issues folks already took the time to report.

Re: V Language Review (2023)

#53

Post by richbell »

dvc24 wrote: post #47
chrisaycock wrote: post #7

Some highlights: - autofree doesn't work - memory arenas (prealloc) isn't thread safe - compiler produces large binaries - coroutines invoke blocking calls - community behavior is, uh, "unwelcoming"

[flagged]

> 1. what exactly does not works? This is so unhelpful 2. then report an issue on GitHub 3. exactly for that purpose `-skip-unused` exists, but Rust generates large binaries too 4. please read how coroutines work under hood, it will process events while waiting for syscall. 5. we welcome folks that aren't bashing on V using outdated "articles aganist V"

The GP was merely summarizing the article. They are not making any claims themselves.

Re: V Language Review (2023)

#54

Post by bigjads »

Cavallium wrote: post #39
12_throw_away wrote: post #13

I know it's a meaningless metric, but I still find myself wondering how, exactly, vlang got to 35K stars on github, very much in the same order of magnitude as, say, cpython with 58K.

A lot of vlang-related statistics are very suspicious, probably some of the metrics are boosted by a click farm or something similar. For example, 99% of the global google searches about "vlang" are from Beijing. https://trends.google.com/trends/explore?date=today%205-y&q=...

[dead]

Re: V Language Review (2023)

#55

Post by odiroot »

lkey wrote: post #9

V's claims have always been dubious on their face. It promised the programming language equivalent of magic with no overhead. I'm glad that someone took the time to print receipts. The author clearly wants a reckoning, but he's unlikely to receive satisfaction. The people that still use or evangelize V are locked in, the contradictions will only make their belief stronger. Alex is a bullshitter, and arguing with some…

Whoa there. It's just a programming language. No need to spill vitriol over that.

I have no skin in the game. Got into V very recently, because it appeals to me at face value.

And in some ways better than other "better C" languages of today.

For me it's just good enough. The syntax is sane, the compiler doesn't want to maniacally ruin my day, the standard library is already quite rich, and finally wrapping C code is a breeze.

Re: V Language Review (2023)

#56

Post by dvc24 »

dequan wrote: post #52
dvc24 wrote: post #47

Earlier quoted context omitted.

[flagged]

"outdated article" the commit tested is 3 months old. This is a standard V community tactic: all negative feedback is "bashing", anything older than a week is "outdated", anything up to date shouldn't have been written and posted on the issue tracker to be ignored instead. Stop trying to control everyone else's speech and just work on fixing the long list of issues folks already took the time to report.

[flagged]

Re: V Language Review (2023)

#57

Post by ptx »

dvc24 wrote: post #47
chrisaycock wrote: post #7

Some highlights: - autofree doesn't work - memory arenas (prealloc) isn't thread safe - compiler produces large binaries - coroutines invoke blocking calls - community behavior is, uh, "unwelcoming"

[flagged]

> it will process events while waiting for syscall

How does that work?

According to the source code quoted in the article, there is a separate "coroutine-safe version of time.sleep", which seems like it shouldn't be needed if V has a general solution for unblocking blocking syscalls.

Re: V Language Review (2023)

#58

Post by saghm »

dvc24 wrote: post #56
dequan wrote: post #52

Earlier quoted context omitted.

"outdated article" the commit tested is 3 months old. This is a standard V community tactic: all negative feedback is "bashing", anything older than a week is "outdated", anything up to date shouldn't have been written and posted on the issue tracker to be ignored instead. Stop trying to control everyone else's speech and just work on fixing the long list of issues folks already took the time to report.

[flagged]

From the article:

> Everything described here is correct for the b66447cf11318d5499bd2d797b97b0b3d98c3063 commit. This is a summary of my experience with the language over 6 months + information that I found on Discord while I was writing this article.

From https://github.com/vlang/v/commit/b66447cf11318d5499bd2d797b...:

> felipensp committed Nov 20, 2023

Can you clarify how you're calculating 2 years? Today is February 24, 2024, so the parent comment saying 3 months seems pretty accurate.

Post reply on HN