<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><blockquote type="cite"><div dir="ltr">"Champion" how?<br><br>"MacPorts should be making [the case]" how?</div></blockquote><br></div><div dir="ltr">The same way everyone else does: make noise, push news, promote, let the tech reporters know. Follow the Woody Allen rule for success.</div><div dir="ltr"><br></div><div dir="ltr">If a comparable announcement to this was made for MacPorts, I missed it:</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://arstechnica.com/gadgets/2021/02/mac-utility-homebrew-finally-gets-native-apple-silicon-and-m1-support/">https://arstechnica.com/gadgets/2021/02/mac-utility-homebrew-finally-gets-native-apple-silicon-and-m1-support/</a></div><div dir="ltr"><br></div><div dir="ltr"><h1 class="title" data-reader-unique-id="titleElement" style="font-size: 1.95552em; line-height: 1.2141em; margin-top: 0px; margin-bottom: 0.5em; max-width: 100%; caret-color: rgb(27, 27, 27); color: rgb(27, 27, 27); font-family: -apple-system-font;">Mac utility Homebrew finally gets native Apple Silicon and M1 support</h1><h2 class="subhead" data-reader-unique-id="subheadElement" style="font-weight: normal; font-size: 1.46664em; color: rgba(27, 27, 27, 0.65); margin-top: -0.35em; line-height: 1.27275em; max-width: 100%; font-family: -apple-system-font;">There aren't bottles for every package yet, but the work is in progress.</h2></div><div dir="ltr"><span style="caret-color: rgb(27, 27, 27); color: rgb(27, 27, 27); font-family: -apple-system-font; font-size: 19px; background-color: rgb(255, 255, 255);">Popular Mac tool Homebrew has long been used by developers and others for package management on macOS, but as we lamented in our first M1 Mac review, it didn't support Apple Silicon when Apple's new Macs first launched late last year. Now, with the release of Homebrew 3.0.0, that's no longer the case: Homebrew now supports Apple Silicon natively, albeit not with every package.</span></div><div dir="ltr"><font color="#1b1b1b" face="-apple-system-font"><span style="caret-color: rgb(27, 27, 27); font-size: 19px; background-color: rgb(255, 255, 255);"><br></span></font></div><div dir="ltr"><font color="#1b1b1b" face="-apple-system-font"><span style="caret-color: rgb(27, 27, 27); font-size: 19px; background-color: rgb(255, 255, 255);"><br></span></font><blockquote type="cite">On Apr 19, 2021, at 03:40, Ryan Schmidt <ryandesign@macports.org> wrote:<br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>On Apr 18, 2021, at 07:28, Steven Smith wrote:</span><br><span></span><br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I completely agree that Homebrew is currently winning at publicity.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>What should the MacPorts community be doing do publicize MacPorts better?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The new M1 architecture is a perfect opportunity to champion MacPorts’s strengths:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>• Strong emphasis on binaries built from source code, often specifically patched</span><br></blockquote><blockquote type="cite"><span>• Strong emphasis on smart, solid engineering with high quality, reliable installs</span><br></blockquote><blockquote type="cite"><span>• Extraordinarily comprehensive coverage across both software and architectures</span><br></blockquote><blockquote type="cite"><span>• Expert, engaged, and helpful development community</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We’re seeing all these strengths play out in MacPorts’s successful and ongoing migration to the new M1 chip.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We’re also seeing the contrast of how Homebrew’s undesirable design decisions, reliance on external binaries, and other shortcuts affect its migration to the M1: https://github.com/Homebrew/brew/issues/7857</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>This is an easy case to make, and MacPorts should be making it, using the M1 as a banner example.</span><br></blockquote><span></span><br><span>Sure.</span><br><span></span><br><span>"Champion" how?</span><br><span></span><br><span>"MacPorts should be making [the case]" how?</span><br><span></span><br><span>I know our main web site needs an overhaul, and drawing attention to some of these facts there would be good. In what other ways, what other venues, do you envision this information being communicated?</span><br><span></span><br></div></blockquote></body></html>