Comment by smcl

3 years ago

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.

    • > Remember, the competition between various younger languages has become a bit fierce and dirty.

      As someone who works full time on one relatively young language, has created a couple more, and knows people working on many others, this is 100% wrong in my personal experience.

      Most young language teams work very hard to communicate accurately and to set appropriate expectations because they know that user trust is a hard requirement for adoption.

      V is the outlier here.

    • 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.

      46 replies →

    • You say it "comes off as part of an effort ... to mount another attack". Maybe it does to you, but I don't know why. I've never heard of this "fierce and dirty" competition between young languages. I've never seen anything even a bit like that. I've only seen fierce fighting between advocates of large well-established languages.

      Xe's post struck me as accurate at the time, and having that context to compare with makes V look a little better now, because it at least establishes that progress is being made towards those claims.

      I don't know where you're getting the idea that this is based on some kind of sinister "personal agenda" other than "this thing sounds interesting, I investigated it, it seems less cool now", which is a pretty defensible position for someone to reach.

      1 reply →

    • You are not doing yourself any favor by harassing people, if anything it makes you look like a fan-boy. Do yourself a favor, read the article then present a constructive criticism, if any.

    • > I see though that V supports closures. What are the rules for shadowing variables in closures?

          fn main() {
              x := 1
              y := fn (x int) {
                  println(x)
              }
              y(x)
              y(2)
          }
      
      

      I am not sure I follow - the `x` parameter for the anonymous function, is entirely different, than the `x` in the main function. For me, there is no way for it to be confused with the `x` inside main.

      ... y := fn [x] (x int) { println(x) } ...

      > Well, that seems like it should be disallowed. It makes sense that x can be captured but to then shadow the argument with the same name without error or warning doesn’t seem inline with the rest of V’s behavior.

      I see what you mean now, yes, that does seem like another good issue candidate. Filed in https://news.ycombinator.com/item?id=31794565

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

  • Ah I'm sorry, I hadn't checked the website in a little while. I now see there's a redirect and that there is a different name in use.

  • 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 the Church of the Latter-day Dude. This allows me to officiate religious ceremonies in at least the United States." - https://dudeism.com

      6 replies →

    • Who gives. Just use 'they' or 'them', or whatever. It is a universal catch all, gender neutral, i18n inclusivity conformant, ISO 69420 compliant, race neutral, etc.

      At this point, all of it is basically designed to further confuse and only create a very monthly chaotic outcome for everyone.

      2 replies →

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 mind that these attacks are on a young language that isn't 1.0 yet, so even with this we are talking about a moving target. The language is still evolving.

  • 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.

      3 replies →

  • Your keep calling people "competitors." I don't think you're using the word right. Perhaps "detractors" is what you mean, but "reviewers" is more neutral. Xe and mawfig don't appear to be offering their own languages to compete with V. At one point, Andy Kelly (a "competitor") criticized the author's behavior, but he's also gone silent on the topic of V because of the vitriol he encountered.

    One reason that people highlight older criticism is because it's useful to examine past behavior, past promises, and contrast them to current behavior and current promises. If V is going to improve its reputation, it's going to do it by (a) making good on the promises it can, (b) coming clean on the promises it can't, and (c) offer a clear win for some distinguishing featureset. Badgering people to shut up about the past isn't on that list.

    • > Andy Kelly (a "competitor") criticized the author's behavior, but he's also gone silent on the topic of V because of the vitriol he encountered

      AFAIK your stated reason for the silence is not accurate. Andy’s criticisms were always based on V making claims that no one could evaluate because it was closed source/unreleased (and then used those claims to solicit money from people). Once V was made open source, those criticisms no longer applied, as things like TFA could be written.

      2 replies →

  • Yeah you can't buy trust. Once it's done is done.

    I'm not touching a language developed by folks who don't see a problem in scamming users, sorry.

    • Financial supporter of V here. I don't feel scammed or misled at all. So keep speaking for yourself with the imaginary money you did not donate nor lose.

  • > Why in the world do competitors of this programming language insist on dragging out evaluations from 3 years ago...

    This question is answered in the comment you just replied to:

    > 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.

  • Mostly because the author completely scammed the shit out of people by promising a ton of things to garner patreon support before open sourcing what was essentially a hobby project at the time. I haven't followed it very closely, but last I heard about it was not delivering on the "autofree" feature.

    I dont really care about the language. I've tried it a couple times and it's nothing special (to me) so I moved on, but I definitely understand where the hate comes from. The author essentially lied for at least months about his project to get financial support.

    Quick edit: to actually add to the discussion, I think the weirdest thing about V is the odd support it does get. Most projects, especially compilers, with as much controversy as V would never get any support. I'm very curious what its proponents are using it for and why they choose V over pretty much any other language.

  • > Why are so many people frothing at the chance to disparage this language and it's author?

    It's because of all the lying. The author keeps claiming that their language has features that it definitely does not have.

    Why do so many people consider "I checked several notable claims, and most of them are false" to be some kind of hateful disparaging attack?

    • 100% right. It's sick. As a donor and supporter of this VALIANT AND VALID effort, I applaud the V community. It's full of sincere passion, love and is putting forth a great effort to realize something useful and needed in this sector.

      5 replies →