5 ms·
As I can't respond to amedvednikov's comment below, let me respond to it through yours (sorry): > No things are closed source. Never have been. That's not cor
by EdSchouten 5y ago
As I can't respond to amedvednikov's comment below, let me respond to it through yours (sorry):
> No things are closed source. Never have been.
That's not correct. I seem to remember that when V was released initially, the compiler was available for download in binary form only. The source code was only released later on.
- amedvednikov 5y agoThat was before the public release and only lasted for a week. So saying now 2.5 years later some things are closed source is ridiculous.
- vlang1dot0 5y agoCould you point to the C2V source?
- ylluminate 5y agoWe could, but it's not yet public. Rest assured, it exists and there is work going forward on it to get it out the door somewhat soon. You may find the public `go2v` work interesting. It's being worked on by some other folks in the community: https://github.com/vlang/go2v https://github.com/vlang/go2v
- vlang1dot0 5y agoSo, you're saying C2V is closed source then? Which is exactly what Alex said isn't true.
- Tozen 5y agoThere is a difference between not releasing the source yet versus closed source. Often, closed source refers to not ever going to open the source, including commercial interests. In regards to not yet releasing the source, things can be in the process of being worked on, made ready for public review, or being organized where other programmers can more sensibly contribute to the source.
- deleted 5y ago[deleted]
- paskozdilar 5y agoNote that, in most cases, you can't respond to a comment because it's been posted too recently. I think it's a mechanism to prevent flaming.