amedvednikov

None of the bugs in the first article are relevant today.

There were no close to impossible/missing features.

What response?

Different people are working on different open source things they like, as the result the language has real world examples.

It improves on Go a lot: https://vlang.io/compare#go

None of the claims in this article are relevant now, you can try them yourself.

Don't trust everything you read on reddit. There are no false or misleading claims, only in the articles from authors who say "V must die".

Like complaining that V depends on OpenGl, Git, libc, and electricity!

If you've been dreaming about a language like this, give it a try. Spend 20 minutes on it, and form your opinion.

I'm sure you'll like it!

That's a nice shell script! Probably enough for 90% of static sites.

You can try out V, it's similar, but is very stable for its age: https://vlang.io.

So what kind of low level stuff can you do in rust/zig that you can't in V?

You don't have to use GC in V. It has optional manual management/autofree/arena.

What kind of low level stuff can you do in rust/zig that you can't in V?

V works just fine for low level stuff, we have a full os/kernel written in V, which can already run g++ and doom.

True, Go has an amazing ecosystem. A great stdlib and libraries.

That's why we're working on Go2V, which will be able to fully translate Go code to V. (Having a language so similar to Go also helps.)

It's already been partially used in our translation of Go's crypto modules:

https://github.com/vlang/v/tree/master/vlib/crypto

GC is often faster than ownership. All the extra clones are costly.

V uses Result types for handling errors, and the developer must handle them by propagating the error or breaking/returning or panicing.

For example:

  // os.v
  fn open(path string) !File {}

  // main.v
  file := os.open('out.txt') or { panic('failed to open: $err') }
  file := os.open('out.txt') or { return }
  file := os.open('out.txt')! // propagate the error
  if file := os.open('out.txt') {} // alternative scoped syntax

Looks really cool!

Any chance you could add `git pull` support as well?

Project Oberon is amazing. Shame it isn't more popular.

You were told this by the mods of the website.

By the way, the array hack was fixed, thanks for reporting.

If you find similar bugs, don't hesitate to report them.

This is not the main site (vlang.io). Such claim was never made there. The OP mentioned that it "was on the list of 'features' for a long time".

The HN comment you referenced is from 2019. I was very anti-GC back then, that's why I didn't want to have a GC, but a model similar to Rust. After playing with GC, I realized it worked really well with V, and offered a better performance.

There's an article about these decisions on V's blog. They can change over years, you know.

If a project leader changes their mind on a technical decision over years and explains the reasons, that doesn't make them a liar.

The end goal is having good performance, flexible memory management, minimal resource usage.

> the creator of V had a clear and obvious pattern of overpromising and overhyping things early on

can you please list any examples here?

These articles have stuff like "V depends on git and electricity" and benchmarking debug builds of V with a slow backend. The author also said that V must die.

Can you please list here actual examples of under delivering and misrepresenting?

can you give any examples?

They said: "I admire your ability to maintain a rational view on this."

Really sad that comments with opposing views can be so easily removed by downvoting.

Why?

e.g. Here's DOOM running in V (translated from C). Seems pretty serious:

https://www.youtube.com/watch?v=6oXrz3oRoEg

Also, can you look at this recent 0.4 changelog with 370 items and say the language is not serious?

https://vlang.veery.cc/post/725/v-0.4-is-out

Can you please list here examples of under delivering and misrepresenting?

This "very critical review" is just a list of small bugs that were fixed a year ago.

Nothing in this article is relevant, but it still stays up, the only article in the blog.

Yes, in most cases you want to use lighter and faster coroutines.

But they are not as stable as OS thread support right now (will be much more stable in 0.4.1), and alas no Windows support yet.

Hacker news removes the space between V and 0.4 :)

Would be nice to have, but can't guarantee it at the moment.

Author of the language here.

Very excited about this release!

2160 commits pushed to master, 1205 bugs closed since V 0.3.

The changelog is huge: it has 370 items.

The highlights are coroutines with the scheduler, vweb improvements (live reloading, controllers, middleware, better multithreaded performance) and generally improved stability.

One of the main reasons I created V.

It's pretty much Go with Option/Result that forces you to handle errors:

f := os.create('foo.txt') or { println(err) return }

https://vlang.io/compare#go