Live data from Hacker News

The V Programming Language

vlang.io

251–260 of 308 posts

Re: The V Programming Language

#251
Wow, did dang really remove all the replies to his comment? Here's what it looked like a few hours ago; it was still open in my browser. https://u.teknik.io/pD724.png

Those comments were generally respectful; I saw no reason to remove them. Seems over-zealous to get rid of any disagreement with a moderator's decision.

Re: The V Programming Language

#252

Earlier quoted context omitted.

Not in general, but many open source developers do hard work and do sometimes not even get praise, so they don't like it when someone who they feel did not work so hard or not at all and just promised unrealistic things, get's the money. (not judging about that case here)

This sounds to me like that same attitude that keeps people from saying how much they make; that your coworker will get mad at you, and not your boss.

A bit, yes. Except in cases where people make money from a limited avaiable fund, by lying.

Re: The V Programming Language

#253

Earlier quoted context omitted.

This sounds to me like that same attitude that keeps people from saying how much they make; that your coworker will get mad at you, and not your boss.

A bit, yes. Except in cases where people make money from a limited avaiable fund, by lying.

"limited available fund" ah yes, the software industry really does barely manage to scrape by, good point.

Re: The V Programming Language

#254

Earlier quoted context omitted.

I can't understand criticising a brand new, v0.0.12 language built entirely by one person of being too small...

Extraordinary claims require extraordinary evidence. If the information presented on https://vlang.io/ had any hint of being aspirational as opposed to comparing it directly with existing languages, and the author had less confrontational interactions with skeptical people online, the reaction to this language would be different. Of course, without the extraordinary claims this code dump would also not receive the at…

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.

My assessment (not a language designer) is that this is something that shows some promise as a transpiled language for people who want a Go-like language without some of the common pain points and are OK with having no GC.

I would add that people who do design languages seem to think it's going to be considerably harder to deliver on the WIP elements than the designer of V thinks. In particular, I note that "direct machine code generation" is a planned item (which would be required for the faster compile time that V promises), but doesn't (as of this source code release) seem to be started - could be wrong about that. Obviously you can promise whatever you want, but writing an entire machine code compiler that will run faster than GCC and equal it in performance is a difficult 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. While I don't have a use for it myself, the designer does seem sincere about their efforts. (My "ideal" language would be something closer to a lightweight version of Rust that was simpler to use, even if it slightly ate in to what you could do with it.)

Re: The V Programming Language

#255

Earlier quoted context omitted.

I take it you've never programmed embedded? Yeah, state sucks. But sometimes, you need a starting point, and diff from that. And, that's state. One of the safe ways of handling global vars, is by having only a single non-interruptible function that can mutate global. And you have best make sure your global-mutating function is fast . You don't want to miss IRQs that might fire off but are blocked.

Yes, embedded is enough of a special case that I don’t consider it as part of a general purpose discussion on programming languages.

Ericsson predicts 18 billion IoT devices by 2022. Those all need code written for them. Do you still consider embedded programming a "niche"? Maybe it's one specific case, but it's relevant and ought to be "part of the discussion".

https://www.ericsson.com/en/mobility-report/internet-of-thin...

Re: The V Programming Language

#256

Earlier quoted context omitted.

This sounds to me like that same attitude that keeps people from saying how much they make; that your coworker will get mad at you, and not your boss.

A bit, yes. Except in cases where people make money from a limited avaiable fund, by lying.

He hasn't lied about anything.

If you do a search in these comments for people who have actually given him money, I think you'll find that none of us have done so under the pretense that all the features he listed on the website are finished.

We're also not "buying" anything. We're supporting a developer who is writing a language we would like to one day use. How else is it going to get written? Do we expect somebody to toil away in obscurity for no pay for 5+ years first?

I would consider it money well spent even if he never finishes it. I'm voting for the language I want with my wallet.

Yes, this opens me up to making me feel like a sucker if he is a scam artist. But, he's delivered things in the past and he's delivered things even since the last conversation. Most frauds don't ship.

Re: The V Programming Language

#257
post #251

Wow, did dang really remove all the replies to his comment? Here's what it looked like a few hours ago; it was still open in my browser. https://u.teknik.io/pD724.png Those comments were generally respectful; I saw no reason to remove them. Seems over-zealous to get rid of any disagreement with a moderator's decision.

No, the subthread was just detached and marked off topic. Scroll down a bit more to find it: https://news.ycombinator.com/item?id=20251706. This is a common moderator action on HN.

Re: The V Programming Language

#258
post #251

Wow, did dang really remove all the replies to his comment? Here's what it looked like a few hours ago; it was still open in my browser. https://u.teknik.io/pD724.png Those comments were generally respectful; I saw no reason to remove them. Seems over-zealous to get rid of any disagreement with a moderator's decision.

No, the subthread was just detached and marked off topic. Scroll down a bit more to find it: https://news.ycombinator.com/item?id=20251706 . This is a common moderator action on HN.

Maybe it would be better for him to amend to his comment that "further discussion on this comment has been moved to here:"

Re: The V Programming Language

#259

Earlier quoted context omitted.

Extraordinary claims require extraordinary evidence. If the information presented on https://vlang.io/ had any hint of being aspirational as opposed to comparing it directly with existing languages, and the author had less confrontational interactions with skeptical people online, the reaction to this language would be different. Of course, without the extraordinary claims this code dump would also not receive the at…

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. My assessment (not a language designer) is that this is something that shows some promise as a transpiled language for people who want a Go-like language without some of the common pain points and are OK with having no GC. I would add that pe…

Thanks!

Work on x64 generation started back in August. I'll publish it very soon. I haven't touched it in a while, and it simply doesn't compile at the moment.

Re: The V Programming Language

#260

Earlier quoted context omitted.

can you `wget https://vlang.io/v.c` again?

Okay, I did and I was able to compile the `vc` compiler from the C source. The REPL in `vc` seems to work (at least for the basic printing I tried) and running `./vc -o v .` worked as well. But the new `v` compiler segfaults with: coudlnt create file "/var/tmp/vlang0.0.12//vrepl.v" Segmentation fault (core dumped) EDIT: however, if I understand it correctly, it was not the instructions after all, that resulted in eve…

You had to do `git pull` to fix the "V" V binary :) Forgot to mention that, sorry.

It's going to be much, much more stable in the coming days.

Post reply on HN