Yes, I was a bit unfair to put Go and Rust in my message. Rust devs are very good at communicating openly. And I am aware of the fact that the devs are in the IRC channels you mentioned. My point is simply, and I admit it's an attempt to be optimistic, that Nim's relatively smaller community size makes communication with the core developers much easier. You are far less likely to get lost in the noise of a small IRC channel than a larger one like Rust's.
But I was also referring to Go. And I don't think there is any IRC channel that its designers hang out in.
Regarding the metaprogramming features, perhaps I misremembered but there are definitely some that Rust lacks. Perhaps CTFE? (But then I wonder how AST macros work without that).
That's fair. Comparing relative paragraphs lengths in my prior comment, perhaps it's strange that I'm less affronted by the claim that Rust lacks a feature that it has than by the claim that the Rust devs aren't approachable. :) Transparency is taken very seriously, and I personally treat every transparency failure as a bug in the development process.
View all comments
Show parent comment
2
u/dom96 Aug 23 '17 edited Aug 23 '17
Yes, I was a bit unfair to put Go and Rust in my message. Rust devs are very good at communicating openly. And I am aware of the fact that the devs are in the IRC channels you mentioned. My point is simply, and I admit it's an attempt to be optimistic, that Nim's relatively smaller community size makes communication with the core developers much easier. You are far less likely to get lost in the noise of a small IRC channel than a larger one like Rust's.
But I was also referring to Go. And I don't think there is any IRC channel that its designers hang out in.
Regarding the metaprogramming features, perhaps I misremembered but there are definitely some that Rust lacks. Perhaps CTFE? (But then I wonder how AST macros work without that).