Live data from Hacker News

V Is for Vaporware

christine.website

11–20 of 37 posts

Re: V Is for Vaporware

#11
post #7

Nice hit piece. All of the criticisms could have been patches. Most of the criticisms are exaggerated. Looks like it took 2s to build on the macbook instead of 1. The 'zero dependency' binary links to libc (as if most programmers wouldn't expect this.)

I agree with the sentiment of your post, but I would like to point out that it took 2 seconds for it to throw an error that the file had more than 50k statements. It did not build at all. It’s not really even a valid test.

Re: V Is for Vaporware

#12

Not sure the author understands what "Work in Progress" means. A good portion of the article seems to be taking claims marked (WIP) and saying "hah! gotcha! this doesn't work yet!" Almost like, I dunno, a work in progress.

They were only marked as WIP when people noticed they were missing.

Re: V Is for Vaporware

#14
post #7

Nice hit piece. All of the criticisms could have been patches. Most of the criticisms are exaggerated. Looks like it took 2s to build on the macbook instead of 1. The 'zero dependency' binary links to libc (as if most programmers wouldn't expect this.)

So you think a C++ translator and hot code reloader can be sent as a patch so easily? What?

Re: V Is for Vaporware

#15
post #8

I don't understand these kinds of articles at all, maybe somebody can help me. So the author has overhyped its creation. So what? Humans get attached to their creations and can't view them objectively. That's a documented psychological fact -- just look at your typical parent, their kids can do no wrong in their eyes. I tried following V's story lately on HN and truthfully, I got very surprised by the ton of hate and…

> So the author has overhyped its creation. So what?

Either: "Someone got excited, took a closer look and wrote a blog post", or "someone got mildly annoyed by the overhyping, tried it out and wrote a blog post about it". It seems to be fairly factual criticism to me, comparing the marketing claims to actual experience.

And especially because getting a language going is such a big project I don't get why you'd state things that aren't there yet - everyone would expect an early version to not have all those things if there weren't claims to the opposite, so being honest about the state of things doesn't really hurt you. To the contrary, it avoids people being disappointed when they want to try something that's claimed as a feature and it isn't there. And some probably consider it unfair towards projects that are less bold in their claims.

I'm not sure what the "harmless" comments are about - the article doesn't mention anything about that (or the income) at all?

Re: V Is for Vaporware

#16
post #2

It would be nice if people were supportive of this effort instead of just pissing on it. Of course it is incomplete at 0.0.12. Was it over hyped? Sure. Good for him to have time for some marketing of his work next to _actually writing a working compiler with a good start for a standard library_ This thing is real and here to stay. How about this: instead of writing about frauds and vapourware, contribute to the proje…

Thanks :) It's 0.0.12, the first public release. What's with all this "vaporware"? The compiler can already compile itself in 0.3 seconds and is written 100% in V: https://github.com/vlang/v#installing-v-from-source It allows building easy cross platform graphical apps: https://github.com/vlang/v/tree/master/examples/tetris It has easy cross compilation and can even compile itself for another platform: https://twitte…

If you have all these great examples, why aren't they on the marketing page instead, and future plans clearly on a roadmap or whatever? They're pretty cool achievements! And something I can now go look at is way more interesting than something thats "coming soon". Good luck with your project, I hope this drama doesn't overshadow it too much long-term (but you're probably better off if you work on your messaging to avoid this topic getting back up over and over)

Re: V Is for Vaporware

#17
post #15
post #8

I don't understand these kinds of articles at all, maybe somebody can help me. So the author has overhyped its creation. So what? Humans get attached to their creations and can't view them objectively. That's a documented psychological fact -- just look at your typical parent, their kids can do no wrong in their eyes. I tried following V's story lately on HN and truthfully, I got very surprised by the ton of hate and…

> So the author has overhyped its creation. So what? Either: "Someone got excited, took a closer look and wrote a blog post", or "someone got mildly annoyed by the overhyping, tried it out and wrote a blog post about it". It seems to be fairly factual criticism to me, comparing the marketing claims to actual experience. And especially because getting a language going is such a big project I don't get why you'd state…

> I don't get why you'd state things that aren't there yet

I interpreted it as "things I want to eventually add", and I already conceded that the author has some false claims (as the blog post points out as well).

Think of it as a roadmap / mission statement. It gives you a good idea if you want to use it when it is eventually ready. A small bit of marketing.

> I'm not sure what the "harmless" comments are about - the article doesn't mention anything about that (or the income) at all?

Zig's author has said they have been discouraged to work on their tech since they allegedly work harder and deliver more yet get less donations: https://news.ycombinator.com/item?id=20230384 (which is a child of https://news.ycombinator.com/item?id=20230351).

Several other people in this thread (and I think others if memory serves) have expressed displeasure that V's author collects donations.

That is toxic. People get donations for all sorts of stuff. Let them, and don't be bitter about it. The way the HN crowd seemed to latch onto V's author specifically was very peculiar for me to observe in the last several months.

Re: V Is for Vaporware

#18
post #15

Earlier quoted context omitted.

> So the author has overhyped its creation. So what? Either: "Someone got excited, took a closer look and wrote a blog post", or "someone got mildly annoyed by the overhyping, tried it out and wrote a blog post about it". It seems to be fairly factual criticism to me, comparing the marketing claims to actual experience. And especially because getting a language going is such a big project I don't get why you'd state…

> I don't get why you'd state things that aren't there yet I interpreted it as "things I want to eventually add", and I already conceded that the author has some false claims (as the blog post points out as well). Think of it as a roadmap / mission statement. It gives you a good idea if you want to use it when it is eventually ready. A small bit of marketing. > I'm not sure what the "harmless" comments are about - th…

I hadn't seen that thread you linked - ugly in both directions IMHO. I see why people have a problem with it, some of the comments are over the line IMHO, and it's still just someones small project, so I get why looser standards should apply. To me, the comments there are different than what I read from the article submitted here.

EDIT: large rewording, sorry!

Re: V Is for Vaporware

#19
post #18

Earlier quoted context omitted.

> I don't get why you'd state things that aren't there yet I interpreted it as "things I want to eventually add", and I already conceded that the author has some false claims (as the blog post points out as well). Think of it as a roadmap / mission statement. It gives you a good idea if you want to use it when it is eventually ready. A small bit of marketing. > I'm not sure what the "harmless" comments are about - th…

I hadn't seen that thread you linked - ugly in both directions IMHO. I see why people have a problem with it, some of the comments are over the line IMHO, and it's still just someones small project, so I get why looser standards should apply. To me, the comments there are different than what I read from the article submitted here. EDIT: large rewording, sorry!

(I see you edited out most of your comment. Still leaving some of mine in place.)

> I did not read the page as a roadmap...

I'll say again that I fail to understand what's so bad if somebody didn't say something is WIP and claimed it's ready. We're programmers and very far from helpless clueless non-technical users. We can download the thing, try it and see for ourselves.

I am asking: where's the actual, measurable, tangible harm in that?

Can't understand what's the big outrage about V. There have been multiple threads about it on HN lately and the amount of hate and bitterness by other HNers is comical and totally unexpected on this forum which I viewed in a higher regard until just recently.

EDIT: Additionally, a comment from `dang`, one of the moderators: https://news.ycombinator.com/item?id=20251393

Re: V Is for Vaporware

#20
post #18

Earlier quoted context omitted.

I hadn't seen that thread you linked - ugly in both directions IMHO. I see why people have a problem with it, some of the comments are over the line IMHO, and it's still just someones small project, so I get why looser standards should apply. To me, the comments there are different than what I read from the article submitted here. EDIT: large rewording, sorry!

(I see you edited out most of your comment. Still leaving some of mine in place.) > I did not read the page as a roadmap... I'll say again that I fail to understand what's so bad if somebody didn't say something is WIP and claimed it's ready. We're programmers and very far from helpless clueless non-technical users. We can download the thing, try it and see for ourselves. I am asking: where's the actual, measurable,…

Oops, I just had removed that section after reading the other thread a bit more.

To "where's the actual, measurable, tangible harm in that?": People's sense of what's fair or not doesn't necessarily match that perfectly. A single project being overhyped probably doesn't do much harm (although discouraging contributors to other projects, taking mindshare from them, ... probably is a minor form of harm, even if hard to quantify), but I think people dislike it because it distracts and it would be a problem if it became the norm. Again, my initial comment in this thread was without the context of other discussions and only based on the article.

Post reply on HN