Replacing C

[Achim Gratz]

Eric S. Raymond writes:
> I'm not worried about that for Go, because Google has sunk a lot of investment
> into million-line Go programs (like running YouTube and the Chrome download
> server). Because those are unlikely to go away, so is its funding case.  This
> is actually one of the stronger arguments for Go.

I think it's irrelevant how many million lines of code exist for any
given language or how big the parent company is.  The real question to
ask, IMHO, is how many lines of code are implemented in the exact space
that NTP occupies and how dependent the owners of that code are on
keeping it working.  I don't know the answer to that question w.r.t. Go
or some other languages you might want to discuss.

> The out-of-left-field possibility I've been mulling privately is
> Ocaml.  But not very seriously; one of the criteria has to be
> accessibility to future maintainers coming out of a C background
> and Ocaml doesn't do at all well there.

If you're considering systems that require a runtime (I'm not sure if
OCaml still requires one, but last I looked it did), then somebody
surely will bring up Java… :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada