6 ms·

It's not a dupe. This submission was falsely mass reported and removed from the front page within minutes. After emailing HN mods, the flags were removed 18 ho

It's not a dupe. This submission was falsely mass reported and removed from the front page within minutes. After emailing HN mods, the flags were removed 18 hours later, but it was gone of course. I've asked HN mods for a permission to re-submit this.

rvz 4y ago
I find it funny that as soon as you [0] asked someone to list these major bugs in V especially when it turned out that they haven't used the language, they begin to continue their regular deflection and dodging of the question. It is a pattern I keep seeing here on HN, but its great that V hasn't given up and it is still active and maintained. No idea why this post was flagged. [0] https://news.ycombinator.com/item?id=31943383 https://news.ycombinator.com/item?id=31943383
- forgotpwd16 4y ago
  Wanna know something funnier also posted in previous thread? The hello_world.v has potential memory leaks. I tried it myself and got a similar result. Somehow the creator cannot reproduce this. ==57519== LEAK SUMMARY: ==57519== definitely lost: 0 bytes in 0 blocks ==57519== indirectly lost: 0 bytes in 0 blocks ==57519== possibly lost: 816 bytes in 3 blocks ==57519== still reachable: 0 bytes in 0 blocks ==57519== suppressed: 0 bytes in 0 blocks [1]: https://news.ycombinator.com/item?id=31931083 https://news.ycombinator.com/item?id=31931083 edit: Got something even better. $ valgrind --leak-check=yes v examples/hello_world.v ... ==58037== LEAK SUMMARY: ==58037== definitely lost: 4,463,772 bytes in 106,561 blocks ==58037== indirectly lost: 5,275,772 bytes in 84,005 blocks ==58037== possibly lost: 0 bytes in 0 blocks ==58037== still reachable: 47,149 bytes in 263 blocks ==58037== suppressed: 0 bytes in 0 blocks ...
  - judge2020 4y ago
    Reproduces on GitHub Actions: https://github.com/judge2020/test-v/runs/7150691976?check_suite_focus=true#step:4:11 https://github.com/judge2020/test-v/runs/7150691976?check_su...
    - amedvednikov 4y ago
      Like I thought, this is some minor GC overhead. Wouldn't be there with `v -gc none hello_world.v`.
  - amedvednikov 4y ago
    You can stop spamming this nothingburger. 816 bytes is probably due to some GC overhead. It's nothing.
    - forgotpwd16 4y ago
      "Probably" doesn't cut it if someone is going to user your language. Let's agree that this isn't a serious matter though. The compiler leaking is nothing as well?
      - amedvednikov 4y ago
        It's not probably anymore, you're too late. See the message below. And no, 800 bytes is not a serious matter.
        mihaigalos 4y ago
        I do think V is amazing and has a bright future. Thank you for putting time in it. If I may, I still believe even 1 byte is a serious matter imho.
        amedvednikov 4y ago
        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 :)
        gompertz 4y ago
        Ahhh, if only Electron or Chrome shared that sentiment =)
        mihaigalos 4y ago
        Electron or Chrome are not the topic of this thread. I also don't appreciate whataboutism, sorry.
  - mayama 4y ago
    I checked with valgrind too and see similar memory leaks. Is v compiler written in vlang yet? I see lot of warnings and leaks for the compiler.
    - amedvednikov 4y ago
      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 4y ago
  Yeah it's a common pattern :)
hunterb123 4y ago
Interesting to note that this thread was also flagged (now restored) within 40 minutes of it being posted.
- amedvednikov 4y ago
  Yeah it's happened 4 times in total now.
  - bragr 4y ago
    You do not engage with criticism in good faith. This is a reoccurring problem in all your threads. This is why you get down voted and flagged. It's not a conspiracy against V, it is your own behavior.
    - hunterb123 4y ago
      You may want to be specific, all criticisms were addressed by the author in this thread. Also, this thread was flagged before any criticism was posted btw. You'd think those people that wanted their criticisms addressed in good faith wouldn't flag a new release that solves their criticisms.
    - amedvednikov 4y ago
      Yeah, please be specific. I've received so many vague accusations like this, and never ever were any actual examples given.
      - bragr 4y ago
        Unsupported ad hominem against the person and technical assertions without any evidence: https://news.ycombinator.com/item?id=31946432 https://news.ycombinator.com/item?id=31946432 Unsupported conspiratorial assertions: https://news.ycombinator.com/item?id=31946840 https://news.ycombinator.com/item?id=31946840 You know what the common thread in all the problems and issues you identify in this post? You communicating poorly: https://news.ycombinator.com/item?id=31946635 https://news.ycombinator.com/item?id=31946635 This is not a constructive way to engage with someone, even if they are spamming: https://news.ycombinator.com/item?id=31945932 https://news.ycombinator.com/item?id=31945932 I'm not even sure what to say about thread, you got all hostile on someone who was basically on your side because the blogs post you hate made him think something that you yourself agree with which that V is not production ready? This person might have come back to check out your 1.0, but I doubt they will now! https://news.ycombinator.com/item?id=31930435 https://news.ycombinator.com/item?id=31930435 And just the level of cognitive dissidence here. Why are you mad about someone calling your 0.3 not production ready software immature? It's interesting how you can call the language immature without even trying it. 0.3 pretty clearly means it's not production ready software. I'm not even that far back in your comment history. That's all the free emotional labor I'm willing to do for you today. Edit: Also I don't want to be the tone police, but I stepped past a lot of comments that seemed to run afoul of the "it's not what you said it's the way you said it" rule. My last piece of advice would be to read through your comments and ask yourself if the tone of them is best for achieving your (I presume) goal of promoting V.

rvz 4y ago

I find it funny that as soon as you [0] asked someone to list these major bugs in V especially when it turned out that they haven't used the language, they begin to continue their regular deflection and dodging of the question. It is a pattern I keep seeing here on HN, but its great that V hasn't given up and it is still active and maintained. No idea why this post was flagged. [0] https://news.ycombinator.com/item?id=31943383 https://news.ycombinator.com/item?id=31943383

forgotpwd16 4y ago
Wanna know something funnier also posted in previous thread? The hello_world.v has potential memory leaks. I tried it myself and got a similar result. Somehow the creator cannot reproduce this. ==57519== LEAK SUMMARY: ==57519== definitely lost: 0 bytes in 0 blocks ==57519== indirectly lost: 0 bytes in 0 blocks ==57519== possibly lost: 816 bytes in 3 blocks ==57519== still reachable: 0 bytes in 0 blocks ==57519== suppressed: 0 bytes in 0 blocks [1]: https://news.ycombinator.com/item?id=31931083 https://news.ycombinator.com/item?id=31931083 edit: Got something even better. $ valgrind --leak-check=yes v examples/hello_world.v ... ==58037== LEAK SUMMARY: ==58037== definitely lost: 4,463,772 bytes in 106,561 blocks ==58037== indirectly lost: 5,275,772 bytes in 84,005 blocks ==58037== possibly lost: 0 bytes in 0 blocks ==58037== still reachable: 47,149 bytes in 263 blocks ==58037== suppressed: 0 bytes in 0 blocks ...
- judge2020 4y ago
  Reproduces on GitHub Actions: https://github.com/judge2020/test-v/runs/7150691976?check_suite_focus=true#step:4:11 https://github.com/judge2020/test-v/runs/7150691976?check_su...
  - amedvednikov 4y ago
    Like I thought, this is some minor GC overhead. Wouldn't be there with `v -gc none hello_world.v`.
- amedvednikov 4y ago
  You can stop spamming this nothingburger. 816 bytes is probably due to some GC overhead. It's nothing.
  - forgotpwd16 4y ago
    "Probably" doesn't cut it if someone is going to user your language. Let's agree that this isn't a serious matter though. The compiler leaking is nothing as well?
    - amedvednikov 4y ago
      It's not probably anymore, you're too late. See the message below. And no, 800 bytes is not a serious matter.
      - mihaigalos 4y ago
        I do think V is amazing and has a bright future. Thank you for putting time in it. If I may, I still believe even 1 byte is a serious matter imho.
        amedvednikov 4y ago
        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 :)
        gompertz 4y ago
        Ahhh, if only Electron or Chrome shared that sentiment =)
        mihaigalos 4y ago
        Electron or Chrome are not the topic of this thread. I also don't appreciate whataboutism, sorry.
- mayama 4y ago
  I checked with valgrind too and see similar memory leaks. Is v compiler written in vlang yet? I see lot of warnings and leaks for the compiler.
  - amedvednikov 4y ago
    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 4y ago
Yeah it's a common pattern :)

hunterb123 4y ago

Interesting to note that this thread was also flagged (now restored) within 40 minutes of it being posted.

amedvednikov 4y ago
Yeah it's happened 4 times in total now.
- bragr 4y ago
  You do not engage with criticism in good faith. This is a reoccurring problem in all your threads. This is why you get down voted and flagged. It's not a conspiracy against V, it is your own behavior.
  - hunterb123 4y ago
    You may want to be specific, all criticisms were addressed by the author in this thread. Also, this thread was flagged before any criticism was posted btw. You'd think those people that wanted their criticisms addressed in good faith wouldn't flag a new release that solves their criticisms.
  - amedvednikov 4y ago
    Yeah, please be specific. I've received so many vague accusations like this, and never ever were any actual examples given.
    - bragr 4y ago
      Unsupported ad hominem against the person and technical assertions without any evidence: https://news.ycombinator.com/item?id=31946432 https://news.ycombinator.com/item?id=31946432 Unsupported conspiratorial assertions: https://news.ycombinator.com/item?id=31946840 https://news.ycombinator.com/item?id=31946840 You know what the common thread in all the problems and issues you identify in this post? You communicating poorly: https://news.ycombinator.com/item?id=31946635 https://news.ycombinator.com/item?id=31946635 This is not a constructive way to engage with someone, even if they are spamming: https://news.ycombinator.com/item?id=31945932 https://news.ycombinator.com/item?id=31945932 I'm not even sure what to say about thread, you got all hostile on someone who was basically on your side because the blogs post you hate made him think something that you yourself agree with which that V is not production ready? This person might have come back to check out your 1.0, but I doubt they will now! https://news.ycombinator.com/item?id=31930435 https://news.ycombinator.com/item?id=31930435 And just the level of cognitive dissidence here. Why are you mad about someone calling your 0.3 not production ready software immature? It's interesting how you can call the language immature without even trying it. 0.3 pretty clearly means it's not production ready software. I'm not even that far back in your comment history. That's all the free emotional labor I'm willing to do for you today. Edit: Also I don't want to be the tone police, but I stepped past a lot of comments that seemed to run afoul of the "it's not what you said it's the way you said it" rule. My last piece of advice would be to read through your comments and ask yourself if the tone of them is best for achieving your (I presume) goal of promoting V.