Thought it'd be appropriate to plug what we're working on here. We're a YC company (W19) are building an iOS browser that's extensible. You can build "extensions" to inject your own JS into pages if they match a certain condition.
I run a Chrome extension that's popular here on HN, called BeeLine Reader. We have an iOS app (and share/action extensions) and have toyed with the idea of building a general-purpose web browser, but we'd much rather be part of an extensible mobile browser. Would love to chat about how you're attacking this problem (and avoiding related App Store prohibitions)!
I think I'm going to manually build things from source until Homebrew officially supports M1 and Big Sur. I don't want to deal with any sort of migration / funky re-install, personally.
Homebrew distributes prebuilt binary packages. It’s possible that the architecture for this is improperly set up and does not understand that different architectures exist: unlike macports, homebrew was born after the x86 transition.
That’s why one user above suggests `-s`: it forces a compilation from source.
The problems with homebrew packages at present are mostly down to projects like Go and Rust not being updated for M1 ARM yet and hence sources not compiling properly rather than a problem with homebrew itself. So users attempting to compile from original upstream sources would run into similar problems.
That approach has always ended badly in my experience because your manual installs will require more care to remove than the Hombrew ones. My usual recommendation is to install anything which supports it using --HEAD which will keep things tracked and make it trivial to either completely uninstall or simply use "brew reinstall" packages after the upstream stabilizes.
> I don't want to deal with any sort of migration / funky re-install, personally.
Isn't the benefit of Homebrew that it all goes into /usr/local and it can just blow everything away if necessary? You could run `brew leaves` to see what packages you have, uninstall everything, and reinstall. Easier than keeping track of what you've manually installed where.
In the short run yeah. You have a point. I intend to uninstall & reinstall everything once Homebrew is officially supported though, which isn't a big deal for me (and I actually kind of enjoy building from source just for the experience).
But these replies are making me think that a large part of my decision to do this is motivated by me just not understanding Homebrew well enough (e.g. how easy it is to nuke everything). Oh well, we'll see how it goes.
i think i’m in a very similar situation, thanks for putting it into words. i’m not doing great but it’s ok. it doesn’t feel good, but it doesn’t feel bad either
That’s why I got the Pro (also my laptop is from 2013 and I’m desperate). I love and use Docker every day, and know it’s a mess right now, but I’m still excited to jump in head first.
Edit: This is my personal laptop fwiw. My work one is still Intel.
What is the difference between the M1 Air and the M1 Pro 13"? From what I can tell, they are basically the same spec except for small differences like slightly bigger battery life, active cooling and touchbar in the Pro.
Form factor is similar. Brightness is better as stated. I believe you get better speakers in the Pro, the charger is higher wattage and the GPU in the high end air and Pro is 8 cores while the GPU on the base Air is 7 cores.
Yep. My new work laptop only has 16GB of RAM and it’s never been an issue. I’m usually running half a dozen containers, VS Code, Slack, Brave/Chrome, and a few other things. Maybe our work loads are just computationally lighter than some?
I ordered a 16GB Pro the other day to be my personal dev machine. I’m sure it’ll be more than fine. I’m upgrading from a 2013 8GB Pro which was only just starting to slow me down.
The code and compilation for me is the light part, and for the most part an hour's worth of essentially text editing for about a moment of compilation anyways.
My resource hogs are slack, mainly the browser, and Zoom calls are apparently the most computationally intensive thing in the world, especially if you screen share while you have an external plugged in.
Memory wise the reason I had to go from 8Gb to 16GB on my personal laptop was literally just for TravisCI.
Honestly, adding external monitors cripples MacBooks pretty quick, even unscaled 2 2k monitors will slow a 2015 15 down significantly (don't try and leave YouTube on either), and it gets worse from there once you start upgrading to 4k monitors. a 2017 15 is good for a 4k and a 2k, and gets a bit slow if you try and go dual 4k.
I planned on looking into eGPU solutions until IT offered me a new Macbook, and I convinced them I needed a 16" Pro.
tldr: External monitors or badly optimized applications (Zoom, YouTube, or browser based CI) will make most MacBooks feel sluggish pretty quick.
Are those displays in scaled mode? Scaled displays tend to perform badly on integrated graphics, and suck up memory, because it has to render a 2x or 3x size internally and then scale down for every frame. Running something that updates the screen constantly, like zoom, probably exacerbates that issue.
