Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
amedvednikov
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
amedvednikov
3y ago
And 1 year later in June 2021 the author stated that V should die.
62.
▲
by
amedvednikov
3y ago
You still haven't listed any impossible claims, only something about autofree and GC copied from the website. What's impossible about that?
63.
▲
by
amedvednikov
3y ago
I agree with Tozen's sibling comment. He's not the one who starts these pointless flamewars. It's the people bringing up these 4 year old debunked "V is scam/vaporware" points in each submission about a V relea
64.
▲
by
amedvednikov
3y ago
> Which explicitly implies that objects are exclusively freed only by autofree and reference counting. Yes, and what's wrong with that? That's how it works now too, except RC has been replaced by a tracing GC.
65.
▲
by
amedvednikov
3y ago
There's no pretending, see my reply to you above.
66.
▲
by
amedvednikov
3y ago
And again, everything written is correct. No heavy GC tracing everything or expensive RC for each object. What's your issue with the wording?
67.
▲
by
amedvednikov
3y ago
The homepage makes it clear autofree is not ready yet and recommends 3 other ways to manage memory until it is. You create an account to post the same message in all V posts. Why? :)
68.
▲
by
amedvednikov
3y ago
You pointed to an old version of the documentation. RC was changed to tracing GC. Things can change in the design. V never promised autofree without GC or RC.
69.
▲
by
amedvednikov
3y ago
autofree is marked as not ready on the website
70.
▲
by
amedvednikov
3y ago
In this comment the author says V is a scam, and should be ignored until it dies. The position is clear. It's hardly unbiased.
71.
▲
by
amedvednikov
3y ago
You maybe failed to find it, yet it exists: https://news.ycombinator.com/item?id=27442724
72.
▲
by
amedvednikov
3y ago
370 items!
73.
▲
by
amedvednikov
3y ago
You're spamming this thread and with your anti V attacks, have a bunch of them downvoted and flagged, and are teaching me about communication... So rude indeed.
74.
▲
by
amedvednikov
3y ago
And what's wrong with the first part of the comment?
75.
▲
by
amedvednikov
3y ago
The author said "V must die" in an HN comment here long after posting the articles.
76.
▲
by
amedvednikov
3y ago
Currently. Previously there were features like C to V translation unmarked as WIP. WIP marks were quickly added, and gradually all features were implemented, and those marks were removed. Current contents of the website has been proof read
77.
▲
by
amedvednikov
3y ago
> Static analysis (autofree) with reference counting, by itself, cannot theoretically free all of the objects during the runtime of the program. It can't, that's what it says on the home page. Stuff that can't be freed dur
78.
▲
by
amedvednikov
3y ago
Nowhere in your quotes does it say GC-less autofree. "The right approach to solve this will be figured out in the near future." And it was figured out, and we now have what we have. It's described on the home page in detail.
79.
▲
by
amedvednikov
3y ago
Most of the stuff we use was written in C89 and even older versions :)
80.
▲
by
amedvednikov
3y ago
What's written is correct, what's the issue again? RC was later replaced with a tracing GC. RC is a type of GC btw, so...
81.
▲
by
amedvednikov
3y ago
Thanks, glad you have such an opinion now. We don't plan to die. There's no language that ticks all V's checkboxes: - simple - fast to compile - C/C++ perf - fits all domains - flexible memory management (gc, manual, aut
82.
▲
by
amedvednikov
3y ago
You consider the phrase "[lang] must die" a death threat? Only the author of the vaporware articles said that, AFAIK.
83.
▲
by
amedvednikov
3y ago
How was this answer aggressive? The author of Odin claimed I lied that I had json serialization, because it wasn't possible. I said you don't need AST to generate json serialization code. What's the drama about?
84.
▲
by
amedvednikov
3y ago
Most of the stuff we use is written in C. Which is even smaller than Go. You don't need complex langs to write software.
85.
▲
by
amedvednikov
3y ago
No, it was written that the source would be released in 2 days. There was also an announcement on Twitter. > I, among others to which you still seem to have bad feelings I don't know who you are, and I have no bad feelings towards y
86.
▲
by
amedvednikov
3y ago
> V was not open-sourced when the accusation was made V has been open source since its public release on June 22, 2019. On June 20, 2019 an early access build of the compiler was released.
87.
▲
by
amedvednikov
3y ago
Yep! Here's DOOM translated from C to V: https://www.youtube.com/watch?v=6oXrz3oRoEg
88.
▲
by
amedvednikov
3y ago
> If your language is too simplistic, essential complexity will just live in your ad hoc program instead, which is objectively worse. Not from my experience. Go is a breath of fresh air in this over-engineered complex industry. Go promot
89.
▲
by
amedvednikov
3y ago
You can look up vlang.io on web archive and see that it never said GC-less autofree. It actually explicitly said that RC/GC are used for stuff that can't be freed during compile time.
90.
▲
by
amedvednikov
3y ago
autofree is not reference counting, and it's marked as "not production ready yet" on the website.
More ›