4 ms·

TBH, I have criticized V before, because when it launched things and claims were weird and maybe inflated, honestly don't quite remember looking at V in a good

TBH, I have criticized V before, because when it launched things and claims were weird and maybe inflated, honestly don't quite remember looking at V in a good light is still hard for me. But I am willing to give it a try, so here's a shot. Can you pls, explain a few things in short really don't want to read all of the docs to figure out the basics. 1. What platforms are well supported by V and how does it work non traditional or extension based C code? 2. What happens for edge cases where the C compiler quirks are being used for code when you transpile C to V? 3. How safe is V really? Like is it memory safe, if so maybe a quick description as to how, does it provide a memory model? What about an ABI? does it match the platform C ABI or something? 4. What happens to linking to C code, is it as easy as Zig? maybe something like zig cc? 5. How is the multithreading in V? Does it have something like openmp atleast something like rayon or do we use platform threads? 6. What about the C++ interop? anything interesting more than what other languages can do? 7. What's the current state of the compiler in terms of stability? And especially the std lib? 8. Lastly anything you want to point out as a very interesting feature in V that is not hype but so comfy that I would like to atleast use V somewhere in my stack? Maybe something like Zig's cc or Nim's metaprogramming or Haskell's mind bending type system, Idris's dependent types, etc.? Preferrably not like Rust's safety thing, I love Rust but just saying things like it's safer is very weird claim without any context. Just some details are fine no need to waste your time on making a hater change their mind. Personally I am trying to keep open mind to things, I might be harsh because of ignorance or preference or just because of being a young douchey programmer but being mean to something that has stuck around, and where a bunch of people seem to be putting in effort somehow seems worse than just shitty on it, even if it's a scam.

halfmatthalfcat 4y ago
Do you actually expect a response to that wall of questions? If you're that interested please read the docs, it's not that hard.
- minraws 4y ago
  Fixed the formatting, reading the docs takes time and in case of languages they don't give a lot of critical information about it's state in the docs, I have worked from Haskell to Rust to C++ professionally never has the language docs told me all the key details about the language to make a selection I was only able to get into them after months if not years of trial and error. I am not gonna pretend I have any love for V, but I will say I might look into it but spending several months or years with the language when I have such limited free time is not an option for me and many others. I fixed the formatting so it should be more clear as well. If no one wants to answer then fine I didn't ask the questions to get a definite answer as I said I am not entitled to an answer I just would like to know those things. I can wait for V to one day take over the world, die off, or someone to just make more fun memes. I don't really have a dog in this fight.
- deleted 4y ago
  [deleted]
amedvednikov 4y ago
1. Windows/Linux/macOS/Android/iOS/pi/WASM/*BSD/Haiku/SerenityOS 2. For stuff like i++ expressions, V allows them. Some stuff gets translated to adapted V code. Some (~2% of the syntax) will result in an error. Those will be fixed this year. 3. Memory safe, bounds checking, C ABI. 4. Ridiculously easy. The main reason it was created (was using Go before). Just run `C.foo(1,2,3)`. Use C2V to generate V wrappers. 5. Only system threads for now. 6. Same as with C. Need export "C". 7. Very stable, at least for me. Never had a crash/segfault. 8. Hard to pick. Fast compilation, hot code reloading, nice clean sum types, clean json serialization and ORM (mysql,sqlite,postgres).
- minraws 4y ago
  Cool thanks for a quick run down.

halfmatthalfcat 4y ago

Do you actually expect a response to that wall of questions? If you're that interested please read the docs, it's not that hard.

minraws 4y ago
Fixed the formatting, reading the docs takes time and in case of languages they don't give a lot of critical information about it's state in the docs, I have worked from Haskell to Rust to C++ professionally never has the language docs told me all the key details about the language to make a selection I was only able to get into them after months if not years of trial and error. I am not gonna pretend I have any love for V, but I will say I might look into it but spending several months or years with the language when I have such limited free time is not an option for me and many others. I fixed the formatting so it should be more clear as well. If no one wants to answer then fine I didn't ask the questions to get a definite answer as I said I am not entitled to an answer I just would like to know those things. I can wait for V to one day take over the world, die off, or someone to just make more fun memes. I don't really have a dog in this fight.
deleted 4y ago
[deleted]

amedvednikov 4y ago

1. Windows/Linux/macOS/Android/iOS/pi/WASM/*BSD/Haiku/SerenityOS 2. For stuff like i++ expressions, V allows them. Some stuff gets translated to adapted V code. Some (~2% of the syntax) will result in an error. Those will be fixed this year. 3. Memory safe, bounds checking, C ABI. 4. Ridiculously easy. The main reason it was created (was using Go before). Just run `C.foo(1,2,3)`. Use C2V to generate V wrappers. 5. Only system threads for now. 6. Same as with C. Need export "C". 7. Very stable, at least for me. Never had a crash/segfault. 8. Hard to pick. Fast compilation, hot code reloading, nice clean sum types, clean json serialization and ORM (mysql,sqlite,postgres).

minraws 4y ago
Cool thanks for a quick run down.