On 11/09/13 08:44, Alec Teal wrote:
If Java must go, and it must have a replacement Ada makes sense. The
issues with Go (sadly, you guys are doing superb work) do make sense.
I don't know enough about Java (the GCC front end and such) to know if
it should go, if it does go why should it be replaced?
What we're trying to balance is developer time vs benefit of the
language. I'm of the opinion that GCJ's importance continues to
diminish across multiple axis and that we probably past the point where
it's still worth our developer's time to continue to build/test it for
every submitted patch.
I originally liked Go as a replacement as it tests certain codepaths
that are currently only tested by the GCJ frontend. However, it's
looking like Ada might be a better choice.
jeff
