Re: Replacing C (was: Re: The end of the beginning is in sight)

2017-01-08 Thread Eric S. Raymond
Frank Nicholas : > If you haven’t seen [Grumpy], you might be interested. Not sure of the > quality (experimental?) > > Google boosts Python by turning it into Go: Yes, Gary turned me on to this earlier in the week. Grumpy is extremely interesting, as a path forward for reposurgeon if not fo

Re: Replacing C (was: Re: The end of the beginning is in sight)

2017-01-08 Thread Frank Nicholas
> >>> 3. Move the codebase to Go or Rust? >> >> While I understand what kind of problem you're trying to solve, at the >> moment I see neither of those two languages survive for long if their >> current parent projects change course (again). > > I'm not worried about that for Go, because Google

Re: Replacing C (was: Re: The end of the beginning is in sight)

2017-01-08 Thread Eric S. Raymond
Sanjeev Gupta : > Would you consider Julia ? Alas, a perfect example of a language excluded from present consideration because the developer and userbase is below the threshold that says long-term sustainability. -- http://www.catb.org/~esr/";>Eric S. Raymond _

Re: Replacing C (was: Re: The end of the beginning is in sight)

2017-01-08 Thread Sanjeev Gupta
On Sun, Jan 8, 2017 at 9:32 PM, Eric S. Raymond wrote: > ractically speaking, I don't have time to become fluent in half a dozen > candidate languages. I can probably budget time for one more beyond Go > and Rust; Erlang actually seems like a strong contender there. > Would you consider Julia ?

Replacing C (was: Re: The end of the beginning is in sight)

2017-01-08 Thread Eric S. Raymond
Mark: Heads up! Serious discussion of language migration follows. Achim Gratz : > Eric S. Raymond writes: > > 1. Performance and algorithm tuning - we need to take a serious swing > > at Gary's slow-convergence problem, in particular. > > This objective needs to be defined more properly. Agreed.