HNHacker News
TopNewBestAskShowJobs

amedvednikov

1,578 karma · joined November 15, 2016

submissionscomments
amedvednikov··on V 0.3
It's not nonsense, read my replies below and the upcoming blog post next week. It's on a scale I've never seen before.
amedvednikov··on V 0.3
Since it seems to be important to many people here, I'll make sure valgrind reports 0 bytes :)
amedvednikov··on V 0.3
I'd agree if it was happening in a loop somewhere. And a long running web service would leak memory over time.

This doesn't happen, we have V web services running for months without leaks.

But since there were several responses with this message, I'll make sure valgrind reports 0 :)

amedvednikov··on V 0.3
Ah yes the famous glfw dependency of the V compiler. Complete scam.
amedvednikov··on V 0.3
Exactly! Thank you :)
amedvednikov··on V 0.3
Thanks, will have a look. wasm is not tested by CI unfortunately (yet).
amedvednikov··on V 0.3
You could say that. A very simplistic way to sum it up.

There's no ownership in V and it's not planned.

But it does borrow immutability, sum types, some elements of memory handling.

V is much closer to Go, about 80% close I'd say:

https://vlang.io/compare#go

amedvednikov··on V 0.3
Thank you. I got really tired of these vague accusations over the last 3 years.
amedvednikov··on V 0.3
Luckily in this case the amount of trolling goes down as the project grows :)

There are now V contributors who used to troll V back in the day.

amedvednikov··on V 0.3
Yeah he was the first to call me a scammer and claimed V had a dependency on glfw.

He was really persistent with his attacks, even received a warning from dang.

I found it really surprising, because before the release he wrote:

> Wow, that's incredibly fast. Self-hosted in 2 weeks? Hot code reloading? This is everything I plan to do with Zig, but apparently done already. How did you do it so quickly?

amedvednikov··on V 0.3
Completely not true. We welcome criticism and feedback, we even have a topic with 800 messages called "What don't you like about V / what would you like to be changed?"

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

Wishing V to die and making false accusations is not "constructive criticism".

There will be a blog post next week.

amedvednikov··on V 0.3
I don't creating an account and monitoring my comments and replying to them with attacks and trolling for 3 years is "just commenting".
amedvednikov··on V 0.3
REPL compiles each time, but we also have a WIP interpreter. That one is the real thing :) Not finished yet.

https://github.com/vlang/v/blob/master/vlib/v/eval

amedvednikov··on V 0.3
"vlang" works fine :)
amedvednikov··on V 0.3
There are coordinated efforts on discords to brigade such threads, there are entire new accounts created just to reply to each of my comments negatively (luckily just today HN banned such an account), this very post about V 0.3 was mass flagged 3 times and removed from the front page 3 times, there are articles that take a simple bug fixed by a 3 line commit, and make a huge deal out of it spending a month writing an attacking post. Who would spend a month to write an article about a type checker bug?
amedvednikov··on V 0.3
You're absolutely right!

Reporting these issues wouldn't take a month, like the article, and they'd be fixed right away, as they were after the article was published.

amedvednikov··on V 0.3
I'm sorry but this is the truth.

This is completely irrelevant. Each V program uses an extra 800 bytes.

If you look at what actual performance and low resource usage V brings to the table, you'll see it's not a problem at all.

amedvednikov··on V 0.3
Yeah, please be specific. I've received so many vague accusations like this, and never ever were any actual examples given.
amedvednikov··on V 0.3
Enjoy! The documentation also works as a tutorial, pretty much.
amedvednikov··on V 0.3
Luckily V supports inline assembly code! It's used a lot in Vinix.
amedvednikov··on V 0.3
If you look at other posts in this thread, you'll see that this review is completely irrelevant since the bugs it complained about were fixed in several 3 line commits.
amedvednikov··on V 0.3
The history is not dodgy. There was an attempt to make it so by overblown picky articles attacking a 0.1 language. I'm going to cover these next week.
amedvednikov··on V 0.3
There actually is such a conspiracy. People who wrote these articles literally wrote they wanted V to die.

I'll make a detailed post about this next week.

amedvednikov··on V 0.3
I have some guesses.

I'll publish a big blog post about this. It will debunk all these "V is a scam" articles.

Basically V appeared out of nowhere and got popular very fast. It took a lot of shortcuts: it was self hosted on release, GitHub started supporting it 1 month after the release, it had hot code reloading, fast compilation (v self is <1s [0]) and so on.

People developing other languages and their communities didn't like it, and decided to attack it.

There were 2 strategies: making completely false statements (like claiming that the V compiler has a dependency on glfw, so the no dependency claim is false, and claiming that V programs use libc, system's only official API, therefore again the no dependency claim is false) and nitpicking over bugs that are inevitable in a 0.1 language, and sometimes complaining that features explicitly marked as [wip] are not ready yet. One of the common questions I saw is "why release it if it's not ready". While that's the whole point of open source. I got lots of help from 500+ contributors and got to this point a lot faster.

Then there was also a misunderstanding with the "preview" release one week before the source code was released, and many thought V was going to be closed source. Over this week unfinished features were not marked as [wip]. They were marked so after the open source release, and now there're no [wip] features on the website. Everything listed there is working in latest V.

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

amedvednikov··on V 0.3
It has been written in V from the start (the first public release).

V doesn't free memory when building V for performance reasons.

A compiler is a perfect example of an app where freeing memory is totally fine on exit, by the OS.

Fortunately V is efficient and doesn't result in gigabytes of RAM used when compiling large bases of code (V itself is about 110k loc + 100k of vlib).

Once there are code bases that require gigabytes of RAM, we'll add an option to free it as it goes.

amedvednikov··on V 0.3
Yeah that was my idea initially when I designed the language.

I don't think any other language has them merged.

There were issues later with the 3 states (Ok, Error, none) instead of a simple binary state.

Since the `or {}` block handles the "not Ok", developers had to check whether it was an Error or a `none`, it's not pretty.

amedvednikov··on V 0.3
All of the issues there were fixed several days ago, so it's no longer relevant.

Since it was another anonymous attack, it's not going to be updated and will stay like this for years.

And the issues discussed are questionable at best. Half the article is about a type checker bug, which was a 3 line fix.

Then false claims like being able to modify array.len.

amedvednikov··on V 0.3
Thank you!

There's also Gitly, which we're launching next week.

https://github.com/vlang/gitly

amedvednikov··on V 0.3
Thanks!

To be fair, "in one hour" was updated to "over a weekend" on the home page. I just did the same in README.md.

The language has definitely grown as you can see by the size of the docs.

But it's definitely not bigger than Go, and that one has always been famous in the industry for being simple.

The best thing is that V is always going to stay small. No constant changes and new complexity (looking at you, C#).

amedvednikov··on V 0.3
800 bytes in some GC cleanup is not "actively leaking memory". It's a nothingburger.

We know it's not a big deal, we have lots of valgrind tests running on CI. And we have V web services running for months and not leaking memory.

← PreviousPage 7 of 26Next →