How to install Homebrew on Mac What you need. Before you install Homebrew on Mac, you’ll need to make sure you have the following: A 64-bit Intel CPU or an Apple Silicon CPU (i.e., an M1 Mac). HOMEBREW AND HOW THE APPLE CAME TO BE by Stephen Wozniak Stephen Wozniak is the designer of the Apple II computer and cofounder of Apple Computer Inc. Without computer clubs there would probably be no Apple computers. Our club in the Silicon Valley, the Homebrew Computer Club, was among the first of its kind.HOMEBREW AND
HOW THE APPLE
CAME TO BE
MacOS Homebrew running natively on M1/Apple Silicon/ARM has partial functionality. We recommend installing into /opt/homebrew and forbid installing into /usr/local (to avoid clashing with the macOS Intel install and allow their usage side-by-side). We currently recommend running Homebrew using Intel emulation with Rosetta 2. In this article, we explain how to brew your own hard apple or pear cider (a.k.a. Perry) What to Expect. Naturally-made, or craft cider is quite dry. It is not sweet because the yeast, left to do its job, will consume most of the sugar in the juice. Many commercial ciders are 'back sweetened'. Nov 17, 2020 This will setup Homebrew in /usr/local. Now whenever you want to interact with it, you can run arch -x8664 brew. If you want to wait for official support for Apple Silicon, feel free to stop reading here. Multiple Homebrews. Homebrew does sorta work on Apple Silicon. See this issue for the current status. OpenJDK and Go don.
by Stephen Wozniak
Stephen Wozniak is the designer ofthe Apple II computer and cofounder of Apple Computer Inc.
Without computerclubs there would probably be no Apple computers. Our club in theSilicon Valley, the Homebrew Computer Club, was among the first of itskind. It was in early 1975, and a lot of tech-type people would gatherand trade integrated circuits back and forth. You could have called itChips and Dips. We had similar interests and we were there to helpother people, but we weren't official and we weren't formal. Ourleader, Lee Felsenstein, who later designed the Osborne computer, wouldget up at every meeting and announce the convening of 'the HomebrewComputer Club which does not exist' and everyone would applaud happily.
The theme of the club was 'Give to help others.'Each session began with a 'mapping period,' when people would get upone by one and speak about some item of interest, a rumor, and have adiscussion. Somebody would say, 'I've got a new part,' or somebody elsewould say he had some new data or ask if anybody had a certain kind ofteletype.
During the 'random access period' that followed, youwould wander outside and find people trading devices or information andhelping each other. Occasionally one guy would show up and say, 'Isthere anyone here from Intel? No? Well, I've got some Intel chips wewant to raffle off.' This was before big personal computer firms andbig money considerations. There was just one personal computer then,the Altair 8800, based around the Intel 8080 microprocessor.
The Apple I and II were designed strictly on ahobby, for-fun basis, not to be a product for a company. They weremeant to bring down to the club and put on the table during the randomaccess period and demonstrate: Look at this, it uses very few chips.It's got a video screen. You can type stuff on it. Personal computerkeyboards and video screens were not well established then. There was alot of showing off to other members of the club. Schematics of theApple I were passed around freely, and I'd even go over to people'shouses and help them build their own. The Apple I and Apple II computers were shown offevery two weeks at the club meeting. 'Here's the latest littlefeature,' we'd say. We'd get some positive feedback going and turnpeople on. It's very motivating for a creator to be able to show what'sbeing created as it goes on. It's unusual for one of the mostsuccessful products of all time, like the Apple II, to be demonstratedthroughout its development.
Today it's pretty obvious that if you're going tobuild a billion-dollar product, you have to keep it secret while it'sin development because a million people will try to steal it. If we'dbeen intent on starting a company and selling our product, we'dprobably have sat down and said, 'Well, we have to choose the rightmicroprocessor, the right number of characters on the screen,' etc. Allthese decisions were being made by other companies, and our computerwould have wound up being like theirs-a big square box with switchesand lights, no video terminal built in . . .
We had to be more pragmatic. The 6502microprocessor, for instance, was chosen for one reason only. It wasthe first one to sell over the counter for $20. The 8080 cost $370 atthe time, and you couldn't get it at any surplus stores. You had to godown to a distributor, and they made you feel like you had to be acompany with an account. It wasn't set up for hobbyists orexperimenters.
Steve Jobs was a friend of mine from high school. We were introducedbecause we had two things in common: electronics and pranks. It turnedout that he had a tremendous drive to start a company. He had worked atAtari and had become friends with some of the key people there,including Nolan Bushnell, the founder. Nolan was his idol. Steve wantedto have a successful product, go out and start selling it, and makesome money. He also had excellent product ideas for the upcoming homepersonal computer.
To produce the Apple I, Steve and I formed apartnership. We didn't sell very many Apple Is the first year. We builtthem at night in our garage. At first we expected to sell circuitboards at the Homebrew Club: just put in your own chips and it'll work.Then we got a $50,000 order from a local store and we were in heaven.
The trouble was how to get the money to build ahundred computers-they might cost over a hundred dollars each to build.Steve went to a local parts supplier and talked them into giving us alot of parts on thirty days' net credit. It was very unusual for themto give us credit, because we didn't own anything. We didn't ownhouses. We didn't even own our cars. But Steve is very persuasive. We'dget the parts and then stuff them into the circuit boards, have themsoldered, get them back in the garage and test them. And we could turnthe whole cycle around in ten days and get paid. It worked really greatbecause we had only one level of management.
We got our names established. The computer magazinesstarted carrying lists of all the microcomputers coming out, and they'ddescribe all the characteristics-how much memory, which processor, wasit assembled or was it a kit, what was its price. The Apple I had agood appearance, and we were always at the top of the lists becausethey were in alphabetical order.
After the Apple I was out, we tried to add newfeatures. We thought about color and maybe some high-resolutiongraphics. I found ways to optimize and combine different parts of thecircuits and make things with fewer chips. It's great to show off at aclub that you use fewer chips than someone else. I did it for no otherreason.
The Apple II came out of trying to improve the AppleI. From thinking out a way to make it with half as many chips, youcould have a much better product. It was faster, it had color, it hadhigh-resolution graphics, it had mixed modes on the screen with text. Alot of neat features made it look like this might be a nifty product.It turns out that some of its best features were inspired by whatlittle experience we had.
Steve and I had done a game for Atari-Breakout forthe arcades-before games were on microprocessors. We were running theApple II down at the Homebrew Club, so I thought it would be neat ifyou could write Breakout in BASIC. I added graphics mode commands tothe Integer BASIC I was writing. Breakout needs paddles: I had to add alittle circuitry for paddle and push button. You need sound: when theball hits the bricks, ping; when you lose, ehhhh. So I put a speakerin. All of these features were basically just to play one game.
These turned out to be common features for thepersonal computers that have come out since that time. We weren't quitethe first to offer a keyboard and video output, but we were close. Wewere the first to offer built-in BASIC. We made the first built-incassette port so you could use a cheap cassette recorder to load yourprograms in and store them. We had started to set standards for whathave come to be known as low-cost personal computers.
Just about the only argument on product design Steveand I ever had was on the number of expansion slots. I wanted eight andhe wanted two. I was for eight simply because I'd been aroundminicomputers that had a lot of extra function boards plugged in. Stevefigured people would only use maybe a printer and a modem, and that wasit. Fortunately we went with eight, because the Apple II'sexpandability was important to its success.
When we geared up to manufacture the Apple II, itlooked like I'd have to leave my nice secure job at Hewlett-Packard. Ithought about it and said no. I just loved going down to the HomebrewComputer Club, showing off my ideas and designing neat computers. I waswilling to do that for free for the rest of my life. Steve gotextremely anxious. He got all my friends and relatives to start phoningand tell me why I was making a mistake. Finally one of them called andsaid you can start a company, remain an engineer and also get rich. Idecided that you can start a company and make money. Once I got theconsciousness right, it was easy to quit HP and take this big risk.
We got our first ad agency and began discussing whowe were and what our product was and how we would market it. Of course,to a marketer Apple was an odd name. It came from the days when youpicked an interesting, fun name for a company. You do that when you'reon a hobby basis. The ad agency kept telling us the name had to bechanged. We had to have a name that suggested technology, numbercrunching, calculations, data bases. We took the attitude that Apple isa good name. Our computer would be friendly-everything an applerepresents, healthy, personal, in the home. We had to hold our groundon that one. The agency designed our color logo. (Our original logo wasNewton under the apple tree.) Steve twiddled the colors around and kepta rainbow orientation.
|COMPUTER GROUP GUIDE|
One of the mostcomplete listings of user groups can be found in the annual ClassroomComputer News Directory. Originally intended for teachers, this200-pagedirectory provides a wealth of information for general users on allaspects of computing, including sets of guidelines for hardware andsoftware selection as well as a complete Yellow Pages of computerservices and products.
The directory is available from Classroom ComputerNews, 341 Mt. Auburn St., Watertown, MA 02172. Telephone: (617)923-8595.
We introduced the Apple II at the First West Coast Computer Faire. Thefirst computer shows were informal, not like the professionallyoriented shows we have today. They were more an outgrowth of computerclubs. We got a lot of our initial support from these clubs. I startedspeaking at them whenever I was invited, and I've been doing it fromthat day on. I travel at my own expense because I think it's excitingto tell the story of how our company sprang up from a club.
Our success was due to a number of factors. First ofall, we had never manufactured computers before. We couldn't look backand say, 'Here's how computers earned a lot of money in the sixties andseventies, that's the style to do.' All we thought about was what wasgoing to work out great in our own homes. Our motivation was what wouldbe good in the end. If there was a known formula for what would make asuccessful product, and what would make a billion dollars, all the bigcompanies would have jumped on it. All these companies were a lotsmarter than us. What we had was luck. We did the right things with theright coincidences of timing and the right people in the right place.
We had a lot of interest and enthusiasm. The rewardsthat drove us were all intrinsic. The computers were being put togetherto show off at a computer club: 'Look at this. I put in these neatcommands.' It's not like you get a better salary, or a better title, ormore respect at work, or a new car. We had the autonomy of creators. Wecould decide what was going to make a neat computer. We could implementit, and we could show it off. We also had excellent feedback from ourpeers.
Back then, the small computer scene was based on thebelief that we were all on top of a revolution. Everyone attending theclub in 1975-76 knew there was a big computer revolution occurring andthe rest of the world wasn't aware of it yet. That's why there was somuch excitement and spirit. We were finally going to get control of ourown computers. It wasn't a million-dollar thing that belonged to thecompany you worked for. This big thing that had so much value, and thatwe wanted to use and control, we finally were getting close to. Look athow many companies have sprung out of our Homebrew Computer Club. Atlast count, it was something like twenty-one! We managed to bring thecomputer revolution home.
GEORGE S. ZARR, JR., Renaissance man and computer professional
After reading all the raving reviews online about the new Apple M1-based Mac computers, and after losing too much time with my overheating MacBook Pro 2013 that’s on its last legs, I caved and bought a Mac Mini M1.
☑️ Apple 30″ Cinema display (2013)
I made the mistake of thinking that any USB hub with a Mini Displayport connector would work with my Cinema display. But apparently, not all such ports are also Thunderbolt 2, as I found out with my Satechi hub.. Fortunately, Apple sells a 55 euro Thunderbolt 3 (with USB-C connector) to Thunderbolt 2 (with mini Displayport connector), and it works perfectly. This already takes 1 of the 2 USB-C ports on the Mac Mini.
☑️ Homebrew in native mode
I do a lot of bash/script development so my first concern was getting all of my bash scripts working on the new ARM architecture. I concentrated on bash/terminal in native arm64 mode, which means not running under Rosetta2. This because I want to benchmark in native mode, and I kind of assume that under Rosetta 2 everything works that worked under MacOS for Intel, and where’s the fun in that?
For that, I needed to get the Homebrew package manager running in native mode. The thing is, Homebrew does not yet support the new Apple Silicon M1 chip (they only started the first steps in Dec 2020), so you have to dodge all the warnings they throw at you. After someresearch, I found the best way to do it, and I combined all of it in an easy install/uninstall bash script:** https://github.com/pforret/m1_homebrew** It installs the command-line tools and Homebrew to
/opt/homebrew for arm64 mode, and to
/usr/local for standard i386 mode.
Running it is as easy as:
🤞 brew install –build-from-source
After installation, running
brew install will give you warnings and will often not be able to install the packages, because there are no pre-built casks for Apple Silicon yet.
Still, you can tell brew to install from source code, and compile on your machine by using
brew install --build-from-source (or shorter:
brew install -s). For small packages like
awk, this will do the job. For large packages with lots of dependencies like
ffmpeg, brew will stop for lack of bottles.
☑️ native imagemagick
My first big package to install was
imagemagick. It’s my go-to tool for image manipulation and part of many of my scripts like e.g. splashmark. Imagemagick has lots of brew dependencies for treating different kinds of files, like libpng, openjpeg, webp and ghostscript. Every time brew requires a package that isn’t installed yet, it stops with the error mentioned above. You then have to build that package separately and try the original
brew install again. This is how I got imagemagick compiled in the end.
☑️ m1_homebrew recursive
I automated this process in the same script m1_homebrew.sh.
m1_homebrew recursive imagemagick first looks for all the dependent packages (via
brew info), installs those first one by one and then, at the end, installs the main package. It can take a long time but it’s magic when it works.
😥 no native ffmpeg
Apple Homebrew M1
Unfortunately, it doesn’t always work. I tried it for
ffmpeg, but this package requires some dependencies that will not build on MacOS M1 for now. Concretely:
openjdk cannot be built yet, and ffmpeg requires them.
- rust: hangs on “
arch -x86_64 make” which implies that it’s building a x86_64 (Intel) version instead of a arm64 native version,
- openjdk: “configure: The tested number of bits in the target (64) differs from the number of bits expected to be found in the target (32)“
They are both still marked as ⚠️ on the official Homebrew M1 compatibility list.
Apple Homebrew Arm
Generate individual tag/category/author pages for your Jekyll website
I’ve been migrating more and more of my websites to Jekyll static sites, from Wordpress. The advantages are clear:
My disaster upgrade to LastPass Premium
LastPass has started pushing its free users towards a paid premium subscription. The way they do this is by only allowing the free version for 1 platform, e.g. only your... • 18 Mar 2021
Detecting excessive SSD wear on Apple Silicon M1 machines