4 ms·

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.

davidatbu 4y ago
If I had done the analysis in that blogpost (whose factual accuracy you corroborated) myself, I would have come to the same conclusion. Fortunately, the internet allows people to publish blogs where they share such analyses, so that effort doesn't have to be duplicated. > 0.3 pretty clearly means it's not production ready software. Despite the version 0.3 being visible, it is obvious that many more people than normal find that the wording on Github and the home page misleading (me included!). Obviously, this is a bit subjective, and I am telling you what I, personally, would have found a better signal to hone my expectations. If you're interested in why that might be, I think it's because several other software projects I've used that are pre-1.0 don't have major bugs that interfere with their primary value proposition (like in Vlang). Off the top of my head, neovim, rocket (a rust webframework), mypy, reqwest come to mind.
- amedvednikov 4y ago
  It would take you literally a couple of minutes to try it yourself and see it all works. Less time than it took you to type these messages. > If I had done the analysis in that blogpost (whose factual accuracy you corroborated) myself, I would have come to the same conclusion. No, you would not even be able to reproduce those bugs, because they have been fixed. > don't have major bugs that interfere with their primary value proposition (like in Vlang). can you list such major bugs here please?
  - davidatbu 4y ago
    > It would take you literally a couple of minutes to try it yourself and see it all works. I had previously said: "if the author of that blog post found (IMO) straightforward ways to invalidate Vlang's claims in ~1 month with the language, I suspect that I will also find _other_ ways to also invalidate Vlang's claims in a straightforward manner." Unfortunately, I don't have a month of spare time, like that blogger, to put towards that effort. > can you list such major bugs here please? It might be (though I doubt it) that the major bugs outlined in that blog post (which your community promptly fixed) happen to be the final set of such major bugs that interfere with Vlang's primary value proposition. Like I said, I'm not willing to put a month of spare time to find out. I will almost certainly check back after some time (probably more than 1 year), and hopefully by then I will have the spare time to do the inspection, or someone else will have done it. I sincerely hope that you and your community succeed in achieving your goals! Good luck!
    - amedvednikov 4y ago
      So you can't list the major bugs here. Then please don't spread the misinformation that V has "major bugs that interfere with their primary value proposition".
      - deleted 4y ago
        [deleted]

davidatbu 4y ago

If I had done the analysis in that blogpost (whose factual accuracy you corroborated) myself, I would have come to the same conclusion. Fortunately, the internet allows people to publish blogs where they share such analyses, so that effort doesn't have to be duplicated. > 0.3 pretty clearly means it's not production ready software. Despite the version 0.3 being visible, it is obvious that many more people than normal find that the wording on Github and the home page misleading (me included!). Obviously, this is a bit subjective, and I am telling you what I, personally, would have found a better signal to hone my expectations. If you're interested in why that might be, I think it's because several other software projects I've used that are pre-1.0 don't have major bugs that interfere with their primary value proposition (like in Vlang). Off the top of my head, neovim, rocket (a rust webframework), mypy, reqwest come to mind.

amedvednikov 4y ago
It would take you literally a couple of minutes to try it yourself and see it all works. Less time than it took you to type these messages. > If I had done the analysis in that blogpost (whose factual accuracy you corroborated) myself, I would have come to the same conclusion. No, you would not even be able to reproduce those bugs, because they have been fixed. > don't have major bugs that interfere with their primary value proposition (like in Vlang). can you list such major bugs here please?
- davidatbu 4y ago
  > It would take you literally a couple of minutes to try it yourself and see it all works. I had previously said: "if the author of that blog post found (IMO) straightforward ways to invalidate Vlang's claims in ~1 month with the language, I suspect that I will also find _other_ ways to also invalidate Vlang's claims in a straightforward manner." Unfortunately, I don't have a month of spare time, like that blogger, to put towards that effort. > can you list such major bugs here please? It might be (though I doubt it) that the major bugs outlined in that blog post (which your community promptly fixed) happen to be the final set of such major bugs that interfere with Vlang's primary value proposition. Like I said, I'm not willing to put a month of spare time to find out. I will almost certainly check back after some time (probably more than 1 year), and hopefully by then I will have the spare time to do the inspection, or someone else will have done it. I sincerely hope that you and your community succeed in achieving your goals! Good luck!
  - amedvednikov 4y ago
    So you can't list the major bugs here. Then please don't spread the misinformation that V has "major bugs that interfere with their primary value proposition".
    - deleted 4y ago
      [deleted]