amedvednikov

That's just Cocoa Calculator junk.

I tried porting Cocoa and decided not to. Will remove.

Native V Calculator uses 4 MB of RAM.

I've updated the screenshot. Here's real Minecraft running on Vinix:

https://vinix-os.org/assets/vinix-minecraft.png?2

Only one person, who said "V must die", was banned.

I've updated the screenshot. Here's real Minecraft running on Vinix:

https://vinix-os.org/assets/vinix-minecraft.png?1

Transformer, checker, markused, binary generation are not costly?

It takes GCC this much time to generate an unoptimized hello world.

It still compiles in 0.5s:

https://www.youtube.com/watch?v=vV-mzTDUpAI

10k+ bugs fixed, only ~40 open github issues.

Reworded and simplified.

That's just Cocoa Calculator junk.

I tried porting Cocoa and decided not to. Will remove.

V has always compiled itself in <1s

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

All listed features are real. Which ones are unfullfilled?

No, it wasn't Go's parser. That's easy to check.

https://github.com/vlang/ui2 does just that

Cool!

I've translated it from Rust to V in 45 minutes. Works great:

https://github.com/medvednikov/libjs_v

Compiles in 0.2 seconds on my M5 (compared to Rust's 3.3 seconds).

Can you please link to V claiming to be production ready?

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

Can you link to the promised autofree without GC?

> For me the biggest gap in programming languages is a rust like language with a garbage collector, instead of a borrow checker.

https://vlang.io

GC, sum types, result/option types, interfaces, no OOP, fast compilation.

Legit interested, what's subpar about the translation?

A lot of text, you didn't answer my simple questions though:

> Can you list any weird behavior/bugs that lead to frustration and confusion?

> And examples of the documentation being outdated/wrong?

Since you wrote

> The documentation is outdated, missing or wrong.

> using it for any real world project is an exercise in frustration and confusion

that shouldn't be hard

People that build the OS don't work on the compiler, not sure what that was about.

Such discussions are always the same. You say there are lots of issues, but can never list one. And you point to articles that complain about V using libc or that C2V was released in 2022 and not earlier. It's 2025!

Our documentation is very vast and up-to-date and we try to keep it up-to-date. So if you say it's wrong/missing/outdated, you could post a couple of examples, so that we can fix it. That shouldn't be hard for you.

As for an issue you referenced, yes a pre-1.0 language has bugs. Thousands. Like all other pre-1.0 languages being developed. We fix them quickly (~9k fixed, ~800 open)

Good point. I'll add the homebrew installation method. Maybe some other popular package managers.

V is very easy to install from source and to bootstrap. And it changes fast. So we're not big fans of package managers yet.

Hm V literally has a big discussion called

"What don't you like about V / what would you like to be changed?"

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

What exactly do you think only looks good on paper?

The network library doesn't use curl:

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

There are prebuilt packages you can install from the home page and from the github repo.

For example

https://github.com/vlang/v/releases/latest/download/v_linux....

Everything that's listed on the home page is delivered.

Can you list any weird behavior/bugs that lead to frustration and confusion?

And examples of the documentation being outdated/wrong?

We recently migrated from YAML CI to VSH as well:

https://github.com/vlang/v/blob/master/ci/linux_ci.vsh

> It's usually all your Pythons, Gos, and anything else with a GC is doing anyway.

GC langs don't do clones (copying), that's the point of the GC.

How is it compromised?