News for hackers. Stuff that matters.
Re:V 0.3 by ketzu on Friday July 01, 2022 @09:48AM (#31946318)
How up-to-date is this [1] review from earlier this year for 0.3? Honestly, the review read nicely but left quite a questionable impression of V.

[1] https://mawfig.github.io/2022/06/18/v-lang-in-2022.html

Re:V 0.3 by xiphias2 on Friday July 01, 2022 @12:08PM (#31948511)
As Rust proved it fast, safe and simple don't go together (fast and safe requires borrow checking on the data types, which is complex).
Re:V 0.3 by ken0x0a on Saturday July 02, 2022 @01:27AM (#31956519)
Thank you for digging! I really appreciate your attention. There are lots of bug fix in 1 year, and will be better time by time. I started to use Vlang 1 year ago, and I created lots of ISSUES on GitHub, and most of them are already fixed.

I like Vlang (also like Rust and ...) so, I'm happy for your attention & deep insight. I hope you to dig and share again sometime.

Re:V 0.3 by Tozen on Friday July 01, 2022 @12:47PM (#31949171)
That "review" was a thinly disguised hit piece against the V language.

1) The "review" is now significantly wrong and already outdated.

Doesn't mention it is reviewing an Alpha or even the version.

Anything of substance in the review was mostly minor and has already been fixed:

https://github.com/vlang/v/issues/14803 https://github.com/vlang/v/issues/14787 https://github.com/vlang/v/issues/14786

2) The author of the "review" used a throwaway account for the apparent purposes of recommending to not use V.

The author of the "review" can run away and hide, where the creators and developers of V are accountable to the public and supporters.

This includes that the author of the review never has to update or make corrections to his hit piece, while still spreading links to it all over the internet.

3) The "review" is used as a linked reference document for further attacks by competitors and detractors. And as has already happened on various other internet sites, including here.

4) If the author of the "review" was really eager to use and fix the V language, he could have brought those issues (he has a GitHub account) to the V GitHub (https://github.com/vlang/v/issues).

Who is going to fix any issues that the author believes is a problem?

It is going to be the V developers. So if the author of the review wanted those things that he believes are a problem fixed, that's who he has to bring them to.

5) The author of the "review" starts it by linking to a number of very contentious posts from competitors and detractors of V, to include those that smear the author and language.

This turned the "review", right off the bat, into setting off drama. A smear campaign on the V language will never get any of the issues fixed on its own, just only invite more drama, smearing, and attacks. Which looks like the original intent.

6) The author of the "review" has shown no interest in working with V developers, and that's prior to publishing the review and spreading links to it.

No intent has been shown to modify his review for correctness, fairness, or language version.

7) The author's review doesn't provided the necessary context and is highly opinionated.

Without feedback or the opinions of the V developers, this is a one-sided negative review full of many debatable points, that does little to help readers outside of trying to produce a negative impression and smear the language.

If the review author is not interested in working with V developers, and rather produce and disseminate drama or facilitate smearing, then that's a reflection of their real intent.

Re:V 0.3 by mihaigalos on Saturday July 02, 2022 @02:35AM (#31956778)
V minor contributor here. My 2 cents: I do get the feeling claims were founded/solid but am not an expert on the subject.

Article's author citation related to V's version which got tested:

> I’ll be using the current version of V built from git which is 50ab2cfd1ae02d4f4280f38c60b8dbd17f7599f6.

To be perfectly fair to the language, for me, it was love at first sight. Syntax is beautiful.

If ever V reaches maturity (0 segfaults + addresses concerns raised in Reddit, HN and other sources such as ^), I would definitely prefer it to Golang, potentially even Rust.

Not to mention its future is secured if C projects are ported to V.

[dead]
Re:V 0.3 by ketzu on Friday July 01, 2022 @11:29AM (#31947787)
> For what it's worth, every GitHub project has a mechanism for submitting issues. It's better Open Source spirit to utilize these tools as intended.

Are project issues the right place for reviews of claims? Negative point sure would be nice to have as github issues (and checking for some easily searchables: they seem to exist [1,2]) but many of the points in the review don't suite issues well. I don't think "you can open tickets" would be a useful response to "wat" [3] either.

Alternatively your suggestion was for me to wade through the issues to figure out if the critizism holds, which I find is not a helpful suggestion either, as many of them are not particularly well searchable. Also, I assumed, as the review got a bit of attention and the creator was in the thread, it would lead to an interesting response a-la "we are aware, fixing it, many fixed already, here is our roadmap" with possible discussion. I am a bit saddened that it turned out to be much more hostile and negative.

[1] https://github.com/vlang/v/issues/11059 (won't fix undefined behavior in generated code)

[2] https://github.com/vlang/v/issues/7519 (fixed missing openssl header)

[3] https://www.destroyallsoftware.com/talks/wat

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:36AM (#31947912)
All the issues in the post have already been fixed.

What's wrong with the division by zero issue? It works just like in Go?

What about the openssl issue? The user didn't install the library on Windows, as was documented.

By the way, we're going to embed openssl to avoid this problem.

Re:V 0.3 by anderskaseorg on Friday July 01, 2022 @01:36PM (#31949888)
The post’s example of undefined behavior via signed integer overflow still holds in current V master.

    $ cat test.v
    fn main() {
        x := i32(2147483647) + 1
        println(x)
    }

    $ ./v version
    V 0.3.0 f0cee25

    $ ./v -o test.c test.v

    $ cc -fsanitize=undefined -Lthirdparty/tcc/lib -Ithirdparty/libgc/include test.c -lgc
    test.c: In function 'main__main':
    test.c:12073:37: warning: integer overflow in expression of type 'int' results in '-2147483648' [-Woverflow]
    12073 |         int x = ((i32)(2147483647)) + 1;
          |                                     ^

    $ ./a.out
    test.c:7577:33: runtime error: signed integer overflow: -2147483648 - 2147483600 cannot be represented in type 'int'
    -2147483648
That V code has compiled to this C code, which is indeed undefined behavior.

    VV_LOCAL_SYMBOL void main__main(void) {
            int x = ((i32)(2147483647)) + 1;
            println(int_str(x));
    }
(Since you asked for people to file issues about these problems, I’ve opened https://github.com/vlang/v/issues/14912.)

Additionally, V’s own documentation calls out a separate instance of undefined behavior (https://github.com/vlang/v/blob/master/doc/docs.md#closures):

“If you need the value to be modified outside the function, use a reference. Warning: you need to make sure the reference is always valid, otherwise this can result in undefined behavior.”

So it shouldn’t be surprising that people call out the “No undefined behavior” claim on the home page as dubious.

Re:V 0.3 by tene on Friday July 01, 2022 @02:05PM (#31950325)
If making sure references are valid is left up to the user, it's ridiculous to call this language safe.
Re:V 0.3 by enragedcacti on Friday July 01, 2022 @11:54AM (#31948235)
> What's wrong with the division by zero issue? It works just like in Go?

As I understand it, V's emitted C code (in release mode) does not handle the possibility of a divide by zero. As such, according to the C spec, you've now entered territory where literally anything could happen depending on how the compiler or platform is implemented.

Go, alternatively, detects a divide by zero and panics (like V does in debug mode) which will consistently occur regardless of compiler or platform because it is defined behavior.

In the case of the user in the issue, he got a SIGILL but other OSes, compiler versions, architectures, etc. could result in some other outcome entirely.

I'm not familiar with where V is ported to, do all the supported platforms result in the same behavior?

Re:V 0.3 by ketzu on Friday July 01, 2022 @11:49AM (#31948144)
I disaggree [1] with your claim that all issues have been fixed, but maybe I misunderstand what "No nulls" means and other things.

> What's wrong with the division by zero issue?

It is undefined behavior in C. [2] section 6.5.5 the 5th paragraph. V generates code that is undefined behavior in the intermediate language, some people might consider that "undefined behavior".

> It works just like in Go?

I read this argument in the issue too. How is that remotely relevant?

> What about the openssl issue?

I linked issues of things that were mentioned in the initial review. Not issues that were problematic, remarkable or anything else.

[1] https://news.ycombinator.com/item?id=31947510

[2] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:53AM (#31948211)
> I read this argument in the issue too. How is that remotely relevant?

How is that remotely irrelevant?

What kind of behavior do you expect?

Re:V 0.3 by sjustinas on Friday July 01, 2022 @02:49PM (#31950975)
Not the parent poster, but there seems to be some misunderstanding. The GitHub issue creator explained that they're getting two different behaviors depending on C compile flags. That's already not "the same behavior as Go" AFAIK.

> What kind of behavior do you expect?

Defined behavior, I assume. If V uses C as an intermediate, and the generated C code invokes undefined behavior, then V can not guarantee "no UB" in that case at all. It is completely up to the C compiler what happens. Even if the compiled app behaves "properly, like Go" with the specific C compiler, with the specific flags, on that specific machine, does not mean this behavior is defined and consistent.

Re:V 0.3 by magicalhippo on Friday July 01, 2022 @08:24PM (#31954758)
> What's wrong with the division by zero issue? It works just like in Go?

In fact it does not work like in Go, and that's the entire point. In Go, division by zero is well-defined[1]:

If the divisor is zero at run time, a run-time panic occurs.

As pointed out by others[2], divide by zero in C is in contrast explicitly undefined behavior. So the statement "it works just like in Go" is false.

It may do the same thing as Go on your machine, with the C compiler you used on the day that is today. But the fact remains the generated C code produces undefined behavior, and thus this happy accident of yours is entirely irrelevant.

What makes this extra egregious is the fact that "no undefined behavior" is listed as a key feature, and that the relevant issue[3] was closed as wont-fix.

Now, there are several ways to properly fix this.

One is to keep the current behavior and change the wording of the key feature listing to remove "no undefined behavior" or modify it to something like "no additional undefined behavior compared to C".

Another way would be to clearly define the behavior of divide by zero, similar to how Go did. The V transpiler then has to generate extra C code that ensures this well-defined behavior, for example by inserting a check for zero. This should be in place before 1.0 release at least.

[1]: https://go.dev/ref/spec#Integer_operators

[2]: https://news.ycombinator.com/item?id=31948144

[3]: https://github.com/vlang/v/issues/11059

Re:V 0.3 by dang on Friday July 01, 2022 @02:17PM (#31950511)
Please don't comment about the voting on comments. It never does any good, and it makes boring reading.

https://news.ycombinator.com/newsguidelines.html

Re:V 0.3 by gompertz on Friday July 01, 2022 @06:20PM (#31953750)
Sure, will do. However I can't help but feel a large majority of the posting on anything V is mostly flame war and personal attacks which is far more egregious than commenting on votes, and against the guidelines you linked.
Re:V 0.3 by dang on Friday July 01, 2022 @06:58PM (#31954104)
Yes, the topic is lamentably flame-prone. I've been trying to persuade some of the key commenters not to handle it that way.

HN moderation is necessarily inconsistent because we can only read a small sample of what gets posted to the site. If you see a post that ought to have been moderated but hasn't been, the likeliest explanation is that we didn't see it. You can help by flagging it or emailing us at [email protected].

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

Re:V 0.3 by Tozen on Friday July 01, 2022 @04:02PM (#31952032)
Exactly. Such bad actors, for anybody that they think is supportive of V, will:

1) Downvote (which is very obvious in many V related threads or even other websites). Even clearly reasonable or minor posts.

2) Flag posts out of spite. Which can leave others scratching their head for what the cause of the flagging could be.

3) Troll (to include YEARS of troll posts by the same accounts and attack blog or post linking).

4) Gaslight (this bad behavior that we constantly do is all in your imagination).

Over time, the behavior of such bad players becomes even more obvious, that it leaves little doubt about what they are doing.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:23AM (#31946814)
You're absolutely right!

Reporting these issues wouldn't take a month, like the article, and they'd be fixed right away, as they were after the article was published.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @09:55AM (#31946432)
All of the issues there were fixed several days ago, so it's no longer relevant.

Since it was another anonymous attack, it's not going to be updated and will stay like this for years.

And the issues discussed are questionable at best. Half the article is about a type checker bug, which was a 3 line fix.

Then false claims like being able to modify array.len.

Re:V 0.3 by raphlinus on Friday July 01, 2022 @10:57AM (#31947248)
The claims made in that blog post are easily verifiable. Your claim that all issues have been fixed was hard to believe, so I checked myself. The first two have indeed been fixed (these involve printing "nil" for a null pointer rather than crashing), but the third (undefined behavior on integer overflow) still reproduces. I didn't go through the rest of them, but expect a similar pattern.

I encourage people following the progress of the V language to look at actual facts rather than trying to evaluate claims based on the language of those claims. One of the reasons why V is so divisive is that a lot of untrue claims are being made (unusually so for a programming language), and people don't respond well to that being called out.

Re:V 0.3 by the_duke on Friday July 01, 2022 @01:13PM (#31949539)
Honestly... At this point, and after trying to engage constructively in other comments, I don't think the claims are actually intentionally false.

They may just come from a fundamental lack of knowledge about low level development.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:40AM (#31947977)
Integer overflow works as expected, like in C.
Re:V 0.3 by raphlinus on Friday July 01, 2022 @11:57AM (#31948304)
Thank you for posting such a beautiful example of a false claim about your language.

The front page of vlang.io has prominently featured under "Safety" the line "No undefined behavior". Saying that C-like undefined behavior[1] is "expected" directly contradicts that. I'll also point out that Nim, another language which compiles to C as a target, addresses this correctly.

[1]: https://raphlinus.github.io/programming/rust/2018/08/17/unde...

Re:V 0.3 by thedufer on Friday July 01, 2022 @11:59AM (#31948341)
Your website says on the homepage "No undefined behavior". Integer overflow in C is explicitly undefined behavior. What does the phrase "undefined behavior" mean to you? Because it's clearly something very different from what it means to the rest of the industry.
Re:V 0.3 by Octoth0rpe on Friday July 01, 2022 @12:05PM (#31948458)
I think there's a communication issue on your end here.

If someone raises an issue re: integer overflows, and you don't change the behavior, it's not 'fixed'. It may be 'addressed' or 'resolved' by responding with with something like "it's working as designed" or "if it's good enough for C, it's good enough for me!", but it's _not_ fixed. I don't think you should claim:

> All of the issues there were fixed several days ago

I really do like V FWIW.

Re:V 0.3 by ben-schaaf on Friday July 01, 2022 @11:56AM (#31948273)
Signed integer overflow is undefined behavior in C. Is it also therefore undefined behavior in V?
Re:V 0.3 by hunterb123 on Friday July 01, 2022 @11:06AM (#31947393)
> The first two have indeed been fixed

> I didn't go through the rest of them, but expect a similar pattern.

You verified two issues were fixed, ran into one issue and then you expect a similar pattern of what exactly...?

Why didn't your comment go like this:

"Hey I went through to verify the these issues were fixed and I'm getting an undefined behaviour on integer overflow, here is how I tested (show code), are you able to reproduce this?"

That would be much less divisive and result in a proper discussion.

I think you'll find if you try to "call" people out instead of asking questions you'll be met with the same tone you gave them.

-- EDIT - replying to @paskozdilar below --

It could be that GP tested incorrectly? Since things are getting so serious shouldn't we see the code GP used to test before mob shaming?

You seem to be jumping to the conclusion the issue is not fixed. I don't think hurling "narcissism" is needed at all here.

Re:V 0.3 by paskozdilar on Friday July 01, 2022 @11:13AM (#31947511)
Similar pattern of false claims.

Author has clearly stated that "all issues are fixed". The other guy found one unfixed issue. That makes the author's statement false.

I don't trust a person that lies, especially when they lie with such conviction and confidence. Reeks of narcissism.

-- EDIT - replying to @hunterb123 above --

I have reproduced the same error as in blogpost.

Re:V 0.3 by raphlinus on Friday July 01, 2022 @11:33AM (#31947858)
Hey, I went through another one of the examples, the lack of SFINAE, here's how I tested: I used the same methodology as the linked blog post. I'm getting the same compiler error as the blog post. Are you able to reproduce this?
Re:V 0.3 by ketzu on Friday July 01, 2022 @11:13AM (#31947510)
So, the review was my only contact with V until today, and I have to say your response seems unnecessarily hostile. I understand there night have been a lot of negativity around your project and it seems to be successful despite these, so nice for you.

The post seems to spend quite a lot of time on the V language and discussing it, so I got curious and put in some of the examples into V for windows. The results seem to be different, but my knowledge on V is too low to understand the implications fully.

The "No null" experiment does not give a segmentation faul, instead it prints &nil. That seems to be effectively a null value to me though. Adding another layer of null dereferencing creates an access violation/sefault.

The undefined behaviour for integer overflow is the exact same as in the post. (edit: and in the github issues it is marked as "won't fix" it seems V does not care about creating undefined behavior in the generated C code, just that the behavior is defined within V.)

The overwriting of len for the array seems to be fixed as the capacity is increased to the value of len seems to return nil references now.

The immutable->mutable trick seems to be caputred by the type checker.

The remarks on included libraries seems to hold, as well as the "simple webserver" being 2MB when compiling (although openssl seems to be included now).

I have no motivation to redo all the other experiments in the blog post. And your response as well as the small checks leave me not-very-impressed with V, as I can't take any of the claims on the website seriously like that. If you claim it is a v0.1 or v0.3 language, sure, make a list of features that actually exist or a roadmap when they are reached. This is especially true for the "novel memory management" which seems optimistically to assume it worked before when a changenote is included that the compiler doesn't leak memory anymore by default. That is not particularly instilling confidence, although it's the right direction.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:39AM (#31947961)
The post is unnecessarily hostile. Created by a new anonymous account, with the goal of attacking V and "not recommending to use it". Also with referencing the notorious ridiculous "V is vaporware" articles, it's pretty clear what the goal of the author was.

It'd take 10 minutes to submit github issues, instead they spent a month on this.

Null is only allowed in unsafe code.

Overwriting of len was never fixed, because it was never an issue in the first place. The author made it up. It's always worked like in Go.

Included libraries, you mean the json library that's part of vlib. So each Go program that uses net.http also has library dependencies by this logic.

Re:V 0.3 by Calavar on Friday July 01, 2022 @02:35PM (#31950796)
This is all around a terrible and nonconstructive attitude.

> The post is unnecessarily hostile. Created by a new anonymous account, with the goal of attacking V and "not recommending to use it".

What about it was hostile? It was written in a very neutral tone and was almost exclusively fact based, with just a couple of summative comments about the author's overall impressions at the end.

How could you possibly know the motives of an anonymous author? Seems like the author was smart to remain anonymous too, given the amount of vitriol the V community has directed his/her way for writing the review.

> Also with referencing the notorious ridiculous "V is vaporware" articles, it's pretty clear what the goal of the author was.

Of course a review will mention a widely circulated previous review. As much as you might like to pretend that it never existed, this isn't the CCP where we can expunge things that we don't particularly like from the historical record.

> It'd take 10 minutes to submit github issues, instead they spent a month on this.

I see, reviews are only okay if they are positive. Otherwise they must be github issues. What a convenient way to make sure that no negative review is ever "by the rules" and to question the motivations of anyone who dare write one.

Re:V 0.3 by Tozen on Friday July 01, 2022 @05:07PM (#31952933)
> What about it was hostile? It was written in a very neutral tone and was almost exclusively fact based, with just a couple of summative comments...

The review started out hostile by links to blogs and posts that smear V and the author from outright competitors and detractors! Completely unnecessary, if the purpose of the review was to stand on its own merits. It also sets the tone, of not being neutral, from the very start. And, links itself with other attack blogs and threads from the past. It made itself the newest link in the chain of attacks.

The review is highly opinionated. It's an evaluation of claims, where the author gives his opinions on their validity. The author never gives readers his qualifications for even being able to properly evaluate the language, and uses a throwaway account, where he can easily run away. The V developers are held accountable for their opinions, but not the reviewer. You can never hold the author of the review accountable for anything he got wrong, was mistaken about, or is missing.

It's also not a fair or objective evaluation, where he sought to get any input from V developers to clarify their positions about claims made. So it's his own one-sided perspective. He is going to be one-man judge, jury, and executioner. And that one-man judge's sentence is, "...I would not recommend spending time on V". Which is clearly very negative. It is also very presumptuous, that readers should come to his same negative conclusions, versus do their own evaluation, check out what the V community has to say, or check out the latest version of V.

> I see, reviews are only okay if they are positive. Otherwise they must be github issues.

Nobody said that reviews must only be positive. What is being conveyed is that if the reviewer really had a problem with using V, wanted it to become production-ready, or wanted something fixed then the way to do it is to submit issues or discussions to V's GitHub.

Otherwise, it shows the intention that one's purpose is not to fix anything, but to spread drama and smear. The reviewer has a throwaway GitHub account, where it would have been easy for them to verify various conclusions with developers, submit issues, or create a discussion at V's GitHub site.

Re:V 0.3 by anderskaseorg on Friday July 01, 2022 @05:00PM (#31952833)
> Null is only allowed in unsafe code.

That’s clearly not the case, as the exact code in the post prints ‘&nil’ in current V master, and if you add a dereference you get a segfault (which someone else just filed as https://github.com/vlang/v/issues/14911).

> Overwriting of len was never fixed, because it was never an issue in the first place. The author made it up.

The home page claims the language has “no null (allowed in unsafe code)”. println(*[]&int{len: 1}[0]) is not marked unsafe, yet it still segfaults by dereferencing a null pointer. Can you explain why you say this was never an issue?

(I’ve filed this as https://github.com/vlang/v/issues/14914. A related issue in maps was filed a year ago: https://github.com/vlang/v/issues/10837.)

> It's always worked like in Go.

Go is not a language that claims to have no null.

Re:V 0.3 by dmux on Friday July 01, 2022 @12:23PM (#31948778)
>It'd take 10 minutes to submit github issues, instead they spent a month on this.

If the author put in the work, I don't see the problem with it being a blog post. Also, given the history of github comments / issues being removed from the vlang github project, I don't blame them for wanting to keep their post for posterity.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @12:27PM (#31948851)
Lol, no issues/comments are removed.

One and only time a github comment was removed was before the open source release and I just started this new job of an open source maintainer.

Actually, sorry, I did remove one issue recently. It said "Delete this project, it's a joke".

Re:V 0.3 by super_flanker on Friday July 01, 2022 @02:29PM (#31950707)
> The immutable->mutable trick seems to be caputred by the type checker.

Just add the immutable variable's reference to a mutable array, now mutate the immutable variable using array[0], magic!!

The compiler is so basic and naive, it's laughable how their authors have guts to fight everyone about it's stability.

Re:V 0.3 by nabakin on Friday July 01, 2022 @02:29PM (#31950716)
I think you're missing the point here Alex. The amount of work you've put in, the number of projects you've made, and the drive you have are amazing. Everyone wants you and V to succeed but you make claims that are not true yet. You claim V has safety features but if it's trivially easy to exploit those safety features, then you don't actually have safety features. You claim V is as fast as C but there are many many many cases where V is slower than C. On average, V seems to be much slower than any compiled language. You claim V can compile a million lines of code in a second when that is not the average case. You claim V can do so many things but each time someone actually tries to verify those claims, it turns out there are many cases where it's not true or only true in one very narrow, specialized case.

When people read "V compiles itself in less than a second", they expect V to compile itself in less than a second for the general case (not just one very specific case). When people read "as fast as C", they expect V programs to have the same runtime as equivalent programs directly written in C. When people read "no null, no globals, no undefined behavior, immutability by default", they expect there to be no issues with this 99% of the time. When people read "Despite being at an early development stage, the V language is relatively stable", they don't expect this number of issues. I could go on, but the V documentation is filled with this.

In my opinion, if you keep going in this direction, no one will ever take V seriously. You might get some GitHub stars, you might get some inexperienced language developers helping you out, but if people can't trust V's claims, if V's claims continue to not hold up, no one will use V anything more than casually.

The simple solution to this is to walk back your claims and preface everything as unstable which is more accurate. Your GitHub description should make it obvious this is an experimental language with many issues. You should only list features in your README which are true and work for the average or general case. Any other features can be listed somewhere else as in progress or testing. Toning down your marketing is all it takes to earn back some trust.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @09:48PM (#31955283)
> You claim V is as fast as C but there are many many many cases where V is slower than C. On average, V seems to be much slower than any compiled language.

This is false.

> Everyone wants you and V to succeed

The same people who write articles about V and say V should die?

Re:V 0.3 by nabakin on Friday July 01, 2022 @10:56PM (#31955704)
> This is false.

Ok could you provide some benchmarks supporting this? I admit the article could be cherry picking benchmarks.

> The same people who write articles about V and say V should die?

Anyone saying that is probably fed up with the inaccurate claims. If you just make it clear to the user what features are in progress and that V is in an experimental state, I don't think anyone reasonable would have a problem with it.

Do you understand what I'm saying with the rest of my comment? Languages typically have a lot higher threshold of quality (a lot less bugs) when they say they have a feature implemented or when they say the language is "relatively stable".

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:10PM (#31955799)
Sure.

https://www.youtube.com/watch?v=pvP6wmcl_Sc

> they expect V to compile itself in less than a second for the general case (not just one very specific case).

What on earth are you talking about? There's no specific case. Check the video. Try it yourself. Have you actually tried it?

Can you list the inaccurate claims here please and in progress features that are not clear to the user?

Re:V 0.3 by capableweb on Friday July 01, 2022 @10:02AM (#31946538)
Slightly off-topic but this whole thing made me curious.

I keep seeing V being "attacked" by various people with these kind of blogposts (or even HN accounts dedicated to criticizing V), with broad range of claims or counter-claims to what V wants to achieve.

While this is maybe not completely absent when other new languages comes up (like Golang or Rust), it feels like V really brings out the people to come up with ways of criticizing it.

Do you have any ideas about why or how come? Have you noticed anything in particular that makes people want to (almost) aggressively "prove" V to be wrong?

Basically, do you have any guesses to why V seems to have more "enemies" out there, compared to lets say Rust or Go?

Re:V 0.3 by colejohnson66 on Friday July 01, 2022 @10:07AM (#31946597)
IMO, it's pretty simple. At the beginning, V was making huge claims that turned out to be false or misleading. The developer clarified that many of those features were actually goals. Fair enough.

There's also the whole issue with blocking people who criticized the language (eg. Xe) because V was being "attacked" as if there's some conspiracy to destroy V. The claims may be outdated, but the response by the developers put many people off.

V has made huge strides since then, but people are very resentful.

Re:V 0.3 by Shadonototra on Friday July 01, 2022 @10:29AM (#31946884)
Zig's author also publicly attacked V

There was a lot of jealousy when V was announced

Looks like the ones who need to self-reflect is Zig, they still don't have a self hosted compiler, meanwhile V compiles itself in less than a second

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:37AM (#31946978)
Yeah he was the first to call me a scammer and claimed V had a dependency on glfw.

He was really persistent with his attacks, even received a warning from dang.

I found it really surprising, because before the release he wrote:

> Wow, that's incredibly fast. Self-hosted in 2 weeks? Hot code reloading? This is everything I plan to do with Zig, but apparently done already. How did you do it so quickly?

Re:V 0.3 by williamstein on Friday July 01, 2022 @10:59AM (#31947282)
Can you provide a link for that quote? I want to read it in context, and my attempts searching the web only brings me back here and another place with this quote without a reference. Thanks!!
Re:V 0.3 by raphlinus on Friday July 01, 2022 @11:01AM (#31947313)
It's legit, here you go: https://news.ycombinator.com/item?id=19086589

I'll also add, my personal reading of the quote has more than a note of "this sounds too good to be true." But that could well be a matter of interpretation.

Re:V 0.3 by Shadonototra on Friday July 01, 2022 @11:15AM (#31947544)
it not that comment, there was some attacks after that

https://twitter.com/andy_kelley/status/1142503808901308418

I can't find the article where he mentions that it is a scam, i also remember people attacking the patreon backers

This tweet seems to be an apology so i guess we can move on

EDIT: there i found it: https://news.ycombinator.com/item?id=20230351

Re:V 0.3 by gompertz on Friday July 01, 2022 @11:37AM (#31947940)
Don't think was an apology. I find it dubious Zigs README on GitHub reads "never to exploit them financially". What a weird comment... Notwithstanding the whole readme comes off like a weird socialist manifesto.

V seeking (and receiving) Patreon or GitHub donations is not exploiting anyone. Neither mechanism is a contract. Either can be cancelled anytime, immediately. So like it or not, the sponsorship is a pretty accurate reflection of satisfied people (unless one is simply too lazy to cancel their pledge...).

Re:V 0.3 by Shadonototra on Friday July 01, 2022 @02:34PM (#31950770)
Yeah you are right, i might have misread his tweet, after reading it again, it sounds like he knows he fucked up and is trying to save the face
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:44AM (#31948044)
Yes, that's also the vibe I got.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:27AM (#31947750)
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:12AM (#31946660)
There actually is such a conspiracy. People who wrote these articles literally wrote they wanted V to die.

I'll make a detailed post about this next week.

Re:V 0.3 by wokwokwok on Friday July 01, 2022 @10:47AM (#31947121)
You posted lower down asking to be called out for specific behaviour that people find objectionable.

This.

It’s complete nonsense that there is a conspiracy to kill v off. You know it. We know it. Saying it is just drama for the sake of drama.

> And the issues discussed are questionable at best. Half the article is about a type checker bug, which was a 3 line fix.

> Then false claims like being able to modify array.len.

This.

You’re just creating drama saying things like this.

Just say: “The issues in that review have been fixed now, please have a look and submit bugs in the issue tracker if you find them”.

If someone has a legitimate thing to say, and at the time they say it it’s valid… that’s fine. If was wrong at the time, then by all means call it out.

…but here’s the good story about v: you fix bugs. A lot. Quickly. You build lots of stuff. It’s very impressive.

Things aren’t always perfect; it’s v0.3 for goodness sake. It’s fine. Just a) don’t claim it’s perfect when it’s not, and b) just clearly point out when issues that have been raised are fixed.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:50AM (#31947155)
It's not nonsense, read my replies below and the upcoming blog post next week. It's on a scale I've never seen before.
Re:V 0.3 by wokwokwok on Friday July 01, 2022 @11:01AM (#31947325)
I’m really sorry you feel that way; I honestly respect the work you do and I’m convinced you’re not correct about this… but hey; you’re deeper into it than me. Maybe there is? I don’t know.

…but, please also stop and read what I said.

You asked for specific examples where your interactions are causing problems.

this is it. Don’t post like this. You’re accusing people of attacking you, attacking other people (for example your comments on the author of Zig below).

This is what causes people to have bad interactions with you.

Re:V 0.3 by Tozen on Monday July 04, 2022 @02:26AM (#31974063)
I think you don't fully understand or know of the scale of the attacks and trolling carried out by detractors and competitors. Which includes hiding what they do and their true purposes, and attempting to instigate and influence others to perpetuate attacks, drama, and smears for them. There is also the gaslighting whenever people recognize some of their actions, recognize their throwaway or troll accounts, or against attempts to call them out. This includes doing such on other websites, not just HN.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:41AM (#31947999)
So people calling me a fraud and a scammer are not attacking me?
Re:V 0.3 by scoutt on Friday July 01, 2022 @12:05PM (#31948459)
I don't know you, but I think you should PR-manage the situation without being confrontational. Writing a blog post about it just invites the trolls to write an answer!

Do you know how many "X is better than Rust", "X language is trash" articles are out there?

Just be passive-aggressive like "Hey! thank you for the bug report and for taking the time to make V a better language! We'll check these errors!". Dismiss them and go your road.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @12:09PM (#31948530)
It's funny because in the previous discussion I got lots of "what's the problem? fix the bugs and publish your own post going through the points in this one".
Re:V 0.3 by scoutt on Friday July 01, 2022 @12:36PM (#31948987)
I think it’s OK to write a blog post about your progress, with a positive attitude. A very different thing is to write a blog post refuting a troll. “Don’t feed the troll” is as old as the internet.
Re:V 0.3 by bragr on Friday July 01, 2022 @01:28PM (#31949771)
Whataboutism is not a defense of our your own behavior.

https://en.wikipedia.org/wiki/Whataboutism

Re:V 0.3 by hunterb123 on Friday July 01, 2022 @06:44PM (#31953970)
Whataboutism doesn't apply here, you're using it wrong...
Re:V 0.3 by eterps on Friday July 01, 2022 @11:05AM (#31947381)
I sincerely hope you reconsider posting it. Even if you're a 100% right from your POV, it will still give off a negative energy and hurt your project. I think @wokwokwok has a good point, why not just focus on fixing bugs and building stuff instead?
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:43AM (#31948022)
Because these articles are meant to stay for years.

People will keep linking to them and say "didn't you see? V uses shell to do http requests! what a joke"

This most recent article by an anonymous author had all of the issues fixed within several days, but it wasn't updated, it'll stay like this forever, as planned.

Re:V 0.3 by eterps on Friday July 01, 2022 @11:56AM (#31948288)
I do understand that that must be frustrating. What I don't understand is why you think writing a blog post about it will have a positive effect on your project.
Re:V 0.3 by yakorevivan on Friday July 01, 2022 @11:52AM (#31948207)
Hey.... even if people are attacking V-lang, don't worry. Any good thing that disrupts existing "kings" gets thrashed initially. That's human behavior. Ignore it.

But, if lead dev replies in ways that seems offensive, or attacking, that is something that actually creates permanent dent in the adoption. Even if you are right in saying what you are saying, it still matters, a lot, to be polite.

I'm someone who really really wants V to succeed. I love what rust is able to achieve, but not the complexity it brings. V-lang gives me what I want from a language.

Language is beautiful, now it's your turn to be the same. Ignore the trolls. Many of them are paid.

And best wishes.... keep the good work. It never goes in-vain.

Re:V 0.3 by jsnell on Friday July 01, 2022 @10:50AM (#31947160)
You made that claim a couple of weeks ago, somebody investigated your claim, it turned out that you were grossly distorting the actual comment when paraphrasing. And given you continued to be active on that thread, you're clearly aware of this. Why continue spreading the lie? At this point you can't even claim it was an honest mistake.

[0] https://news.ycombinator.com/item?id=31830750

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:56AM (#31947244)
Is "I think it is something that should be ignored until it dies into obscurity" different from "I think it should die"?
Re:V 0.3 by tene on Friday July 01, 2022 @02:39PM (#31950853)
Yes, it's very different. Xe is predicting that V will die in obscurity, and recommending that people ignore it due to that prediction. Look at the second half of that comment:

> There are good ideas there, but if you sell someone the moon and give them a block of cheese that's kind of a scam.

Xe says "There are good ideas there". What do you think the metaphor of being sold the moon and receiving a block of cheese was intended to express? What does it mean to you? To me, it very clearly expresses that the language described by V's marketing would be extremely valuable and desirable, and that Xe is disappointed that V does not live up to what they expected. It's bizarre to me that you somehow see this as consistent with "should die".

What is your evidence that there's a conspiracy? Why do you believe that people are secretly coordinating on secret plans to destroy you?

Everything I've seen is completely consistent with individuals disapproving of what they see as you repeatedly claiming that V is far more capable and ready than it actually is and ignoring others who point out their perception of the same exaggerations.

I'll be curious to read your upcoming blog post about this topic, as I have yet to see you describe any justification for your conspiracy claims besides you finding it implausible that people could actually disapprove of how you talk about your work.

The blog posts that you keep claiming are maliciously-motivated conspiracy seem entirely normal criticism to me. They describe their goals and motivations, and those goals and motivations seem like very normal and reasonable motivations that explain the content of the blog post. I don't see anything that would need speculated malicious conspiracy to explain it.

Re:V 0.3 by Tozen on Friday July 01, 2022 @04:25PM (#31952334)
> ...seem entirely normal criticism to me...

Creating a blog, with an obvious smear title like "V is Vaporware" and making comments like "I recommend against using it for anything...", is not "normal" criticism. That is attempting to go above and beyond, with drama and smearing.

To include following such blog posts up with more linking, smearing, drama posts, and attempts to use such to get more attention for one's self at the expense of the V language.

Re:V 0.3 by tene on Friday July 01, 2022 @06:15PM (#31953717)
There are things that are actually vaporware. It is reasonable and normal for people to actually say when they believe that something has a lot of signs of being vaporware.

Are there really, truly no tools that you personally recommend against using?

Re:V 0.3 by bmacho on Friday July 01, 2022 @11:36AM (#31947922)
> There actually is such a conspiracy. People who wrote these articles literally wrote they wanted V to die.

That's not a conspiracy[0], but a review[1]. You should be glad for the people that actually spend time to market your product, raise your credibility, tell you how you see from outside, and provide independent checks. For free.

[0]: https://en.wikipedia.org/wiki/Conspiracy

[1]: https://en.wikipedia.org/wiki/Review

Re:V 0.3 by jsnell on Friday July 01, 2022 @11:00AM (#31947307)
Yes, it is completely different, as explained in that comment. Glad we've sorted this out, I trust that you'll stop making this claim in the future.
Re:V 0.3 by Tozen on Friday July 01, 2022 @02:35PM (#31950793)
I disagree with you as well. Clearly the blog creator is hoping for V's death, for whatever hidden intentions that they have.
Re:V 0.3 by jsnell on Friday July 01, 2022 @06:51PM (#31954042)
We cannot know what the blog author was hoping for, we can only know what they wrote. And what they wrote is not anywhere near what amedvednikov repeatedly claims. Why are you ok with such blatant misrepresntation? If this conspiracy actually exists, isn't there some evidence that actually stands on its own rather than needing to be lied about?
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:44AM (#31948033)
Agree to disagree. An author saying that proves the bias and the attack angle.
Re:V 0.3 by jsnell on Friday July 01, 2022 @12:16PM (#31948647)
It doesn't. But there's a more important point: you're paraphrasing somebody you clearly have a great deal of personal animosity toward, completely changing the meaning in the process, and with no indication that this is what's happening. You've continued doing that even when it's pointed out to you. There are two options I can see:

- You genuinely are not fluent enough in the language to either understand the original statement, or to write a fair paraphrase, and are not willing to believe this mistake.

- You know exactly what you're doing. That is, if you gave the actual quote, nobody would for a moment take it as a proof of your conspiracy claims.

Neither of the above is acting in good faith. I'd ask again whether you'll stop lying about what Xe said, but at this point the answer feels pretty obvious...

Re:V 0.3 by colejohnson66 on Friday July 01, 2022 @10:22AM (#31946793)
While wishing V would die is extreme, many people are just resentful about how V treated criticism in the beginning.

Not to mention that a conspiracy requires a coordinated effort. It's a lot more likely that blog writers are upset about something and decide to go on rants about other minutiae they find instead of submitting GitHub issues.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:26AM (#31946840)
There are coordinated efforts on discords to brigade such threads, there are entire new accounts created just to reply to each of my comments negatively (luckily just today HN banned such an account), this very post about V 0.3 was mass flagged 3 times and removed from the front page 3 times, there are articles that take a simple bug fixed by a 3 line commit, and make a huge deal out of it spending a month writing an attacking post. Who would spend a month to write an article about a type checker bug?
Re:V 0.3 by InefficientRed on Friday July 01, 2022 @10:53AM (#31947199)
> Who would spend a month to write an article about a type checker bug?

I have no horse in this race, have never heard of V, and frankly find the emotional charge in this comment section extraordinary... odd.

But I am a PL person.

Bugs in the type checker are pretty unambiguously a big deal. I totally understand why the examples in the blog post are alarming. The point isn't that they can be fixed by 3 lines; the point is that there were obvious soundness bugs in the type checker implementation and the language designer's attitude seems to be "NBD if the patch is small enough". Given the post and reaction, I would not be surprised if there are many more soundness bugs lurking. So, that's an issue if I want to use the language for anything serious.

That said, it looks like a hobby language in its early stages of approaching maturity, so the degree of divisiveness is seriously confusing. My reaction to all the drama is closer to "yup some soundness bugs; type systems get subtle fast, what a great thing to learn from" than "I hope V dies / the V critics are terrible".

I'm guessing there are weird personality/politics at play, but don't care enough to find out.

Anyways. I liked the Android examples.

Re:V 0.3 by colejohnson66 on Friday July 01, 2022 @10:28AM (#31946865)
Simply, V is very divisive. So, some people who peruse HN but don't have an account will see a V post, and make an account just to comment. Humans are just irrational.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:30AM (#31946904)
I don't creating an account and monitoring my comments and replying to them with attacks and trolling for 3 years is "just commenting".
Re:V 0.3 by colejohnson66 on Friday July 01, 2022 @10:33AM (#31946931)
There's definitely trolls; I wasn't trying to imply otherwise. There's always going to be people who think your project is stupid, and it'll only get worse as the project grows. I think the best solution is to just ignore them.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:38AM (#31946996)
Luckily in this case the amount of trolling goes down as the project grows :)

There are now V contributors who used to troll V back in the day.

Re:V 0.3 by hunterb123 on Friday July 01, 2022 @10:41AM (#31947033)
> Simply, V is very divisive.

How is an open-source programming language divisive?

Seems the people brigading are toxic and divisive, not the language or it's maintainers.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:43AM (#31947064)
Exactly! Thank you :)
Re:V 0.3 by gompertz on Friday July 01, 2022 @10:23AM (#31946808)
It's great you're level headed on this. As an indirect measure, I've perused the Discords of competing languages and the vibe is a world apart in terms of maturity, age group, topics (bullying is very prevailing, talking politics rampant, excessive anime) - essentially unmoderated reflections of character. So it's no wonder that if that's the community forged behind the scenes (in those competing languages), that it's going to bleed out and become issues elsewhere - and V is one such topic that seems to be commonly targeted by those groups.
Re:V 0.3 by wb13579 on Friday July 01, 2022 @10:42AM (#31947048)
It's because V made impossible promises, and used those to get donations.

For example from wayback machine http://web.archive.org/web/20190520021931/https://vlang.io/d...: "(Work in progress) There's no garbage collection or reference counting. V cleans everything up during compilation. If your V program compiles, it's guaranteed that it's going to be leak free."

When people called him out for this saying that this was impossible he doubled down on it and said that it's fine to say things like that because of the "work in progress", as if it was coming.

It turns out, it was impossible. V eventually had to add reference counting.

The worst part is that he used lies like this to get thousands of dollars from Patreon sponsors.

It seems like he's trying to clean up his act, but he's still making some dubious claims. He claims to have invented an "innovative and flexible memory management" reference counting algorithm that removes 80-90% of overhead. But there's no way to do that with mutable data, as far as i know. And sure enough, it doesn't work, users are still told to use the garbage collection option. If that turns out to be true, I might change my mind, but I fully expect that it's a false promise too.

Re:V 0.3 by gompertz on Friday July 01, 2022 @11:01AM (#31947314)
V backer here. I've never ever felt remotely scammed or deceived. So people who bring up the scamming topic can continue to do so with the imaginary money they did not pledge/donate.

Also I see the Patreon topic a lot - Patreon is not a contract. If one is unhappy they can stop pledging ANY time, immediately. So like it or not, the Patreon support you see is a very accurate representation of satisfied backers as well.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:20AM (#31947628)
Thank you for the support!
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:51AM (#31947177)
It does work, and there's a 1.5 year old working demo:

https://www.youtube.com/watch?v=gmB8ea8uLsM

0 GC is used.

None of the people who ever donated or are still donating felt they were being scammed. They often write about this here on HN.

Re:V 0.3 by wb13579 on Friday July 01, 2022 @10:56AM (#31947242)
A demo, sure. But answer us this: does autofree ever crash, and does autofree ever leak?
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:01AM (#31947321)
A 0.3 language feature that is marked as "not ready for production" on the website have bugs. How unexpected.
Re:V 0.3 by wb13579 on Friday July 01, 2022 @11:09AM (#31947455)
That's what I thought.

Last time it seemed impossible, you said it was "work in progress" for years, and it turned out to be a lie.

This time it seems impossible, and it's been "work in progress" for 1.5 years. You can see why that's suspicious.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:20AM (#31947622)
You have a very strange definition of a lie. There's a working example. Anyone can run it and inspect it, it's all open source.

Autofree hasn't been a priority because of how unexpectedly well the GC is performing with V, but it will be finished.

All this is clearly stated on the website.

Re:V 0.3 by wb13579 on Friday July 01, 2022 @11:32AM (#31947835)
Your claim of "(Work in progress) There's no garbage collection or reference counting. V cleans everything up during compilation. If your V program compiles, it's guaranteed that it's going to be leak free." was absolutely a lie. That's why you had to eventually fall back to reference counting.

The newer reference counting system has an example but it's very easy to conjure a working example of a system that has fundamental holes. When people use it for larger programs it crashes or leaks even today. Is that incorrect?

Re:V 0.3 by bragr on Friday July 01, 2022 @10:18AM (#31946726)
V has "enemies" because that's how they respond to people giving them constructive criticism and questioning their claims. Most authors would relish of thorough technical analysis of where their issues where so they could improve their new language and compiler, but not V it seems.

They mostly seem to deflect with denial or claims the issues were 'nothingburgers', but if that's the case, it should be trivial to offer a rebuttal in the form of a blog post, but instead we get ad hominems and conspiracy theories.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:33AM (#31946921)
Completely not true. We welcome criticism and feedback, we even have a topic with 800 messages called "What don't you like about V / what would you like to be changed?"

https://github.com/vlang/v/discussions/7610

Wishing V to die and making false accusations is not "constructive criticism".

There will be a blog post next week.

Re:V 0.3 by mihaigalos on Friday July 01, 2022 @11:19AM (#31947619)
The community isn't too friendly, I'm sorry.

In the cited thread, I've deleted my contribution because of the tone of the discussion (passive-agressive know-it-alls with smirk emojis): https://github.com/vlang/v/discussions/7610#discussioncommen...

Is this how you welcome people to the community?

I enjoy V and contributed several PRs which got merged, but there's definitely an attitude problem there. I gave up contributions because of it.

Re:V 0.3 by Tozen on Monday July 04, 2022 @08:43PM (#31983131)
Out of curiosity, I checked the discussion in which you referred to by link. The person in question is not a developer or contributor, but appears to be passionate about the discussion. I don't think it's bad to have a difference of opinion, even among good friends. In addition, we can't always be right on every issue, and sometimes we have to "agree, to disagree".

The other person in that discussion on V's GitHub even apologized for appearing harsh, seems to have begged you to come back, and gave you a compliment.

Also deleting your part of the discussion also robs other readers from evaluating the full merits of your side. There will usually be people on your side of the discussion as well or see your point of view. I think you will find that overall and from what I've seen, people in the V community can be appreciative and welcoming, but like anywhere its a mix of different personalities and characters.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:25AM (#31947720)
This user is not a member of the V team, and never contributed to the V project.

He enjoys language development and submits his feedback and ideas, discusses other ideas etc.

I do not work as a big censor and read every single of the thousands of messages, and I do not have time to do it.

Re:V 0.3 by mihaigalos on Friday July 01, 2022 @11:28AM (#31947773)
That was a rhetorical question, I am not implying you should do anything. Thank you for the transparency.
Re:V 0.3 by gompertz on Friday July 01, 2022 @10:37AM (#31946983)
Just like work, and in life, you're going to come across a myriad of people who handle criticism in different ways. Be it for cultural differences, deductive reasoning differences, even down to childhood upbringing, you know the story... We all do. It's 2022.

Not that you've done so; but others seem to reciprocate back with bullying, and with twice the force of any denials. A lot of people need to get the wisdom that others are different from them, and simply move on. The same threads, blogs, comments have come up on every single V post - living rent free in many people's heads.

Re:V 0.3 by hunterb123 on Friday July 01, 2022 @10:30AM (#31946901)
The "nothingburger" you quoted is a single word you took from a reply chain in which amedvednikov explained the 800 byte "memory leak" was actually just GC overhead and expected.

So it wasn't a memory leak, it is GC overhead, hence it being labeled as a "nothingburger".

What specifically do you feel hasn't been resolved or addressed properly?

Re:V 0.3 by bragr on Friday July 01, 2022 @11:09AM (#31947456)
>What specifically do you feel hasn't been resolved or addressed properly?

The author responding constructively to criticism. The bugs may be fixed, but if the author can't calmly engage and link to the fixed commit, or give evidence that, for example, everything compiled with GCC leaks those 800 bytes, well that's a major red flag about the project management of V.

Re:V 0.3 by striking on Friday July 01, 2022 @10:14AM (#31946686)
I think the highly aspirational nature of the claims about V upon its original launch are why it attracted so much scrutiny. It claimed to do a lot of things and didn't clearly separate things that might be delivered in the future from those that would be features present in the language today.

And, judging by the review linked upthread, as of last month this has remained the case. For this reason, I'm not surprised that the scrutiny continues.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:17AM (#31946722)
If you look at other posts in this thread, you'll see that this review is completely irrelevant since the bugs it complained about were fixed in several 3 line commits.
Re:V 0.3 by striking on Friday July 01, 2022 @11:09AM (#31947447)
I won't pretend to be up to date on your language and what is fixed or working, but if it was so easy to fix these bugs that were apparently so trivial, why weren't they fixed before announcing / releasing the features? Even just communicating that a feature isn't done yet and may need a little more time (e.g. a beta tag) would go a long way in rebuilding trust with people outside your community.

Meanwhile, defensive reactions like those I see in and around this thread make me feel like I trust you less.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:22AM (#31947660)
I'm sorry but that makes completely no sense. "Why didn't you release software without any bugs?"

That's not how the world works. And it's open source, where hundreds of contributors help you find and fix these bugs. That's the whole point.

Re:V 0.3 by striking on Friday July 01, 2022 @01:40PM (#31949935)
As I said in my previous reply, you're more than welcome to stick a beta tag on something that isn't ready for prime time yet. Take a look at Rust and their releases as an example of the ultimate in building a stable foundation that people trust.

I'm not asking you to never ship a bug. I'm saying I don't trust you or your language and giving you an example of how you might regain my trust. Feel free to ignore my advice, but if your goal is to encourage more people to use your language instead of encouraging more people to fight you, maybe you could at least give the impression that you were willing to hear someone out instead of telling them their opinion doesn't make any sense at all.

Re:V 0.3 by amedvednikov on Sunday July 03, 2022 @01:57AM (#31965447)
It literally says V 0.3 in the very center of the website. First thing.
Re:V 0.3 by striking on Wednesday July 06, 2022 @02:41PM (#32005064)
Yeah, and that's not enough. I guess I'll hold off on trying your language until 1.0.
Re:V 0.3 by the_duke on Friday July 01, 2022 @10:08AM (#31946609)
You might want to look into the somewhat dodgy history of the language. The negativity is not surprising.

Though you may just be asking rhetorically to probe for a response from the founder, in which case, never mind.

Re:V 0.3 by capableweb on Friday July 01, 2022 @10:11AM (#31946646)
> Though you may just be asking somewhat rhetorically to probe for a response from a supporter

No, I was genuinely asking the question directly at the creator of the project, to understand their view of the contention they seem to be at the receiving end of.

I know the history of the project, but it seems to me like most languages in their pre 1.0 make claims about what they would like the language to be, not what it currently is, but they still don't receive their criticism in such manner. Or maybe I'm just reading into it too much. Hence the question :)

Re:V 0.3 by yellowapple on Friday July 01, 2022 @07:13PM (#31954259)
> most languages in their pre 1.0 make claims about what they would like the language to be, not what it currently is, but they still don't receive their criticism in such manner

That's because those languages make those claims in future-tense rather than past tense; they explicitly state them as goals, rather than presenting them as if they're already implemented. For example, I wrote a tiny scripting language for Erlang/OTP apps called OTPCL, and I make it clear in the README which features are actually implemented (like the parser and interpreter) v. which ones are in progress (like the standard library) v. which ones haven't been started at all yet (like the compiler). Same deal with up-and-coming languages closer to V's use case, like Zig; there's a clear distinction between those three levels of completeness.

V did not make that distinction originally; a large number of its radically ambitious goals were presented on the website as if they were already implemented, only to later be revealed to be "WIP" at best. A lot of people - including, at one point, Zig's creator - assumed malice here, figuring the disparity between the website v. the actual releases to be an attempt to swindle Patreon backers (I can't read the mind of V's author, but I would guess that it was more of a language/communication thing than anything outright malicious). In any case, that left a pretty negative first impression for a lot of folks, myself included - and while it seems V is making some progress, it's hard to get that bad taste out of my mouth and consider even trying it out when languages like Zig and Odin and Nim and Crystal seem to be a lot more transparent and realistic from the outset.

Re:V 0.3 by cxr on Friday July 01, 2022 @10:26AM (#31946846)
> You might want to look into the very dodgy history of the language. The negativity is not surprising.

This is a mostly content-free reply that casts vague aspersions; it's not especially helpful when someone asks, essentially, hey, what's going on here? to then respond that they may be interested in looking into what's going on. Of course they're interested—that's where the question comes from, after all. Please respond meaningfully, then, and abstain from replying with non-specific ad hominem.

Re:V 0.3 by the_duke on Friday July 01, 2022 @10:54AM (#31947212)
Look, I'm not hostile towards the initiator or the language. I'm happy to give V a chance in the future.

But it started out with huge promises that could never be kept, and were tied to fund raising. This is why there was so much skepticism in the beginning, and why you are facing so much hostility now.

The way to change that is by professionalism and convincing arguments, benchmarks, showing how the promises are kept and responding to criticism in a good faith manner by providing technical explanations.

Not by responding with more hostility.

It's also perfectly fine for fans of the language to support it here, but there are many "content-free" posts in this submission that just hype up V with minimal value-add...

I personally don't see an ad-hominem in my post.

Re:V 0.3 by cxr on Friday July 01, 2022 @06:43PM (#31953963)
Nothing in this comment makes sense as a reply to me or what I wrote.

> This is why[...] you are facing so much hostility now.

You are confused about something. You seem to think I'm someone else.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:59AM (#31947280)
Can you please list here the huge promises that could never be kept?

1. 2. 3.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:39AM (#31947011)
Thank you. I got really tired of these vague accusations over the last 3 years.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:16AM (#31946706)
The history is not dodgy. There was an attempt to make it so by overblown picky articles attacking a 0.1 language. I'm going to cover these next week.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:10AM (#31946635)
I have some guesses.

I'll publish a big blog post about this. It will debunk all these "V is a scam" articles.

Basically V appeared out of nowhere and got popular very fast. It took a lot of shortcuts: it was self hosted on release, GitHub started supporting it 1 month after the release, it had hot code reloading, fast compilation (v self is <1s [0]) and so on.

People developing other languages and their communities didn't like it, and decided to attack it.

There were 2 strategies: making completely false statements (like claiming that the V compiler has a dependency on glfw, so the no dependency claim is false, and claiming that V programs use libc, system's only official API, therefore again the no dependency claim is false) and nitpicking over bugs that are inevitable in a 0.1 language, and sometimes complaining that features explicitly marked as [wip] are not ready yet. One of the common questions I saw is "why release it if it's not ready". While that's the whole point of open source. I got lots of help from 500+ contributors and got to this point a lot faster.

Then there was also a misunderstanding with the "preview" release one week before the source code was released, and many thought V was going to be closed source. Over this week unfinished features were not marked as [wip]. They were marked so after the open source release, and now there're no [wip] features on the website. Everything listed there is working in latest V.

[0]: https://www.youtube.com/watch?v=pvP6wmcl_Sc

Re:V 0.3 by paskozdilar on Friday July 01, 2022 @10:39AM (#31947014)
> People developing other languages and their communities didn't like it, and decided to attack it.

I honestly doubt this is the case. Aside from some cargo-culters (which are far from being a majority), most programming language enthusiasts are very welcoming to new languages and ideas they bring with them. I have never seen a "language war" happening this way.

Personally, I admire the V's ambitions (if the autofree() ever reaches production-quality it would be a total triumph over Golang's garbage collection approach), but I dislike the unprofessional approach to the community (explained in many other comments - particularly false claims about language capabilities, deleting criticisms, unwillingness to admit shortcomings and making up excuses for each of them, etc.).

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:55AM (#31947224)
There are 0 false claims about language capabilities on the website or in the docs.

If you can link one, that'd be great, and it'll be fixed. I've spent a lot of time verifying all claims are valid.

For example there was the "functions are pure by default except IO" which caused lots of criticism and memes. I simply changed the wording to a more verbose but correct phrase. So we do admit shortcomings and not make up excuses "for each of them"

We do not delete criticisms, we actually welcome them and any kind of feedback:

https://github.com/vlang/v/discussions/7610

Re:V 0.3 by paskozdilar on Friday July 01, 2022 @11:04AM (#31947373)
So you're sticking with "people are evil and hate me"?
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:21AM (#31947650)
So can you list the "false claims about language capabilities" here?
Re:V 0.3 by defen on Friday July 01, 2022 @12:56PM (#31949322)
Saying "no undefined behavior" when what you really mean is "We define our language's behavior to be the same as C's" (in other words, you just punt undefined behavior to the C compiler) is deceptive at best. I'm specifically thinking of signed integer overflow here, but that makes me think there may be other cases as well.
Re:V 0.3 by paskozdilar on Friday July 01, 2022 @12:07PM (#31948489)
You're reading my words, but you're not trying to understand what I'm saying.

Unless you demonstrate an honest effort to understand, I will not continue this pointless argument.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @09:52PM (#31955317)
You said there are false claims about language capabilities, I asked you to list them. It's a reasonable request. I don't want to have false claims on the website.
Re:V 0.3 by zamberzand on Friday July 01, 2022 @10:11PM (#31955430)
In my opinion, the current documentation on the autofree engine [0] constitutes a false claim about language capabilities:

> Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via reference counting.

> The developer doesn't need to change anything in their code. "It just works", like in Python, Go, or Java, except there's no heavy GC tracing everything or expensive RC for each object.

[0]: https://github.com/vlang/v/blob/master/doc/docs.md#memory-ma...

So, I am not entirely sure the best way to quantify whether this is true. However, I thought a fun test would be recreating "my first memory leak" -- the first memory leak I can remember fixing in code that I wrote. Specifically, I was essentially leaking some bespoke heap-allocated iterators I had created (inside of an infinite game loop).

So here is my little test:

    struct Iter {
    mut:
        pointer int
    }

    fn main() {
        my_array := [ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 ]
        
        for true { // simulated game loop
            mut iter := &Iter { 0 }
            
            // heap allocated iterator
            for iter.pointer < my_array.len {
                print(my_array[iter.pointer])
                print(" ")
                iter.pointer += 1
            }
            println("")
        }
    }
I compiled this with -autofree -gc none, with V 0.3. Checking it with valgrind, it continuously leaks memory.

So, from what I can tell, this description of the autofree engine in the documentation does not accurately describe the existing functionality available in V.

I am curious where the 90%-100% figure comes from. It is such a specific number that it implies to me, as a reader, that it comes from an empirical measurement of an existing system. But, there is no link to where this measurement was taken. In my opinion, the documentation should include some details about how these figures were generated.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @10:32PM (#31955545)
No, it describes it absolutely accurately:

> until V's autofree engine is production ready.

Re:V 0.3 by zamberzand on Friday July 01, 2022 @10:40PM (#31955611)
So, to be clear, is the intended reading of the documentation as follows?

> Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via reference counting.

> The developer doesn't need to change anything in their code. "It just works", like in Python, Go, or Java, except there's no heavy GC tracing everything or expensive RC for each object.

> These points are both currently untrue, and should not be relied on in code.

I'm hoping I don't come off as flippant here. I just don't see any way to interpret these claims as an accurate description without adding that third bullet point.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:11PM (#31955809)
They are both true, and it clearly says it's not production ready yet, so there are bugs.
Re:V 0.3 by zamberzand on Saturday July 02, 2022 @12:13AM (#31956172)
Okay, I really don't understand what you're saying here.

The claims are objectively false. The autofree engine objectively does not free 90%-100% of objects, it is objectively not true that "It just works."

If I understand you, you're saying that autofree doesn't work because of bugs in the compiler. But, the fact that the claims are false as a result of bugs in the compiler does not somehow make those claims true.

Re:V 0.3 by Tozen on Saturday July 02, 2022 @02:11AM (#31956685)
Autofree exists and does work (https://youtu.be/gmB8ea8uLsM), however, it doesn't work where a user can have a complete lack of understanding about memory management like various GCs do or have never used it before. Autofree, as it is, also requires looking at examples of usage in various programs.

The website and documentation does explain the situation, for those that cared to actually read them. "Right now allocations are handled by a minimal and well performing GC until V's autofree engine is production ready." This should be enough to understand that autofree is WIP and not enabled by default (which is referred to in the documentation).

The other issue, is that people who have never used V or autofree (not even talking outright detractors), might interject or repeat uninformed opinions about the situation. Where those that have more thoroughly experimented with autofree and have used V or are in the V community, would likely understand the situation and history of it (have read other things about it on V's GitHub or asked about it on discord).

Re:V 0.3 by zamberzand on Saturday July 02, 2022 @02:41AM (#31956792)
I understand that autofree is WIP. I read that part of the docs, and I have watched the demo.

But I don't really understand what the intended reading of the documentation is.

If I were to completely take these two paragraphs out of context, they are factually untrue:

> Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via reference counting.

> The developer doesn't need to change anything in their code. "It just works", like in Python, Go, or Java, except there's no heavy GC tracing everything or expensive RC for each object.

So, what does this mean? Well, nothing, necessarily. If the context clarifies that these points are all untrue, then, the documentation could be considered perfectly accurate as far as I'm concerned.

However, when I asked if the intended reading of the documentation was that these points are untrue, the answer was--no, these points are all actually true.

I don't understand that position. These claims are straightforwardly untrue.

To me, your response is reinforcing my original proposed reading. That is--to me, your response indicates that I should read these claims as being false, and that the documentation is acknowledging them as false.

Now to me, that is a perfectly good response to my original comment. If this part of the documentation is not intended to be read as a statement of fact, that makes perfect sense to me, even though I do think it could be communicated better.

As it stands, though, I'm not really sure what I'm meant to get from this[0] comment.

[0] https://news.ycombinator.com/item?id=31955809

Re:V 0.3 by Tozen on Saturday July 02, 2022 @04:04AM (#31957132)
When a person new to V reads the documentation (which they should be doing), they would also see the following.

"Note 2: Autofree is still WIP. Until it stabilises and becomes the default, please avoid using it. Right now allocations are handled by a minimal and well performing GC until V's autofree engine is production ready."

So, autofree (as a WIP) is not at this point working as intended, which is described by, "The developer doesn't need to change anything in their code. "It just works"..." I don't take this as any attempt to mislead or deceive, like you seem to be doing. The documentation is even telling people to avoid using autofree, as it's WIP.

Yes, there is a difference between how autofree is suppose to work versus how it is presently working. Yes of course, I can totally see how people get very excited about autofree, and want it 100% working or want its development accelerated. But, it should be obvious that at this point, when a person is using it, they are experimenting. When a person takes it upon themselves to enable autofree, in an alpha status language, they shouldn't be surprised there are issues.

Then bringing it back to what I had typed about earlier, using autofree at this point, requires that the person understands something about memory management and looks at examples of its usage. Particularly when a person is going to enable it, against the recommendation of the documentation.

Re:V 0.3 by zamberzand on Saturday July 02, 2022 @12:41PM (#31960476)
It seems we are essentially in agreement on how the documentation is meant to be read, which is that the points it makes about autofree are not meant to be statements of fact.
Re:V 0.3 by Tozen on Saturday July 02, 2022 @07:15PM (#31963381)
Not exactly, because what I'm saying is that the V website and documentation is explaining what autofree does, describing what autofree is, and how it works.

It appears you are implying that if autofree doesn't work perfectly as it is described, then that indicates a false claim or deception.

The counter to that (and what I'm saying) is that the website and documentation states that autofree is WIP and even recommends not to use it, and tells users that at this time GC is used instead. There is no deception, they are being clear. So if the user goes against the recommendation of the documentation, they should not be surprised that WIP autofree in alpha status V, is not working perfectly.

Furthermore, autofree does exist. We are not talking about a lie or false claim, where something is not in existence. Autofree does function, so here too, we are not talking about something that does not work at all. We are now talking about to the degree it is working or how well it works. Which on that point, the website and documentation both indicate WIP, so a user should not yet expect it to fully function.

I further elaborated that if you experiment with it, you may get autofree to work well. But, that can depend on: the program, can require experience using V, some memory management knowledge, and/or going through examples of V programs that use it. The expectation (and what those in the V community are aware of) is that as V goes to higher versions on its way to beta status, we will see better performing versions of autofree that requires less to no needed user knowledge about details.

Re:V 0.3 by avgcorrection on Friday July 01, 2022 @10:35AM (#31946945)
Should the null hypothesis be that all languages deserve equal praise & blame and thus equal amounts of negative & positive critique?

Maybe this language deserves more criticism. Or people are biased against it. Could be either explanation, or something else. But there ain’t just one single possibility.

Re:V 0.3 by Tozen on Saturday July 02, 2022 @01:38AM (#31956566)
> ...it feels like V really brings out the people to come up with ways of criticizing it.

V is an up and coming language in the categories of both C and Go alternatives. This means a wide range of competitors and "acolytes" who may "come out of the woodworks" to take a shot at a rival, at anytime. The more popular they believe V is becoming or the more threatened by it that they may feel, the more likely we are to see "shots fired".

This is not to say that various criticisms are not or will not be valid. In fact, constructive criticism can be good and healthy. Among them, bringing bugs and issues to the attention of developers or having technical discussions with the language's community.

But, the negative or non-constructive acts (attack blogs, downvoting, flagging, gaslighting, trolling, etc...) do shed light on some of the odd heavy-handed, sneaky, or aggressive vibes that many of us can see. It demonstrates the intentions of bad actors or those acting in bad faith.

> ...absent when other new languages comes up (like Golang or Rust)...

Golang and Rust are backed by major companies. They do have plenty of "enemies" and competitors taking shots at them, but they aren't given the media "airtime" for their negative narratives to stick and their attempts get drowned out by the size of the language's userbase or amount of "infomercials".

Various other newer languages simply lack the popularity, userbase, or sponsors for most to even take notice or care. So they are simply not talked about.

Re:V 0.3 by Tozen on Friday July 01, 2022 @02:22PM (#31950578)
> Basically, do you have any guesses to why V seems to have more "enemies" out there, compared to lets say Rust or Go?

You have to keep in mind that V is an up and coming language, that is an alternative to Go, and somewhat to Rust. V is in the categories of C and Go alternatives. There are many other competing languages in V's categories, such as Zig, Odin, Nim, etc...

Not too hard to see how "enemies" and rivals can "pop out of the woodwork" to take shots, the more popular that V becomes or the more they might feel that V is a threat to their interests.

As for Go and Rust, they are backed by major companies, where "enemies" of their language will simply not get any or little media "airtime" nor enough traction to establish a negative public narrative that can stick. You can attempt to say something negative about them, but will be ignored or drowned out in various ways.