151–160 of 336 posts
It would be very nice if you could do the same thing for Nim.
It's a great idea, I nominate myself unless anyone more qualified steps in. It should take about a month. I will do what the author did and evaluate the claims the language makes one by one.
Earlier quoted context omitted.
An article like the V one on Zig checking the claims would be awesome, wouldnt it.?
Quoted post unavailable.
I never understood the motivations behind V. It's clearly not a hobby project started out by a developer who is genuinely experimenting with PLs and want to put out something unique. It feels more like a stunt or a flair to either extort money or become famous. All that would be perfectly okay if V did what it claims to do but the author fanatically makes exciting claims but implements only fluff to hide the underlyi…
The impression should not be given that V is just a one-man show. Many of the offshoot projects are in collaboration with others, not just the author, who have invested heavily in them and also wanted or helped create them.
Earlier quoted context omitted.
I wouldn't bet a single dollar on V improving to any qualitative level. It's been a surprisingly large transpiling hack. Graydon Hoare had some PLT knowledge before going on doing Rust, it's not just feature names and potential impl.
What are the qualitative levels in your opinion? The V compiler is self hosting for example, there are useful examples done in the main repo, people are using it for writing web servers. What it should do, to "qualify", and to qualify in what?
Earlier quoted context omitted.
It's a great idea, I nominate myself unless anyone more qualified steps in. It should take about a month. I will do what the author did and evaluate the claims the language makes one by one.
Very well, be sure to ask in the IM channels when you need guidance and good luck.
What do you mean IM channels?
Earlier quoted context omitted.
Are there any other language evaluations in your blog, or a plan for any, etc? I'd like to read other reviews, but I only see this one post.
Sorry, not yet. New to blogging and this took quite a long time to complete to a level I was satisfied with so it will probably be a while before I complete another one.
I do not understand the hatred, reminds me of the last article of this kind. This language is in alpha. I've been in the Discord community since 2020 and no one would think of recommending the language for production use because it's WIP. Sure the goals are high and a lot of things don't work yet or are shaky but that's the way it is ATM. The wording of the article is simply not appropriate for the fact that the lang…
Valid criticisms of the language should arguably be more directed towards its issues on GitHub (https://github.com/vlang/v/issues), in addition to any blog or article, where the contributors and developers can address them.
When approached correctly, and not in an adversarial and combative way, I've seen the V community be very friendly and helpful.
Earlier quoted context omitted.
A lot of that post is actually me wanting to be sure that my legacy isn't one of perceived toxicity. When you are in as many minority groups as I am, then you end up becoming an unpaid existential ambassador and you need to be hyper careful to not look like an asshole or do things that could possibly make you look like an asshole because people will assume that being an asshole is a representative sample of those gro…
Hate mail? Really? Care to post an example?
1. They don't post it, and get accused of lying.
2. They post one of the tamer examples, and get accused of overreacting to nothing.
3. They post a median example, and get told that people reacting with vigour is normal and it's not about them.
4. They post a very strong example, hurting some readers and get responses claiming that you clearly can't take threats at face value.
5. They get accused of making it up, anyway.
6. They don't include personal details, so you can't do anything, anyway.
7. They include personal details and get accused of doxxing or making it personal.
There's just no good outcome from your request.
Earlier quoted context omitted.
I don't think this article contains any hatred. There is absolutely nothing wrong with an unfinished language - take a look at https://news.ycombinator.com/item?id=31775216 (2 days ago) for an example. This article criticises V for presenting itself as a usable language , when it definitely isn't, with all these features which don't work.
I don't think it is fair to criticize the language like that without having "0.2 ALPHA" in the title of the ycombinator title and the article. In fact the hole article does not contain the word "alpha" or explaining the state once. It reads like that the language is expected to be ready and that all features need to work now, but they don't. "At this time, I would not recommend spending time on V. I would also be ver…
This is why the "critic" can also be interpreted (or misinterpreted) as another attack. It's one thing if this was a blog evaluating the claims of multiple programming languages, but it being a very specific and dedicated critic of V, looks strange.
To include it uses the term "we" a lot in the summary, as if it was a collaboration effort by a group of programmers directed at V. It is unknown who are the "we" being referred to.
"We’re able to create a null pointer (V reference) with no compiler errors or warnings."
"We weren’t able to shadow local variables."
If the evaluation was in the spirit of improving the language (as it is still alpha) or pointing out things that need to be addressed, then one would expect it to be presented as various issues or bugs on V's GitHub. There would not be any blindsiding or surprise, but an exchange between the evaluator(s) and V's developers and contributors.
Parts of the evaluation and summary are debatably subjective. The categories of purity, sum types, generics, speed, and compiling are among them. So getting direct feedback from the developers and contributors of V would have been much more fair and helpful.
To be fair, they didn't claim that the values were immutable, only the variables. Isn't the example in the article basically the same as Java's final variables, i.e. immutable references to mutable values?
> No global variables [...] Evaluation: V does not prevent you from creating and mutating globally shared state in any meaningful way.
Although I agree with the evaluation, the claim of "no global variables" might still hold, assuming it refers to mutable global variables. The global constant holds an immutable reference to a mutable value, just like how in Java a singleton object (or a class with mutable static fields) can be used to simulate global variables.