On Wed, 13 Nov 2019 13:25:17 +0100, Tim Kuijsten wrote: > "Theo de Raadt" <dera...@openbsd.org> wrote: > > I'll add my voice to this. > > > > The powerful vendors writing new languages must expand their breath, > > or face the consequences that some software is not going to get written > > in their languages. Better is very much muted by unportable. > > What about gccgo? It supports more architectures than the standard Go > compiler, is written and maintained by one of the core developers of > the language and exists since the inception of Go[1].
gccgo is even worse because it relies on the (deprecated and utterly unportable) setcontext() family of functions. > (Note: I only learned about the existence of the different compilers > last night when I was researching a bit and evaluating whether or not I > should try Go) > > [1] https://commandcenter.blogspot.com/2017/09/go-ten-years-and-climbing.html >
