Live data from Hacker News

V Language Review

mawfig.github.io

21–30 of 336 posts

Re: V Language Review

#21
post #13
post #5

Earlier quoted context omitted.

Xe is phasing out that name in favor of "Xe". Xer domain name change was a part of that shift.

Is 'Xe' the name or the preferred pronoun of the person in question? Is this like Latinx but race neutral? Gender identity accommodations seem to get more complex and confusing by the month...

Why not both?

Re: V Language Review

#22

At this point, why do people even spend time on debunking the marketing claims of this language at all? It's been done to death, whoever was going to be convinced the V developer is a charlatan has already been convinced. For better or for worse.

I think everyone wants a "Rust but better" language to exist, and that very well might be V in 5 years, but Rust wasn't advertising features as 'completed' years before they were implemented/stable and neither should V. Continuing to point out the design issues will either get the marketing claims removed (just throw up a roadmap!) or articles like this will be used to show V's progress in a distant future.

Everyone wants that? Not even everyone wants something like Rust. But I doubt that everyone who programs in Rust (and like it somewhat) want Rust-but-better (when that entails learning a completely different language, at least).

Re: V Language Review

#23

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.

> the design of the language itself (leaving aside the implementation) is genuinely interesting […]

> Disclaimer: I’ve never actually used it.

I can make a hypotethical language as well (I do it all the time), but I wouldn’t make a website about it and give it a name.

Re: V Language Review

#24
post #13

Earlier quoted context omitted.

Is 'Xe' the name or the preferred pronoun of the person in question? Is this like Latinx but race neutral? Gender identity accommodations seem to get more complex and confusing by the month...

Name, at least that's my interpretation from looking at her Contact Me page: > Copyright 2012-2022 Xe Iaso (Christine Dodrill). https://xeiaso.net/contact [correction] on their GitHub page I see: Please call me (order of preference): Xe/xer, They/them or She/her please. [edit] obscure to have your pronoun also be your name (or maybe your title?). Or maybe it is all just satire, given: "I am an ordained minister with…

To be honest having a person's name be the same as their nominative case pronoun is kind of cool from a whole different perspective than you normally get to see. By doing this experiment I get to see how bad of an idea it is to do that. So far the xe/xer pronouns don't seem to stick as well, but it looks cool so I'm gonna keep up the experiment.

I'm also quite seriously an ordained minister.

Re: V Language Review

#25
post #24

Earlier quoted context omitted.

Name, at least that's my interpretation from looking at her Contact Me page: > Copyright 2012-2022 Xe Iaso (Christine Dodrill). https://xeiaso.net/contact [correction] on their GitHub page I see: Please call me (order of preference): Xe/xer, They/them or She/her please. [edit] obscure to have your pronoun also be your name (or maybe your title?). Or maybe it is all just satire, given: "I am an ordained minister with…

To be honest having a person's name be the same as their nominative case pronoun is kind of cool from a whole different perspective than you normally get to see. By doing this experiment I get to see how bad of an idea it is to do that. So far the xe/xer pronouns don't seem to stick as well, but it looks cool so I'm gonna keep up the experiment. I'm also quite seriously an ordained minister.

[deleted]

Re: V Language Review

#26
post #16

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.

I'm sorry if you feel this is a dunk on V. Having seen quite a bit of discussion both on hacker news and other places saying that V has improved significantly since Xe's articles a few years ago, I thought it would be worth while to attempt a modern evaluation of the language based on where it is today. Throughout, I tried to ground my review by basing it on the claims the developers themselves make. Would you mind e…

Sorry, I didn’t mean to suggest that this article itself was a dunk. I was commenting on the discussion I see elsewhere on the language (including elsewhere in this comments section). The article itself is a good summary of the problems with V — mostly with its implementation which does appear shoddy.

V’s design address many things I feel are lacking whenever I use Go: nil safety, sum types, option/result types, mandatory error checking. I think V is best understood in the context of being Go++.

Having looked a bit deeper though, the immutability and generics stuff does feel a bit bolted on, so I do see your point.

Re: V Language Review

#28

At this point, why do people even spend time on debunking the marketing claims of this language at all? It's been done to death, whoever was going to be convinced the V developer is a charlatan has already been convinced. For better or for worse.

For what it's worth, there has been some progress on the language and the author has responded to past criticism. I've been following developments of the language for a few years now, and I'd love it if all the claims came to fruition. Since it's a work in progress, past criticism doesn't necessarily apply -- leaving me to wonder "is it not bullshit yet?" Since the author has a habit of overpromising and even declaring things finished before even starting on them, and newcomers might not know what to think, his claims warrant regular scrutiny. It appears that V is still for vapor.

Re: V Language Review

#30
post #18
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.

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.

I'm always interested in new languages and loved your write-up & evaluation of V.

I really don't get the purpose of someone exaggerating the capabilities of their language, to the point of outright lies.

Post reply on HN