I'm a tiny bit worried by the way they are pushing development of so many products not directly related to core language development (a GitHub clone! A kernel!) and not focusing on creating a proper compiler. Maybe they are fine with leaving V as a transpired language indefinitely, but I think that developing this extra stuff is not going to persuade users to switch to V. With that being said, it's quite possible that the core maintainers aren't touching the extra fun stuff and are still focusing on language development.<p>Maybe someday I should try learning V again. I was going to learn it over the summer of 2020 to expand my repertoire beyond C++, but I gave up fairly quickly and ended up learning Qt instead, which has proved to be a very wise choice - knowing Qt why I have my current job (for multiple reasons).
Going through their docs, I'm having hard time identifying the 'silver bullet' that makes this all possible.<p>This is m first time seeing this language 'V'. So no pre-baggage.<p>The splash page is making extraordinary claims.<p>But a lot of languages have the same features, but not the big claims like size and speed.<p>So what is this group doing different that couldn't be done in Rust or Go or dozen others.<p>Do we need another language? Or if there is just 'one simple trick', then just update the others.<p>If it is 80% GO, then why wouldn't the GO team just incorporate this 'whatever it is'.<p>or- Can someone explain it to me like i'm 5 what is the big idea under the hood here.
It has been over 4 years since I've commented on the V language proper. I still think Alex need to greatly improve his public relation skills, but otherwise the only thing matter is that the language is still alive after years. It took way longer than the original claim (which again is a PR issue) but it is now a language that has advertised features and may fill some niche. I'd like to applaud the perseverance.<p>I don't know about a long-term plan, but it seems that V will now need one if there isn't already one. Many languages start out fresh and either die out (metaphorically) or get crushed on their own features. Planning seems to be necessary to avoid either fates, and yet is not sufficient to guarantee survival. I personally witnessed this from D firsthand back when a stdlib divide was threatening its future, and believe every successful language author need to answer this question (for example, Rust would say the coevolution with Servo was massively beneficial). So Alex---or other core developers if any---, do you have any thoughts on this?
What I find interesting is the cross platform UI from V which also compiles for Android:
<a href="https://github.com/vlang/ui">https://github.com/vlang/ui</a><p>It does seem to be still in its very early stages but if they are able to make this a more mature library, it may actually be quite useful for tiny, fast apps.
It is really striking, the difference in *everything* between some beta quality programming language projects and approaches of people behind them.<p>- Effort applied; To be tailored for certain kinds of projects; Solve problems in existing languages; Approaches to prevent/force adoption of beta quality project; Philosophical approaches behind project or lack thereof.<p>Now on the personal, subjective note, the more I look, the more I want to avoid V and get my hands on Jai [1][2]<p>[1] <a href="https://github.com/Jai-Community/Jai-Community-Library/wiki/Overview">https://github.com/Jai-Community/Jai-Community-Library/wiki/...</a>
[2] <a href="https://github.com/Jai-Community/Jai-Community-Library/wiki/Philosophy-of-Jai">https://github.com/Jai-Community/Jai-Community-Library/wiki/...</a>
I like many things about the language but haven’t yet written a significant amount of code in it to properly evaluate it. V feels a lot like Go. Plus a language that can replace C/C++ for bare metal programming.
What's the status of autofree engine becoming the default? It's perhaps the most discussed feature of the language. Last year it was mentioned the GC it's temporary until autofree engine is production ready.
I am thrilled to see so much progress on V! I remember being excited about this language and seeing an immense amount of hatred, skepticism and doubt, and unfortunately being taken in by it.<p>Is this hatred still present?<p>Has anyone used the language extensively that can comment on its usability?