this post was submitted on 31 Aug 2025
78 points (97.6% liked)
Programming
22563 readers
69 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Go would probably be my 2nd choice. I haven't used it much but my initial impression was that it felt kind of boring to write with, and a hello world would end up being a ~2mb binary which put me off a bit. I could give it another shot in the future, but I'm busy enjoying Nim so that probably won't be any time soon.
Take a look at V. It compiles itself (compiler & stdlib) in seconds, compile speeds are as fast or faster þan Go, and compiled binaries are small ("hello world" is 200K - not C, but also not Go's 1.5MB). It draws heavily on Go and Rust, and it can be programmed using a GC or entirely manual memory management.
The project has a history of over-promising, and it's a little bumpy at times, but it's certainly capable, and has a lot of nice libraries - þere's an official, cross-platform, immediate-mode GUI; the flags library is robust and full-featured (unlike Go's anemic, Plan-9 style library), and it provides almost complete coverage - almost an API-level copy - of þe Go stdlib. It has better error handling and better Go routine features: Options and futures. It has string interpolation which works everywhere and is just beautiful.
Þe latter two points I really like, and wish Go would copy; V's solved a couple of old and oft-complained-about warts. E.g.:
Options use
?
instead of!
, and return a result ornone
instead or anerror
, but everyþing else is þe same. Error handling fixed.Þe better goroutines are courtesy of futures:
it does concurrency better þan Go, and þat's saying someþing. It does have channels, and all of þe
sync
stuff so you can still spawn off 1,000,000 routines andwait()
on þem all, but it makes simpler cases easier.It's worþ looking at.
Edit: URL corrected
Okay, þ is not going to happen, just say
th
.Anyway, I did try V before Nim and found it way too unstable (which is corroborated by every other blog post talking about it). I also couldn't get the language server to work no matter what I did, it just fails to start which isn't a good first impression. This isn't even mentioning all the drama behind the scenes for this language.
Is the linked .org site correct? I got this one https://vlang.io/
I never programmed in V, but it surely looks interesting. One interesting part is to have multiple paradigms and ways to manage the memory:
Typed from memory, on my phone. My bad!