Publicizing MacPorts

[Steven Smith]

> "Champion" how?
> 
> "MacPorts should be making [the case]" how?

The same way everyone else does: make noise, push news, promote, let the tech reporters know. Follow the Woody Allen rule for success.

If a comparable announcement to this was made for MacPorts, I missed it:

https://arstechnica.com/gadgets/2021/02/mac-utility-homebrew-finally-gets-native-apple-silicon-and-m1-support/

Mac utility Homebrew finally gets native Apple Silicon and M1 support
There aren't bottles for every package yet, but the work is in progress.

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.


> On Apr 19, 2021, at 03:40, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Apr 18, 2021, at 07:28, Steven Smith wrote:
> 
>>>> I completely agree that Homebrew is currently winning at publicity.
>>> 
>>> What should the MacPorts community be doing do publicize MacPorts better?
>> 
>> The new M1 architecture is a perfect opportunity to champion MacPorts’s strengths:
>> 
>> • Strong emphasis on binaries built from source code, often specifically patched
>> • Strong emphasis on smart, solid engineering with high quality, reliable installs
>> • Extraordinarily comprehensive coverage across both software and architectures
>> • Expert, engaged, and helpful development community
>> 
>> We’re seeing all these strengths play out in MacPorts’s successful and ongoing migration to the new M1 chip.
>> 
>> 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
>> 
>> This is an easy case to make, and MacPorts should be making it, using the M1 as a banner example.
> 
> Sure.
> 
> "Champion" how?
> 
> "MacPorts should be making [the case]" how?
> 
> 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?
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210419/1eb53b9c/attachment.htm>