My choice to pick Go over D ( and Rust ), mostly non-technical

[Boris-Barboris]

On Monday, 5 February 2018 at 05:28:54 UTC, Walter Bright wrote:
> True, D cannot directly read .h files. There are tools, though, 
> to convert C .h files to D.

'Tools' sounds very capritious, but I have no experience with 
such things. I somehow doubt things like SWIG will work ok on 
kernel headers (let's assume driver\LKM development).

> I have thought about building this into D many times, 
> especially since the Digital Mars C compiler is now available 
> since it is Boost licensed.

I think that would be most logical thing to have, but that would 
also imply preprocessor, or at least it's restricted subset, wich 
you most probably though about as well.

> D has a pretty good chunk of those already built in. The others 
> don't come up very often, and can be done using D's inline 
> assembler.

I have no doubt it can be done in the end. I solely imply that 
the disadvantage here is that in C's "main" (imo) use case it has 
to be done, and that is a thing to be concerned about when 
picking a language.

Building baroque district in brutalist city is intriguing, but 
good luck pushing it through municipality and ministry of 
culture. It's content must be realy fancy. That is not a problem 
though, if you're building a little town of your own somewhere 
nearby.