3 ms·

Yeah basically complaining that WIP features explicitly marked as WIP are not ready and that the first public alpha release is not stable. Focusing on the fact

Yeah basically complaining that WIP features explicitly marked as WIP are not ready and that the first public alpha release is not stable. Focusing on the fact that the language is written 100% in itself from the start? Nope! Mention that it builds itself in <1 second? Nah Graphics library, DOOM's p_enemy.c translated to p_enemy.v which can be compiled and replace p_enemy.o, safety features? No. The language can be bootstrapped with "cc v.c" without any dependencies? Who cares! There's a temporary one-line os.system() hack? VAPORWARE!

chubs 7y ago
`p_enemy.c translated to p_enemy.v which can be compiled and replace p_enemy.o` <- that's extremely impressive, good on you! :)
- amedvednikov 7y ago
  Thanks. Here's how it looks like, although it doesn't compile at the moment: https://github.com/vlang/doom/blob/master/p_enemy.v https://github.com/vlang/doom/blob/master/p_enemy.v I have to finish this project asap.
smohare 7y ago
I wouldn’t take things so personally, and instead let your work stand for itself. Overly emotional attachment to one’s technical ideas and works is only a recipe for eventual mental stagnation. To be clear though, I’m not claiming this is necessarily an issue for the parent.
Crestwave 7y ago
> Yeah basically complaining that WIP features explicitly marked as WIP are not ready ... As far as I know, several of these features were not marked as WIP when this article was posted. Additionally, no features were marked at all close to the article's posting. From the article: > This article was posted on 2019-06-23. Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear. One if its criticisms is the claim on memory management. Here's an snapshot of it on 2019-06-25: https://web.archive.org/web/20190625172349/https://vlang.io/docs#memory https://web.archive.org/web/20190625172349/https://vlang.io/.... Here's the page now, marked as WIP: https://vlang.io/docs#memory https://vlang.io/docs#memory. You could argue that you simply forgot to mark these. I'm not going to go into discussion about that, but I just want to say that the author's claims seem legitimate at the time of posting. > ... and that the first public alpha release is not stable. Another quote from the article: > Thanks for reading this far. I hope this feedback can help make V a productive tool for programming. It’s a shame it seems to have been hyped so much for comparatively so little as a result. The developer has been hyping and selling this language like it’s the new sliced bread. It is not. This is a very alpha product. I bet you could use it for productive development as is if you really stuck your head into it, but as it stands I recommend against using it for anything. > The language can be bootstrapped with "cc v.c" without any dependencies? Who cares! One of the article's criticisms is that that claim isn't (wasn't?) true.

chubs 7y ago

`p_enemy.c translated to p_enemy.v which can be compiled and replace p_enemy.o` <- that's extremely impressive, good on you! :)

amedvednikov 7y ago
Thanks. Here's how it looks like, although it doesn't compile at the moment: https://github.com/vlang/doom/blob/master/p_enemy.v https://github.com/vlang/doom/blob/master/p_enemy.v I have to finish this project asap.

smohare 7y ago

I wouldn’t take things so personally, and instead let your work stand for itself. Overly emotional attachment to one’s technical ideas and works is only a recipe for eventual mental stagnation. To be clear though, I’m not claiming this is necessarily an issue for the parent.

Crestwave 7y ago

> Yeah basically complaining that WIP features explicitly marked as WIP are not ready ... As far as I know, several of these features were not marked as WIP when this article was posted. Additionally, no features were marked at all close to the article's posting. From the article: > This article was posted on 2019-06-23. Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear. One if its criticisms is the claim on memory management. Here's an snapshot of it on 2019-06-25: https://web.archive.org/web/20190625172349/https://vlang.io/docs#memory https://web.archive.org/web/20190625172349/https://vlang.io/.... Here's the page now, marked as WIP: https://vlang.io/docs#memory https://vlang.io/docs#memory. You could argue that you simply forgot to mark these. I'm not going to go into discussion about that, but I just want to say that the author's claims seem legitimate at the time of posting. > ... and that the first public alpha release is not stable. Another quote from the article: > Thanks for reading this far. I hope this feedback can help make V a productive tool for programming. It’s a shame it seems to have been hyped so much for comparatively so little as a result. The developer has been hyping and selling this language like it’s the new sliced bread. It is not. This is a very alpha product. I bet you could use it for productive development as is if you really stuck your head into it, but as it stands I recommend against using it for anything. > The language can be bootstrapped with "cc v.c" without any dependencies? Who cares! One of the article's criticisms is that that claim isn't (wasn't?) true.