1,578 karma · joined November 15, 2016
So rude indeed.
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 by many people.
It can't, that's what it says on the home page. Stuff that can't be freed during compile time is handled via GC.
What's the issue again? What's the impossible claim?
"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. 4 ways to handle memory.
Why another new account?
RC was later replaced with a tracing GC.
RC is a type of GC btw, so...
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, autofree in the future, arena)
- batteries included
- readability and development speed of python, C perf
etc
Only the author of the vaporware articles said that, AFAIK.
I said you don't need AST to generate json serialization code.
What's the drama about?
You don't need complex langs to write software.
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 you.
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.
Not from my experience. Go is a breath of fresh air in this over-engineered complex industry.
Go promotes simplicity and speed, and so does V.
> I'm sure you'll like it!
And what's wrong with this comment?
They were released 2 days before the source. It was just an early access thing.
They probably weren't when you worked with them.
Just for one thing: focus on simplicity and fast builds.
It does, a lot: https://vlang.io/compare#go
No header files hell for example.
We're not going anywhere :)
You can check the number of commits over the last 4 years.