From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com [173.203.187.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A76973CB53 for ; Wed, 23 Jun 2021 12:09:15 -0400 (EDT) Received: from app38.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp2.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 4BD9518AB; Wed, 23 Jun 2021 12:09:15 -0400 (EDT) Received: from deepplum.com (localhost.localdomain [127.0.0.1]) by app38.wa-webapps.iad3a (Postfix) with ESMTP id 38979E03AC; Wed, 23 Jun 2021 12:09:15 -0400 (EDT) Received: by apps.rackspace.com (Authenticated sender: dpreed@deepplum.com, from: dpreed@deepplum.com) with HTTP; Wed, 23 Jun 2021 12:09:15 -0400 (EDT) X-Auth-ID: dpreed@deepplum.com Date: Wed, 23 Jun 2021 12:09:15 -0400 (EDT) From: "David P. Reed" To: "Matt Mathis" Cc: "Dave Taht" , "Cake List" , "cerowrt-devel" , "bloat" MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-Type: plain In-Reply-To: References: X-Client-IP: 209.6.168.128 Message-ID: <1624464555.230819179@apps.rackspace.com> X-Mailer: webmail/19.0.4-RC X-Classification-ID: 6f378fa2-f97d-4c3e-945a-fccbf66e50c9-1-1 Subject: Re: [Cake] =?utf-8?q?=5BCerowrt-devel=5D__access_to_cmsg_from_go=3F?= X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2021 16:09:15 -0000 (They closed the issue on the golang link.)=0A=0A=0AI'm not a golang user. = One language too many for me. It sounds like a library issue.=0A=0AMy sugge= stion would be to use the openness of open source. Generate a patchset that= extends the interface properly. Don't try to "improve" what you don't like= - communities like stability and backward compatibility. Explain the added= semantics in documentation.=0A=0AThen, maintain your fork. I don't know ho= w the golang community works with versioning of libraries, but Python, Rust= , Haskell, and NodeJS all have ways to let projects use variants of librari= es.=0A=0AThen, submit that patchset upstream to the golang community. Advoc= ate for upstreaming it, and develop a community that uses the patched libra= ry. Eventually, you may be able to stop maintaining your variant toolset. O= r you will develop an alternat library user base that disagrees with upstre= am's decisions.=0A=0A(Analogy, Android's Linux Kernel vs. Linus Torvalds's.= Google Android rejects to some extent Linus's crew's unwillingness to acce= pt what Android needs as improvements.)=0A=0AThis is "modern open source co= mmunity" practice for getting things done. Pragmatic innovations in shared = codebases sometimes have to wait for the original egos to die off.