vlang1dot0

8 ms·

1.
by vlang1dot0 4y ago
It has an automated release generated every week. The could be no commit activity whatsoever and there would still be 52 "releases" of V every year. It's one thing to like V but it's another to constantly repeat misleadi
2.
by vlang1dot0 4y ago
I don't see how that really follows. V heap allocates any value which is address taken. You don't need to be an advanced C programmer to use pointers.
3.
by vlang1dot0 4y ago
They've been working on C2V for a long time now and even still it falls over quickly for anything other than the exact version of doom they are using. Multiline comments crash the tool for instance.
4.
by vlang1dot0 4y ago
You only merged it one hour ago. https://github.com/vlang/v/pull/14805 Over promising (hardly a one line patch) and under delivering (well beyond your "it will be fixed today" statement) as usual.
5.
by vlang1dot0 4y ago
Did you even bother to read what he pasted? Tcc is used in the first set of commands that do not terminate.
6.
by vlang1dot0 4y ago
How's that "one line" fix in the type checker coming? Looks like it wasn't fixed yesterday.
7.
by vlang1dot0 4y ago
Your demo includes code that uses manual memory management because of autofree bugs. https://github.com/vlang/ved/blob/9b85e6291c9fe9135db1e300de...
8.
by vlang1dot0 4y ago
Yes, technically you can do that but it makes no sense from a design point of view to have a language that cares so much about safety it adds a borrowing system but then says "fuck it" to type safety. You have to have type safety
9.
by vlang1dot0 4y ago
If the US gov decides to project its will on your software project, an ISO standard is not going to help you at all. They will sabotage the ISO process, or force your hosting provider (GitHub) to remove your project or apply changes to it,
10.
by vlang1dot0 4y ago
I see about 1k lines of new tests, probably 500-600 lines of build system integration across various files, nearly 1k lines of cargo lock file information for dev dependencies and the Rust code appears to be more highly commented than the C
11.
by vlang1dot0 4y ago
According to the article: > YJIT is a relatively simple JIT compiler that totals about 11,000 lines of C code.
12.
by vlang1dot0 4y ago
So no actual response to objective criticism just "my interpretation is things are going well so they can claim anything they want"? Wow, what a compelling argument you make! If you want to look at GitHub, sure let's do that.
13.
by vlang1dot0 4y ago
Are you arguing it's fairer to say V's default is to ignore managing memory at all?
14.
by vlang1dot0 4y ago
So, you're saying C2V is closed source then? Which is exactly what Alex said isn't true.
15.
by vlang1dot0 4y ago
Really? - No null Then what is `voidptr(0)`? - No global variables https://github.com/vlang/v/blob/master/doc/docs.md#global-va... At least add "by default" to the web site. - No undefined
16.
by vlang1dot0 4y ago
So how do you plan to make autofree work without move semantics, an ownership model or borrowing annotations? If your answer is "like Lobster", then how do you plan to deal with the semantic differences between those languages whi
17.
by vlang1dot0 4y ago
No, "it's fast because it's C" doesn't hold. You can write slow code in any language.
18.
by vlang1dot0 4y ago
Could you point to the C2V source?
19.
by vlang1dot0 4y ago
The reason V is so controversial is that it separates nearly everyone who looks at it into two diametrically opposed groups: those who have some experience or knowledge of programming language design and implementation and those who do not.
20.
by vlang1dot0 5y ago
This feels intentionally ignorant of the state of Rust considering there is more funding and more people paid to work directly on Rust than any prior point in the project's entire history.
21.
by vlang1dot0 5y ago
Rust is not governed by the Rust Foundation. Rust is governed by the Core Team and the teams under them.
22.
by vlang1dot0 5y ago
I'm pretty sure sed could have saved them the trouble.
23.
by vlang1dot0 5y ago
Budget doesn't really have anything to do with it. The vast majority of people on a team or working group aren't paid to work on Rust; they're volunteers.
24.
by vlang1dot0 5y ago
I don't see how that follows. Declarative build configuration is very good and Rust needs to lean harder in that direction and minimize the use of build.rs.
25.
by vlang1dot0 5y ago
The foundation is funding oncall support staff for crates.io which was a much more urgent need than funding more devs. Amazon, Microsoft, Huawei, Google and Futurewei are all now employing a good chunk of the devs to work on it full time.
26.
by vlang1dot0 5y ago
Not sure I'd point to C++ of all things as being free from the concerns of large corporations lol. This is just such an uninformed take.
27.
by vlang1dot0 5y ago
Yeah given the general responses from other people involved with the project, Steve seems pretty far out on a limb here.
28.
by vlang1dot0 5y ago
> V was also self hosted (written in V) from the start, which says a lot about the maturity of the language. How could that possibly be true? You need a V compiler to compile V but none would have existed "from the start". You&
29.
by vlang1dot0 5y ago
Frankly it's rather amusing.
30.
by vlang1dot0 5y ago
The languages you've listed generally work as advertised and while you might dislike some of the design decisions or tradeoffs inherent in those decisions, ultimately, they do what they claim to. The same cannot be said of V.

More ›