Live data from Hacker News

V Language Review (2023)

n-skvortsov-1997.github.io

81–90 of 115 posts

Re: V Language Review (2023)

#81
post #66
post #63

Earlier quoted context omitted.

I would argue that at least some of the grief GNOME gets is deserved. Especially given their attitude towards their users.

As I said, some grief is deserved in all these cases. But unreasonable criticism makes people also not listen to more reasonable (deserved) criticism. That was my entire point. That you're completely ignoring this and instead just reply with an unsubstantial and off-topic dig at gnome is an excellent demonstration of my point.

Wasn't actually off-topic since you specifically mentioned them.

And a lot the incidents I can think of, of people being unreasonable there, came AFTER attempts at reasonable requests were ignored.

But sure go off.

Re: V Language Review (2023)

#82

Can someone explain the backstory of what V is and why someone took the time to write this? To the uninitiated this sounds like someone criticizing some kid’s side project. I’m picking up some context clues that V is widely used / famous / notable / significant somehow, but the only time I have ever heard of it before this is Xe Iaso’s similarly negative posts. Did V receive some huge funding grant that made it the t…

We can’t just appreciate that someone took the time to evaluate the technical merits of a particular technology? What the hell does all of this peripheral stuff (“is the author otherwise well-known?”) matter?

Re: V Language Review (2023)

#83

"a summary of my experience with the language over 6 months " -- I was only able to use it for a week around Christmas before hitting compiler bugs. I like the look of it, but I can't currently use it.

To be fair, I ran into a compiler bug in Zig within a few hours of using it. I'd still expect Zig to be a lot less buggy than V, based on what I heard. Last time I looked at V it just seemed like the language wanted to have it all. No tradeoffs, just "The best parts of Rust and Go" with no explanation how that's remotely achievable (and it wasn't, judging by the attempts to make "auto free" memory management happen,…

Then again, out of the C alternative languages Zig, Odin and C3 - Zig’s always been the one with the most open bugs despite (or due to?) having by far the most amount of people working on it.

Ironic now when the compiler is written in Zig considering how Zig is advertising itself as being better at stability and reliability than C/C++ (the C3 compiler is written in C and Odin’s compiler is a C-like C++)

Re: V Language Review (2023)

#85
post #83

Earlier quoted context omitted.

To be fair, I ran into a compiler bug in Zig within a few hours of using it. I'd still expect Zig to be a lot less buggy than V, based on what I heard. Last time I looked at V it just seemed like the language wanted to have it all. No tradeoffs, just "The best parts of Rust and Go" with no explanation how that's remotely achievable (and it wasn't, judging by the attempts to make "auto free" memory management happen,…

Then again, out of the C alternative languages Zig, Odin and C3 - Zig’s always been the one with the most open bugs despite (or due to?) having by far the most amount of people working on it. Ironic now when the compiler is written in Zig considering how Zig is advertising itself as being better at stability and reliability than C/C++ (the C3 compiler is written in C and Odin’s compiler is a C-like C++)

[flagged]

Re: V Language Review (2023)

#87
post #83

Earlier quoted context omitted.

To be fair, I ran into a compiler bug in Zig within a few hours of using it. I'd still expect Zig to be a lot less buggy than V, based on what I heard. Last time I looked at V it just seemed like the language wanted to have it all. No tradeoffs, just "The best parts of Rust and Go" with no explanation how that's remotely achievable (and it wasn't, judging by the attempts to make "auto free" memory management happen,…

Then again, out of the C alternative languages Zig, Odin and C3 - Zig’s always been the one with the most open bugs despite (or due to?) having by far the most amount of people working on it. Ironic now when the compiler is written in Zig considering how Zig is advertising itself as being better at stability and reliability than C/C++ (the C3 compiler is written in C and Odin’s compiler is a C-like C++)

Zig, similar to Rust, is like crawling into a syntax dumpster fire. Ugh. Give me C any day if I didn't have a choice for better options.

Re: V Language Review (2023)

#88

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

They have more starts than C# at 10k

Then Mojo also has more stars than C#. I guess GitHub stars don't mean much.

Re: V Language Review (2023)

#89

Earlier quoted context omitted.

What's amazing is how large the community became and how strong their love and belief was.

[flagged]

How do you feel about the basic stuff not working as demonstrated in the article? What's so special about V that you prefer using a literally broken language? (The perma memory leaks are basically enough already to qualify it as broken)

Genuinely curious, I don't understand the point

Re: V Language Review (2023)

#90

Can someone explain the backstory of what V is and why someone took the time to write this? To the uninitiated this sounds like someone criticizing some kid’s side project. I’m picking up some context clues that V is widely used / famous / notable / significant somehow, but the only time I have ever heard of it before this is Xe Iaso’s similarly negative posts. Did V receive some huge funding grant that made it the t…

> To the uninitiated this sounds like someone criticizing some kid’s side project.

As someone uninitiated, you may not appreciate what a devastating burn that is.

Post reply on HN