4 ms·

It might be better now, but these posts from a few years ago painted a very different picture: https://xeiaso.net/blog/v-vaporware-2019-06-23 https://xeiaso.ne

It might be better now, but these posts from a few years ago painted a very different picture: https://xeiaso.net/blog/v-vaporware-2019-06-23 https://xeiaso.net/blog/v-vaporware-2019-06-23 https://xeiaso.net/blog/v-vvork-in-progress-2020-01-03 https://xeiaso.net/blog/v-vvork-in-progress-2020-01-03 https://xeiaso.net/blog/vlang-update-2020-06-17 https://xeiaso.net/blog/vlang-update-2020-06-17 They were doing very level-headed reviews of the language at that time, found that the claims were mostly unsubstantiated, and then got blocked by the V team. That did not inspire confidence at all, as you might imagine. I can completely understand OP when they are saying "V promised a lot of stuff as ready but has undelivered most of them and people lost trust." -- that was my view too. ----- Again, it might be better now. The V team might have delivered in the meantime. But I can definitely see where OP is coming from.

Tozen 4y ago
- suprfnk 4y ago
  I am not a "sleeper account". I posted a very calm and charitable take on my view, in it explaining that I understand OP's view. Nowhere did I smear the language, or troll, or do anything of the sort. You on the other hand immediately label me as a sleeper account and a troll, for only mentioning a few links to a webpage. Although I can understand being defensive by default if you get trolled a lot, I don't think this is a good way to win people over. It certainly is off-putting to me. ----- But anyway, content related: did Xe/Xena/Christine lie in their blog posts at that time? I've read other blog posts by them and those generally seem to be level headed, well written blog posts -- not spam or anything. Next to checking out the Vlang's website, those blog posts were my only exposure to the language at the time -- as you can imagine for a new language. ----- >> ...and then got blocked by the V team. > This appears to be more trolling, and just distortions or lies, as a setup to unload more spam links and misinformation. Is the image in the tweet in the last post not correct? That Xe got blocked by @v_language? Or is that not the official Twitter account? You have to remember, I'm just an outside observer -- and all I see is a person testing the claims a language does, finding they are mostly unsubstantiated, and getting blocked in the process.
  - Tozen 4y ago
    - suprfnk 4y ago
      Haha, alright man. Still with the alt/sleeper account. Cool. I'm just some guy from the Netherlands trying to get a calm conversation going. I don't feel like any of my posts have been in any way inflammatory. You seem way too defensive to have any useful conversation with, so I won't bother any more. Good luck with vlang!
      - 10241024 4y ago
        To give you some background on why your original post might've been considered inflammatory - the author of the blog you shared has openly said "V is something that should be ignored until it dies into obscurity": https://news.ycombinator.com/item?id=27442724 https://news.ycombinator.com/item?id=27442724 I wouldn't call the author an objective reviewer of the language. Also even in this thread there were people spreading lies about the language: https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544576 https://news.ycombinator.com/item?id=33544576 who have a history of spreading lies about V that goes back years: https://news.ycombinator.com/item?id=20765490 https://news.ycombinator.com/item?id=20765490 My advice is - check out the language and make up your own mind. In the end this is a tool, not a football club.
        suprfnk 4y ago
        Hey, thanks for the civil response! > the author of the blog you shared has openly said "V is something that should be ignored until it dies into obscurity": I didn't know this -- that's very harsh, and I don't agree at all. I see that that comment was made after the reviewing blog posts, however. I can get that the relation between V and them has soured. > Also even in this thread there were people spreading lies about the language: https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544205 That's the one I initially replied to, sharing my view as an outside observer. It would probably serve V well to handle such popular blog posts in some way. Like put up a blog post refuting the points in the article, and then link to that or something. Something to undo the damage to the language's image by those posts, and (re-)inspire confidence. The other way is probably to be "so good they can't ignore you". That would be great, always good to have more great tools. > My advice is - check out the language and make up your own mind. In the end this is a tool, not a football club. I completely agree -- and people should try it for themselves. I guess my point is mostly that if the community's exposure to a language is those blog posts, they won't be inclined to try it. And if those blog posts don't get handled in a graceful and confidence inspiring way, the community won't "update" its view of the language.
- skitter 4y ago
  Things might be better now, but the previous false advertisement makes it really hard to tell. For example, vlang.io claims no undefined behaviour¹, but with struct Foo { bar int } println(&Foo(voidptr(some_address_here))) it seems to read whatever memory is at that address (which is UB in C, and V compiles to C, so...). ¹it says some overflowing can still result in UB, but that's not what's happening here; also this warning was only added in July.

Tozen 4y ago

suprfnk 4y ago
I am not a "sleeper account". I posted a very calm and charitable take on my view, in it explaining that I understand OP's view. Nowhere did I smear the language, or troll, or do anything of the sort. You on the other hand immediately label me as a sleeper account and a troll, for only mentioning a few links to a webpage. Although I can understand being defensive by default if you get trolled a lot, I don't think this is a good way to win people over. It certainly is off-putting to me. ----- But anyway, content related: did Xe/Xena/Christine lie in their blog posts at that time? I've read other blog posts by them and those generally seem to be level headed, well written blog posts -- not spam or anything. Next to checking out the Vlang's website, those blog posts were my only exposure to the language at the time -- as you can imagine for a new language. ----- >> ...and then got blocked by the V team. > This appears to be more trolling, and just distortions or lies, as a setup to unload more spam links and misinformation. Is the image in the tweet in the last post not correct? That Xe got blocked by @v_language? Or is that not the official Twitter account? You have to remember, I'm just an outside observer -- and all I see is a person testing the claims a language does, finding they are mostly unsubstantiated, and getting blocked in the process.
- Tozen 4y ago
  - suprfnk 4y ago
    Haha, alright man. Still with the alt/sleeper account. Cool. I'm just some guy from the Netherlands trying to get a calm conversation going. I don't feel like any of my posts have been in any way inflammatory. You seem way too defensive to have any useful conversation with, so I won't bother any more. Good luck with vlang!
    - 10241024 4y ago
      To give you some background on why your original post might've been considered inflammatory - the author of the blog you shared has openly said "V is something that should be ignored until it dies into obscurity": https://news.ycombinator.com/item?id=27442724 https://news.ycombinator.com/item?id=27442724 I wouldn't call the author an objective reviewer of the language. Also even in this thread there were people spreading lies about the language: https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544576 https://news.ycombinator.com/item?id=33544576 who have a history of spreading lies about V that goes back years: https://news.ycombinator.com/item?id=20765490 https://news.ycombinator.com/item?id=20765490 My advice is - check out the language and make up your own mind. In the end this is a tool, not a football club.
      - suprfnk 4y ago
        Hey, thanks for the civil response! > the author of the blog you shared has openly said "V is something that should be ignored until it dies into obscurity": I didn't know this -- that's very harsh, and I don't agree at all. I see that that comment was made after the reviewing blog posts, however. I can get that the relation between V and them has soured. > Also even in this thread there were people spreading lies about the language: https://news.ycombinator.com/item?id=33544205 https://news.ycombinator.com/item?id=33544205 That's the one I initially replied to, sharing my view as an outside observer. It would probably serve V well to handle such popular blog posts in some way. Like put up a blog post refuting the points in the article, and then link to that or something. Something to undo the damage to the language's image by those posts, and (re-)inspire confidence. The other way is probably to be "so good they can't ignore you". That would be great, always good to have more great tools. > My advice is - check out the language and make up your own mind. In the end this is a tool, not a football club. I completely agree -- and people should try it for themselves. I guess my point is mostly that if the community's exposure to a language is those blog posts, they won't be inclined to try it. And if those blog posts don't get handled in a graceful and confidence inspiring way, the community won't "update" its view of the language.
skitter 4y ago
Things might be better now, but the previous false advertisement makes it really hard to tell. For example, vlang.io claims no undefined behaviour¹, but with struct Foo { bar int } println(&Foo(voidptr(some_address_here))) it seems to read whatever memory is at that address (which is UB in C, and V compiles to C, so...). ¹it says some overflowing can still result in UB, but that's not what's happening here; also this warning was only added in July.