Wouter, thank you so much for this response. your message has motivated me to change adequate to target gccgo (rather than golang-go, which is a couple of years ahead), to extend the availability of adequate to more ports
On Wed Dec 18, 2024 at 9:34 PM CET, Wouter Verhelst wrote: > Hi, > > On Wed, Dec 11, 2024 at 11:57:14PM +0100, Serafeim (Serafi) Zanikolas wrote: [..] > If you write something for the project, I think you should totally > choose the language that you're most familiar and comfortable with. > Sometimes that means disappointing people using architectures on which > your language of choice is not available. That's fine, provided you're > not trying to replace or implement a core component of Debian. > > If you're trying to write something that eventually should be running on > *every* Debian system out there, then please, for the love of all that > is important to you, don't use something that requires specific porter > work. But outside that constraint? Do whatever makes you most > productive. two things: first, what is a "core component of Debian" is very much up to debate, but I'd be quite surprised if anybody made the case that adequate is. second, any porter work to make gccgo available would be valuable in its own sake, given how many other programs are written in go these days
signature.asc
Description: PGP signature
