5 ms·
Can you please list here examples of under delivering and misrepresenting?
by amedvednikov 3y ago
Can you please list here examples of under delivering and misrepresenting?
- bheadmaster 3y ago[flagged]
- amedvednikov 3y ago[flagged]
- super_flanker 3y ago[flagged]
- amedvednikov 3y agoThis is not the main site (vlang.io). Such claim was never made there. The OP mentioned that it "was on the list of 'features' for a long time". The HN comment you referenced is from 2019. I was very anti-GC back then, that's why I didn't want to have a GC, but a model similar to Rust. After playing with GC, I realized it worked really well with V, and offered a better performance. There's an article about these decisions on V's blog. They can change over years, you know. If a project leader changes their mind on a technical decision over years and explains the reasons, that doesn't make them a liar. The end goal is having good performance, flexible memory management, minimal resource usage.
- bheadmaster 3y ago[flagged]
- mbStavola 3y agoAs you're well aware, there were a series of articles written about this[0][1] which were popular on HN a few years back. This is well documented, reproducible, and done in good faith. Now, I just want to make it clear that my exact wording here was "people were rightfully critical of V" and not "people are rightfully critical of V" (emphasis added). My intent is not to malign the current state of V, because 1) I do not keep up with the language and 2) it isn't relevant to the point being made. The parent comment was drawing a comparison between "other languages" (which, by now, it's apparent that they're speaking primarily about V) and Val when it comes to HN's reaction. If we're going to compare, it only makes sense to compare them at similar stages of development / release. So, in this case we're talking about early release V and what was promised versus delivered. It does not matter what is being done in service of users now because the criticism I'm referring to isn't from now, but when the initial HN impressions of V were formed. [0]: https://xeiaso.net/blog/v-vaporware-2019-06-23 https://xeiaso.net/blog/v-vaporware-2019-06-23 [1]: https://xeiaso.net/blog/vlang-update-2020-06-17 https://xeiaso.net/blog/vlang-update-2020-06-17
- amedvednikov 3y agoThese articles have stuff like "V depends on git and electricity" and benchmarking debug builds of V with a slow backend. The author also said that V must die. Can you please list here actual examples of under delivering and misrepresenting?
- Tozen 3y ago[flagged]
- super_flanker 3y ago[flagged]
- Tozen 3y ago[flagged]
- dang 3y agoYou have a history of posting flamewar comments to HN about this topic. If you do it again, we will ban you. I'm not going to ban you right now, because you haven't been posting exclusively about it - but these flamewars are unacceptable. No more of this please. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- dang 3y agoYou have a history of posting flamewar comments to HN about this topic. If you do it again, we will ban you. I'm not going to ban you right now, because you haven't been posting exclusively about it - but these flamewars are unacceptable. No more of this please. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- dang 3y agoPlease don't take HN threads further into flamewar on this topic. It's extremely tedious, it's happened dozens of times already, and we don't need any more of this. I'm sure your programming language is just fine. What's far from fine are these flamewars. Everybody, on all sides of this, needs to stop doing it on HN. Other forums are fine with flamewars; please conduct them there instead. It's not what this site is for, and destroys what it is for. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html