Hacker News Reader

Comment by kaba0 | Hacker News Reader

How about refuting the memory leaks claim? Or the others in previous posts as well, that were calling out impossible features of the lang (that sounded like some ad)

Nitpicking nitpicks is still nitpicking.

View on HN

A memory leak that even the author admits is one line of code fix away? (free() on a global const)

See the YouTube demo I posted which shows how V removes 100% of leaks in a complex graphical application (text editor).

Well, I will believe it when I see it, as well as the other hard to believe claims like I don’t know how many lines of code/second compilation speed, perfect C-to-V compiler, etc. I’m not sure how many of it is still up on the website, because some were called out and were taken down.

Why won't you see it? It's public:

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

You can also download it and try it yourself.

As for compilation speed, here's V compiling itself in 0.2 seconds:

https://pbs.twimg.com/media/EoAx9fsWMAE2M4U?format=jpg&name=...

The nearly 1 second compilation is impressive, but why claim it has 0.2 second compile time when using a cache? It doesn’t represent the real-world time it would take to compile v or another program from fresh in order to install it.

I often compile projects before the cache expires...

-usecache here means that vlib is cached. It will be the default in 0.2.1.

The entire V compiler is built from scratch.

All memory leaks in C are one line of code away as well (calling free() in some place).

Reply on news.ycombinator.com