Live data from Hacker News

V Language Review

mawfig.github.io

41–50 of 336 posts

Re: V Language Review

#41
post #12

My recommendation is that if you like the look of V, you should consider Zig or Odin as well. Personally, Zig seems like the most promising C-but-modern language due to the interesting compile-time programming features and impressive investment in toolchain infrastructure.

Zig is arguably not something similar enough that it would be attractive. Odin and Vlang are kind of offshoots of Golang, so would be more similar and attractive to those users. If a person is a Golang user, they would be more likely to see the advantages and possible improvements of Odin and Vlang.

Re: V Language Review

#42
post #38
post #18

Earlier quoted context omitted.

Thanks for linking Xe's blog here! It's a few years old and I've seen a lot of comments on HN that suggest V has improved significantly since 2019 so I thought it might be worth looking into for myself and writing down a review of what I found.

Quoted post unavailable.

Every evaluation in my blog is fully reproducible from the version of V I linked to and I've included all the source code used as well. My post stands on it's own.

Instead of insinuating I'm some kind of competitor or have a personal agenda, I would encourage you to respond to the actual points raised in my post.

Re: V Language Review

#43
post #36
post #3

Christine Dodrill's early assessment of the language might be of interest here: https://xeiaso.net/blog/v-vaporware-2019-06-23 She doesn't pull any punches, but I think she was quite prescient in capturing the vibe of the project.

Why in the world do competitors of this programming language insist on dragging out evaluations from 3 years ago, which state that V is vaporware and before the language was even released? This is 2022, not 2019, and we are talking a hundred releases later ( https://github.com/vlang/v/releases ). At least stick to the current evaluation (or attack), which is more relevant, and make points from there. But, keep in min…

I don't have a horse in this race, but when a language makes present-tense claims about its features I assume that they're already functioning features.

People are poking holes in V because its claims are unfounded, not because they've decided they're in competition with the language. A simple "work in progress" sign on the features in question would draw a lot of fire away from the language and its creator.

Re: V Language Review

#44
post #37
post #12

My recommendation is that if you like the look of V, you should consider Zig or Odin as well. Personally, Zig seems like the most promising C-but-modern language due to the interesting compile-time programming features and impressive investment in toolchain infrastructure.

An article like the V one on Zig checking the claims would be awesome, wouldnt it.?

No post body was provided.

Re: V Language Review

#45

It would be very nice if you could do the same thing for Nim.

Nim and Zig are both pretty interesting to me as up-and-coming languages so I do have them on a short list of things to try. This post took about a month of effort in my spare time to write so I don't think I will get to those anytime soon.

Re: V Language Review

#46
post #36

Earlier quoted context omitted.

Why in the world do competitors of this programming language insist on dragging out evaluations from 3 years ago, which state that V is vaporware and before the language was even released? This is 2022, not 2019, and we are talking a hundred releases later ( https://github.com/vlang/v/releases ). At least stick to the current evaluation (or attack), which is more relevant, and make points from there. But, keep in min…

I don't have a horse in this race, but when a language makes present-tense claims about its features I assume that they're already functioning features. People are poking holes in V because its claims are unfounded, not because they've decided they're in competition with the language. A simple "work in progress" sign on the features in question would draw a lot of fire away from the language and its creator.

Indeed! I even mentioned this in my "Rules of engagement" section:

> Features indicated to be incomplete/work in progress/unimplemented will be mentioned as such.

Indicating on the vlang.io homepage how much of the language has yet to be realized would go a long way in my opinion.

Re: V Language Review

#47

People like to dunk on V because of its author and community, but I will say that the design of the language itself (leaving aside the implementation) is genuinely interesting. To me, it feels like what Go should have been. And I like Go. So obviously I have a bit of a soft spot for V. Disclaimer: I’ve never actually used it.

No post body was provided.

Re: V Language Review

#48
post #3

Christine Dodrill's early assessment of the language might be of interest here: https://xeiaso.net/blog/v-vaporware-2019-06-23 She doesn't pull any punches, but I think she was quite prescient in capturing the vibe of the project.

Nah that article is old as hell - time for new information. Things change.

I also despise how many people want to shit on this new language before it even takes off. Why are so many people frothing at the chance to disparage this language and it's author? Never seen something like this.

Re: V Language Review

#49
post #3

Christine Dodrill's early assessment of the language might be of interest here: https://xeiaso.net/blog/v-vaporware-2019-06-23 She doesn't pull any punches, but I think she was quite prescient in capturing the vibe of the project.

Nah that article is old as hell - time for new information. Things change. I also despise how many people want to shit on this new language before it even takes off. Why are so many people frothing at the chance to disparage this language and it's author? Never seen something like this.

It's been around for a few years now.

Re: V Language Review

#50
post #42
post #38

Earlier quoted context omitted.

Quoted post unavailable.

Every evaluation in my blog is fully reproducible from the version of V I linked to and I've included all the source code used as well. My post stands on it's own. Instead of insinuating I'm some kind of competitor or have a personal agenda, I would encourage you to respond to the actual points raised in my post.

That's interesting or telling, because if you read what I posted carefully, I was not insinuating anything about your evaluation. Instead, the point was being made that you probably don't want to be associated with an old evaluation from 3 years ago, which is falsely accusing V of being vaporware, and where the author and the developer of V clearly have beefs with each other.
Post reply on HN