3 ms·
> It's worth noting that the website now has "WIP" annotations on many of the claims. I'm not sure how recently these were added as this thread is my introducti
by dom96 7y ago
> It's worth noting that the website now has "WIP" annotations on many of the claims. I'm not sure how recently these were added as this thread is my introduction to the language.
Indeed, many of these have been added just today. But even with the WIP tags many of these claims still seem false, for example, the author asserts that "V compiles ≈1.2 million lines of code per second per CPU core." but below that notes that "direct machine code generation" is still a work in progress. For this particular case it sounds a lot like the author wrote a very bare bones code generator that was over-optimized for that benchmark to produce these numbers.
And indeed, as you mention, writing a machine code compiler is no easy task.
> The goals of the project remind me a lot of Nim, and I'd have preferred to see a comparison with it rather than Rust.
It reminds me a lot of Nim as well. As a core dev of Nim I find the hype surrounding it very interesting (and perhaps a little disheartening).
For what it's worth, there used to be a comparison, and in fact we discussed it in our forum[1]. Sadly it didn't seem particularly fair and it seems that V's author has decided to remove it after our debunking.
1 - https://forum.nim-lang.org/t/4758 https://forum.nim-lang.org/t/4758
- reikonomusha 7y agoI read in one of the issues that he compiled some thousands of calls to print, one per line, and that was the benchmark.
- amedvednikov 7y ago> Indeed, many of these have been added just today. 2 days ago, but yes, very recently. Something I should have done from the start. > Sadly it didn't seem particularly fair and it seems that V's author has decided to remove it after our debunking. Araq's rude response didn't debunk anything. All points still stand. I removed the comparison because it's useless, and only encourages flame wars.