I love looking at new languages. People invent really creative stuff. However, my exploration usually ends with "this is great, but there are no libraries for it, so I probably won't use it".<p>If you are building a language, starting from scratch is the epitome of Not Invented Here syndrome. Build it on top of an existing ecosystem. Look at Elixir and how it builds on Erlang and interoperates with it just perfectly. Or look Groovy, Scala and Clojure to see what kind of range you can get from a single platform. With the exception of Go, every language that has become popular in the past 10 years, built on something else.
My friendly advice for the author of this project:<p>Release the code on Github. Just release anything, even if it's not finished. Make the code work first, <i>then</i> build a slick website where you brag about its features and benchmarks.<p>Creating the website first, before there's even anything to try out, is disingeous at best, and at worst it's leaching productivity away from time better spent programming. I remember how, as a junior developer, it was a lot more fun talking about how great my project was going to be, than doing the actual, hard work. But it does take hard work to bring something to completion.<p>You're doing the exact same thing with your chat app, Volt. You spent years talking about how great it was going to be. You promised features and release dates, then changed the release dates once you weren't able to deliver. Your current alpha release barely works and barely has any of the features. You clearly need some helping hands to implement all the features you've been promising over the years.<p>I'm sure there are lots of developers here who would love to hack on a new programming language or a chat app.
I‘m not sure this will ever reach the light of day. It follows the same patterns as Eul did, another creation if the same inventor:
- plenty of empty links on the website that lead to something ‚coming in march/april/june/...‘
- lots of nice ideas, but nothing to show for it<p>I wish the creator all the best, but Eul promised a lot, long long ago, and never delivered
Creating and evolving programming languages is a difficult task. It also takes considerable time to write a decent set of libraries and iron out most of the wrinkles before it can be used in production.<p>As more people move into programming, we're bound to see more languages on the horizon. I wonder what the most popular languages will be, say, 10 years from now?<p>I'm personally looking forward seeing one language reach maturity – Pony – <a href="https://www.ponylang.io/" rel="nofollow">https://www.ponylang.io/</a>
It seems that it brings some novel concepts to the table, one being the combo: statically compiled + actor model + high performance + capabilities secure.
Looks very similar to Zig in terms of goals. I'm rooting for both, but it seems that Zig is ahead in terms of community. Would V have any benefits over Zig?<p>I think a "better C" is the biggest hole in the programming language world today. Rust doesn't do it to me, because what makes C great is that it's so simple, and easy to write a compiler for. Rust is a different class.
I'm curious. Why the short names such as .len instead of .length? Also, ui.WindowCfg instead of ui.WindowConfig? I think this would make we hesitate all the time. Was it .new_textbox or .new_txtbox? Short keywords are one thing (Lua's local and function are no fun) but abbreviated library functions and types are another.
It looks like a nice little language. It looks like Go influenced the syntax (in a good way). Based on the "concurrent" example, can we assume that it does coroutines instead of green threads?<p>Have you tried converting the C impl of the Computer Language Benchmarks Game to compare runtime performance against other languages?
well, I don't know why this doesn't have more upvotes. It deserves them. This is literally the first time I've fallen in love with a programming language. It does all the things I'd want it to. Has all the positives of go without most of the shortcomings, is minimal and understandable, disallows 10.days.ago style magic without being overly limiting, compiles fast and makes small apps, something I really want in the age of bundling Chromium and Node with every hello world, and has a native GUI, so huge potential for accessibility. The only thing unnerving me is that Volt, the only publicly available app written in V, doesn't seem to be accessible which might indicate the GUI is not native after all.
There used to be a stack-based language called V as well... <a href="https://code.google.com/archive/p/v-language/" rel="nofollow">https://code.google.com/archive/p/v-language/</a>
I know it is "yet another language" but I at least like the examples I saw. Very golang inspired obviously (even has the go keyword) but with some niceties (e.g optionals). Maybe when I get around to writing my Z language I'll use this as a basis.
Looks very similar to Go(which is a good thing) but to catch up it needs a great std lib and great tools like Go has. I wish it would keep the upper-case/lower-case convention as well for private/public identifiers
I think this looks extremely promising. Out of curiosity, is there any support for lambdas / functional programming? Can I pass a function as a reference?
This seems pretty amazing. I'm really curious how it manages to avoid data races. It doesn't seem to mention anything complicated like rust lifetimes.<p>Also, what happens when unsafe C++ is converted to v, for example, code with iterator invalidation?<p>There are so many unanswered questions.
If it works as advertised, it looks to be a boon. I hope we can commit to a full security audit of the compiler, runtime, and std libs. My trust is lacking lately.
Come on guys. I get it that everyone and their cat invent new languages nowadays. And that is a cool thing, do not get me wrong. But as a professional in that field, is it too much to ask to give just a little overview over the /interesting/ parts of the language? What is its type discipline? What data structures are supported? What is the execution/evaluation strategy? How about concurrency? Coroutines? Macros? Modules? The language design space has been mapped thoroughly in the last decades. Is it so hard to give a tiny X on that map?
Well cheers to someone making a compiled language that is like a simplified C/C++. Rust is great but it's a paradigm shift, and Go is great but it (edit here:) has a runtime which we don't have implicit control over.<p>This is a promising C-ish language without the cruft and easy foot-shot triggers.<p>Can't wait for the rules regarding packages/modules, how they are distributed, the clean and simple build systems, documentation constructs, and clean integration into VSCode ... and of course all of the key/default libraries we need to be productive.<p>Good start folks, looking forward to the next rev.
I dont believe this is real. Sorry but maybe someone can decompile the volt app to see if this is any legit.<p>I mean if you are releasing such vaporware you should at least do it anonymously not openly like you do.