v

well I just git cloned it and ran make and that was it. Very impressive 26k line generated c file: https://github.com/vlang/vc/blob/master/v.c is this the future of C? it's like too dangerous for humans to code it directly. We need langs like this to make C for us. Magic in this file: https://github.com/vlang/v/blob/master/tools/gen_vc.v

> The V compiler hasn't crashed once for me, and I haven't received any crash reports from other users. https://github.com/vlang/v/issues/2838 "Compiler crash during filtering's assignment operation on a mutable array" https://github.com/vlang/v/issues/2565 "Compiler crash when using inexistent struct type in const block" (One of these is from two days after the author wrote the above statement, but the other isn't.) There are other reports where the V compiler seems to generate C code that does not compile, or only with very nasty type warnings, for example: https://github.com/vlang/v/issues/2960 https://github.com/vlang/v/issues/2981

Scripting is one of V's main features[0]. Just a couple days ago, it was incorporated into the 'master' branch[1] so you can now use it. 0 - https://vlang.io/docs#bash 1 - https://github.com/vlang/v/commit/5cd38ec91bc1919aca9f63432e...

Claims to "being able to now compile itself in 0.09 seconds" whilst pushing the need for an AST to the side represents a serious problem in the language's general direction (and I mean general in an aggregated way). Of course shelling-out to curl for your download function is a bodge to be fixed, but the language's issues are not merely one specific problem. The author's misrepresentation of the language, of course, hangs overhead upon all of this. https://github.com/vlang/v/issues/35 I don't want to discount all of the work people have put into V. It is clear that they have made considerable progress since earlier this year and I commend them for pushing the language into a more usable state. Nevertheless, I still retain a considerable degree of skepticism.

> many empty promises by the creator which V simply wasn't able to deliver on. Seems like this trend will probably continue with regards to the "1.0 release in December 2019" claim advertised in the Github description[1][a], since things like memory management are not implemented yet[2] and the December 2019 deadline would mean going from "first public alpha"[3] to 1.0 in less than a year. [1] https://github.com/vlang/v [a] depending on what 1.0 means, I guess [2] https://news.ycombinator.com/item?id=21296992 [3] https://news.ycombinator.com/item?id=21297051

and the REPL only leaks 1MB [1] to compile and run a hello world program. 1: https://github.com/vlang/v/issues/514

I'm working on a language with a focus on simplicity and "only one way to do it": https://vlang.io The development has been going quite well: https://github.com/vlang/v/blob/master/CHANGELOG.md