On Tuesday, 19 December 2017 at 09:54:05 UTC, Walter Bright wrote:
"C, Python, Go, and the Generalized Greenspun Law"
http://esr.ibiblio.org/?p=7804
That is what I keep saying thanks to my experience using Oberon
systems during
the 90's, and following everything that was done with Mesa/Cedar,
Modula-2+, Modula-3, Singularity, Midori, just to name the most
famous ones in CS circles.
Microsoft has been busying adopting lessons from Midori into C#,
hence .NET Native, and the language changes for features already
present in D.
The problem is that this yet another area where developers only
change their opinion if they experience themselves what it means
to use a GC enabled systems programming language.
It is very hard to change the mentality that just because the GC
is there, doesn't mean there aren't other ways to manage memory
and other resources.
GC is a convenience, if at the end the use case constraints
aren't met, then it is time to profile and use other approaches,
like actually doing some manual memory management in the hot
path, but only if it really a must have.
Google is already using Go on some of their Fuchsia system
modules, like the TCP/IP stack and file system driver utilities,
maybe someone like Google really needs to push such an OS into
developers to settle the discussion once for all.
And then D's GC won't be an issue any more, given that the
language is much better than just using Go.
--
Paulo
