3 ms·
To the problem you were originally trying to solve, why not just use Rust? Go and C are really about as related as Java and C. Rust would have met all your requ
by ilovecaching 8y ago
To the problem you were originally trying to solve, why not just use Rust? Go and C are really about as related as Java and C. Rust would have met all your requirements, and has a lot of features you added to V to begin with.
- amedvednikov 8y agoSlow compilation. Complexity.
- ilovecaching 8y agoThat's strange, I find Rust to be much less complex than working with C++ or C. It keeps track of all the tough bits for me, and it has all of the nice expressive stuff from Haskell. With Go I kept running into cases where the language simply had no feature to save me from multiplicative complexity in my code base. I haven't had any problems with build times thus far, how big is your project?
- amedvednikov 8y agoIt's not big. But I'm developing V so that everyone can create large applications with very fast compilation times. I'm getting x120 improvement for DOOM 3, and I think it can be up to 400 times faster for more complex C++ projects using more templates, boost, etc. Of course I didn't need a new language to make my project compile faster :) I just wanted a simpler C, and I had some experience with writing languages (I wrote 2 languages at school/uni). Now I'm actually more excited about V than the original product I created it for :)
- solarkraft 8y agoThis is the part that astonishes me the most. How can you compile so fast?
- fxfan 8y agoHe is a russian- these guys are crazy when it comes to performance lol.
- bogdanoff_2 8y agoWhy not Pascal?