[Athas]

This blog post showcases V in a positive light. I suppose it is good that people can have productive experiences with it now, although I don't see from this post why it is a significant improvement on Go.

The problems discussed (performance, compiler fragility) are somewhat worrying though. My impression is still that V is not particularly robust and focuses on flashy things instead of getting the basics right. I must admit that it is however still hard to look at V objectively, given the near-fradulent presentation it had when it was first announced.

[theamk]

"near-fradulent presentation it had when it was first announced"?

It's not just in the past, the lies are still here. A very simple to explain example: https://vlang.io/ proudly says "No null (allowed in unsafe code)", while going to V playground and typing

    x := []&int { len: 10, cap: 0 }; println(x[4])

still prints "&nil" (note how there is no unsafe in sight).

The V team are either intentionally misleading people or have only vague idea about how languages are designed. Stay away.

[baranul]

Such code will generate warnings, "arrays of references need to be initialized right away, therefore `len:` cannot be used (unless inside `unsafe`, or if you also use `init:`)". By the way, the other optional parameter, besides `len` and `cap`, is `init` (in the documentation too). The person is being told to use unsafe or do something else.

Warnings are given to allow the programmer to experiment or solve by other methods. Beta means language still in development. Lastly and for V, the warnings mean that in production mode (-prod flag), that kind of code will not compile.

[rurban]

Rust got away with the very same overhype and lies, so many projects will follow. It's still useful, just don't believe the hype

[theamk]

What are you talking about? Rust was always very clear about which features are implemented and which are not.

Not to mention their early design docs were extremely great - I remember reading them and being impressed. And when designs change, it's all there, with posts about what was changed and why.

Compare to V's autofree-without-GC debacle - I reemember reading about this and thinking "no way they can do it, they need something innovative like Rust's model and they have vague handwaving". And guess what? They could not. Some time after after they silently added third-party GC to the language - no blogpost, no announcement, you have to go to wayback machine to even know that they promised autofree without GC.

I'd say Vlang's communication style is approximately opposite compared to Rust. Don't put them next to each other.

[amedvednikov]

The code you pasted doesn't compile, so it's you who are lying.

Can you link to the promised autofree without GC?

[hitekker]

IIRC, it was intentional false advertising and deception. https://xeiaso.net/blog/vlang-update-2020-06-17/

Last I heard in 2024, the situation has not improved

https://news.ycombinator.com/item?id=39503446