The first release was just Go's parser ripped out and bolted onto a barebones first year of college level compiler, and touted as "safer than Rust", "compiles in milliseconds", etc. but didn't even have real type-checking at the time, nor did it free memory, and many other basic functionality. Furthermore, I vividly remember the author's Patreon advertised at the top of the page back then, and for a while he raked in a couple thousand dollars a month for it.
However, over the years some actually talented people (and nowadays probably LLMs) have somehow sort of fixed most of the biggest warts, but it's still nowhere near what it advertised in that first release.
What's wild is I was looking at the language's home page again, and looking to find their GitHub, the first GitHub link I noticed, is the GitHub sponsors link.
I don't mind supporting a project like this, but this is a bit excessive.
Was it really Go's parser? That wouldn't surprise me, but also that kind of makes sense to me why it looked a bit 'familiar' in terms of syntax.
It's definitely been "alpha" tier for a while, which it doesnt help that the developer doesn't outline any sort of stability that I can recall (back then at least) which imho if you're publishing a language, you should let the reader know.
It appears you're calling something a scam because an early alpha version was early alpha quality. If so, that would be unprofessional and inflammatory.
I'm open to being wrong. So again, can you explain what you mean?
I have this amazing new thing I'm making, nothing like it, better than everything else. Here's a prototype that does none of that and is _barely_ functional. Care to invest $2000? If so, do I have a bridge to show you...
They haven't had a stable 1.0 release yet, but they've had many pre-1.0 releases. It's not some personal experiment that's been sitting in the dev's Github that people are piling onto; the author has gone out of their way to promote it, beg for donations, and lash out at any criticisms.
The issue has never been the quality of the language per se, the issue has been 1) wildly misrepresenting the quality of the language in the present tense; 2) not even having any kind of a realistic roadmap towards achieving the kind of outsized and implausible claims about the quality of the language; and 3) using these outsized, implausible misrepresentations as a way of soliciting hype and funding for the author.
I never paid enough attention to figure out if the drama is justified or not (and don't really care either, please don't try to convince me to care either, don't shoot the messenger).
Huh. Pretty cool. I haven't looked at vnix in a while, and it's been almost as long since I looked at V. It had a lot of controversy early on. I'd be interested to hear from anyone who has tried it recently to find out if they ever ended up delivering on their promises.
QEMU uses macOS hardware virtualization for the ARM64 desktop.
Huh, since when does QEMU support hardware virtualization on Apple Silicon? To the best of my knowledge, among all the VM managers available on macOS (VMware, Parallels, VirtualBox, …) only UTM currently supports hardware virtualization and that's through the Apple Virtualization backend, not through QEMU.
How are things going with V btw? In the past i've seen some bad press about this programming language.
It was nice to use when I tried to dabble with it.
How this scam language gained traction is beyond me.
How can a language be a scam?
I have no opinion on the subject but I have found this to be an interesting dive into the supposed controversy: https://justinas.org/the-bizarre-world-of-v
The first release was just Go's parser ripped out and bolted onto a barebones first year of college level compiler, and touted as "safer than Rust", "compiles in milliseconds", etc. but didn't even have real type-checking at the time, nor did it free memory, and many other basic functionality. Furthermore, I vividly remember the author's Patreon advertised at the top of the page back then, and for a while he raked in a couple thousand dollars a month for it.
However, over the years some actually talented people (and nowadays probably LLMs) have somehow sort of fixed most of the biggest warts, but it's still nowhere near what it advertised in that first release.
Lol this is interesting. If you want to make money you can "invent" a language. With LLMs you could probably make it pretty decent too.
What's wild is I was looking at the language's home page again, and looking to find their GitHub, the first GitHub link I noticed, is the GitHub sponsors link.
I don't mind supporting a project like this, but this is a bit excessive.
Was it really Go's parser? That wouldn't surprise me, but also that kind of makes sense to me why it looked a bit 'familiar' in terms of syntax.
It's definitely been "alpha" tier for a while, which it doesnt help that the developer doesn't outline any sort of stability that I can recall (back then at least) which imho if you're publishing a language, you should let the reader know.
Can you explain what you mean by this? They haven't had a first release yet. They're still in beta.
That's being pedantic. The first public announcement was many years ago.
It appears you're calling something a scam because an early alpha version was early alpha quality. If so, that would be unprofessional and inflammatory.
I'm open to being wrong. So again, can you explain what you mean?
I have this amazing new thing I'm making, nothing like it, better than everything else. Here's a prototype that does none of that and is _barely_ functional. Care to invest $2000? If so, do I have a bridge to show you...
If I go to the vlang releases page, I see literally hundreds of releases https://github.com/vlang/v/releases
They haven't had a stable 1.0 release yet, but they've had many pre-1.0 releases. It's not some personal experiment that's been sitting in the dev's Github that people are piling onto; the author has gone out of their way to promote it, beg for donations, and lash out at any criticisms.
The issue has never been the quality of the language per se, the issue has been 1) wildly misrepresenting the quality of the language in the present tense; 2) not even having any kind of a realistic roadmap towards achieving the kind of outsized and implausible claims about the quality of the language; and 3) using these outsized, implausible misrepresentations as a way of soliciting hype and funding for the author.
For a longer read:
https://justinas.org/the-bizarre-world-of-v
This seems to be the language's main page https://vlang.io/
For reference, for the ones who aren't aware of the constant drama that seems to follow V: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... (open up almost any discussion and see the flood of similar messages).
I never paid enough attention to figure out if the drama is justified or not (and don't really care either, please don't try to convince me to care either, don't shoot the messenger).
The book about the language was published by packt, and I had my eyebrows raised. I want to give a benefit of doubt tough and learn more.
Yeah it seems to be following the No Man's Sky playbook.
I don't know.
But I just released a language called U, and I was surprised to see this one.
https://ulanguage.org
Just like V but without sharp edges?
Huh. Pretty cool. I haven't looked at vnix in a while, and it's been almost as long since I looked at V. It had a lot of controversy early on. I'd be interested to hear from anyone who has tried it recently to find out if they ever ended up delivering on their promises.
I enjoy the screenshot showing Calculator taking 617 MB of RAM. It feels very modern indeed.
You have an amazing eye for details. Might be the "wine calculator" from the desktop.
It looks nice. How much vibecoding does it contain? Can we trust these claims?
Huh, since when does QEMU support hardware virtualization on Apple Silicon? To the best of my knowledge, among all the VM managers available on macOS (VMware, Parallels, VirtualBox, …) only UTM currently supports hardware virtualization and that's through the Apple Virtualization backend, not through QEMU.