Live data from Hacker News

Hello V-Lang

blog.hackersreboot.tech

111–120 of 193 posts

Re: Hello V-Lang

#111
post #23

Earlier quoted context omitted.

Have seen Linus giving the finger to Nvidia, but not ranting on a forum about a new language.

Here you go: http://harmful.cat-v.org/software/c++/linus

This website boils my blood every time it comes up - like look at their considered harmful list, it is seriously ridiculous.

Re: Hello V-Lang

#112
post #27

Earlier quoted context omitted.

i'm pretty sure that half of these features don't work. Such as the famous "autofree" where everyone doubted it could work and the solution now was.... to drop in boehm-gc. for anyone unfamiliar with v, take everything on that list with a giant spoon full of salt.

I assumed that there was a English language barrier from the original author that made the mistake of present versus future tense for the feature list. When combined with a lack of feature tracking that looked to people like big claims were made without substance, but to me it always felt like everything in V was "work in progress." They definitely have a hacker mindset to get the minimum working examples through and…

I've never been able to quite understand what was going on with V (and the associated messenger client Volt written in it), but it seems to be something a bit more complicated than just a language barrier. I made a habit of checking the Volt website for a while out of interest in using the project, and it was somewhat surreal how fast the documented timeline would change. There was a super specific timeline in terms of what month features would land out as far as 2-3 years (e.g. "support for $os in $current_year + 2, open source in $current_year + 3), and but then as the months went by, the items on the timeline would not land, and the timeline would get revised pushing things out with no announcement of any sort. The platforms that were supported seemed to be constantly changing; one month there would be a Windows binary with Mac and Linux listed as "coming soon", and then the next month, there would be a Mac one but the Windows one was gone with no explanation. Charitably, I think the developer had fairly unrealistic expectations for how future work would progress and probably a lack of focus on following the plan they had publicly stated. I don't _think_ there was any malicious intent, but ultimately I felt like I wouldn't be able to trust that the products would be reliable if/when they did end up releasing and lost interest in following the timeline.

Re: Hello V-Lang

#113
post #24

Last time I checked V-Lang looked amazing on paper but on closer evaluation many of the claimed features were only planned, crashed the compiler on trivial inputs, or simply were half-baked and didn't deliver on the promises (things like syntax errors from the underlying C backend, memory leaks etc. because transpilation was straightforward and lacked proper checks, hence the fast compilation speed). A few months ago…

> citing V -> C translation only, without the C -> binary part Not really, here's a benchmark of V compiling itself in 0.3 seconds that includes all steps (including the C -> binary part) and results in the compiler binary: https://www.youtube.com/watch?v=pvP6wmcl_Sc This video is linked on the home page. > crashed the compiler on trivial inputs We have thousands of tests, lots of big projects written in V (V itself…

Could you explain clearly what is the memory model of the language? Because I haven’t seen it anywhere outside of the ridiculous old claims.

Re: Hello V-Lang

#114

Earlier quoted context omitted.

FWIW bro I enjoy that you are building something so ambitious and making progress despite the unwarranted hate. I have no idea why you bring out so many visceral trolls. Can someone share why this guy and vlang are so hated? It seems like he is ironing out the kinks even years after the hate keeps piling on. He keeps this up he's going to win.

It's a communication problem. Looking at the homepage and the projects it feels like everything is ready and, if the claims were true, it would be the most ground breaking language of the last decades. When you go to look at the code or try to run something you find out: - some things are still closed source - some are broken - some are wins from C It's a great strategy for collecting a check from VCs and I wish the…

No things are closed source. Never have been.

What things are broken for you?

What claims are not true?

Re: Hello V-Lang

#115

Earlier quoted context omitted.

V is also written to be as simple as possible :) Compilation time is very important during development for the quick dev cycle (change, build, test). You don't need to do -O2 builds dozens of times per day. -prod (-O2) builds are definitely an order of magnitude slower, that's a fact.

What is the performance delta between debug and prod? What is the performance delta between tcc and GCC -O0 if you’ve had a chance to compare? I also disagree with others that using a different compiler is somehow cheating. Engineering is about winning and choosing the right tradeoffs. Being able to choose a faster backend for debug is one that all compilers offer. Most people spend most of the time living with -O0 b…

No difference between tcc and gcc -O0, despite tcc compiling it 10 times faster.

20%-100% difference between gcc -O0 and -O2.

Re: Hello V-Lang

#116

Earlier quoted context omitted.

I don't think it's correct making claims like "it's a toy language" and "crashes on trivial input" without actually trying it out. You don't need an article to clone the repo, build the language in Autofree works: https://www.youtube.com/watch?v=gmB8ea8uLsM But it's not finished yet. We saw a better performance with a GC (due to all the extra copying autofree has to do), and made it the default. I've always been anti…

Is all the extra copying that autofree has to do related to the lack of move semantics in the language? Nim had to introduce a bunch of new language constructs/semantics to support their ORC backend, which is the solution that’s similar to yours. (See https://nim-lang.org/docs/destructors.html .) I expected V to move in the same direction but hadn’t found any discussion of move semantics in the docs so I found it str…

V will never have move semantics. Complicates the language too much.

Re: Hello V-Lang

#117

Earlier quoted context omitted.

Can you list the hyperbolic claims here please?

Well, for a start there's the "Translating DOOM from C to V and building it in 0.7 seconds" which is still on your front page. In spite of being a 'WIP' for as long as I can remember. Then there's; vweb, vorum, volt and ved [all of which feature prominently on the front page too] which have been little more than alpha quality proofs of concept for a similarly long time. Don't get me wrong; I was actually interested i…

vweb, volt, and ved are not a "little more than alpha"

yes, the os is being developed in V, and it can already run bash, GCC, G++, and Doom.

https://github.com/vlang/vinix

the person working on it, is an osdev, and not a compiler developer

Re: Hello V-Lang

#118
post #95

Earlier quoted context omitted.

FWIW bro I enjoy that you are building something so ambitious and making progress despite the unwarranted hate. I have no idea why you bring out so many visceral trolls. Can someone share why this guy and vlang are so hated? It seems like he is ironing out the kinks even years after the hate keeps piling on. He keeps this up he's going to win.

I applaud Alexander's efforts, but the hate is somewhat warranted, because they make misleading claims such as having "innovative memory management" when in fact they merely use Boehm GC. All the hate could be entirely avoided if their "marketing material" was a little more honest and humble.

no, we don't "merely use Boehm GC"

Re: Hello V-Lang

#119
post #97

Earlier quoted context omitted.

> sets high goals The problem is that in the initial releases the " high goals " were listed as " features " of the language, not as planed improvements of the initial implementation. So even now when I read a list like in the article, I'm not sure which are already implemented and which are just wishes, but after the initial bad impression I'm not bother to check.

Problem? Is the communication not up to the author? And shouldn't people rather help out than just make demands on an open source project?

I don't have time to help every single open source project that makes bold claims. I also don't demand anything, I just moved V to my ignored list. It may be unfair, and I may take a look in a few years again if there are enough solid news about V floating around.

Re: Hello V-Lang

#120
post #27

Earlier quoted context omitted.

i'm pretty sure that half of these features don't work. Such as the famous "autofree" where everyone doubted it could work and the solution now was.... to drop in boehm-gc. for anyone unfamiliar with v, take everything on that list with a giant spoon full of salt.

The solution V seems to apply here is a bit more nuanced than that. They’re going in roughly the similar direction as Nim did with the new ORC, which is essentially keeping the GC but try to do some compiler analysis to insert free() calls at compile time as much as it can using scope-based memory management and move semantics. The confusing thing about V is that these design decisions aren’t written properly on the…

> keeping the GC but try to do some compiler analysis to insert free() calls at compile time as much as it can

This is correct.

> Also, the choice of Boehm GC is a little bit disappointing

Which one would you recommend?

> Almost all claims of the usability/stability of the language seems to come from the main creator himself

The creators of Vinix and vsql don't have any issues with the usability/stability.

Post reply on HN