81–90 of 165 posts
As mentioned in the epilogue regarding single monitors, I feel that Apple was a little too silent regarding that limitation. It also caught me off guard especially as I purchased the LG 4K thunderbolt/usb-c monitors from the Apple website with the hope of connecting everything via daisy chain. I haven’t yet definitively found a DisplayLink hub that can output its video via thunderbolt and/or USB-C so whenever I see a…
Earlier quoted context omitted.
I’m not aware of anyone (except those using VMs) who are complaining about the memory. I personally went from 16gb to 8 and don’t miss it. Do you actually own/use an m1 Mac?
If it works for you, it works for you. However in 2021 I am not interested in a computer with less than 32GB ram. Sure, I could work around the limitations and close not in use programs/tabs to avoid going OOM, or using swap, but life is short and memory is cheap. I'd rather not have to worry about it.
I've been hoping for years that they would start supporting Linux, but I've settled with the fact that this won't happen.
If one year ago one would have asked NI if they plan to support ARM chips, they would probably have laughed at you, but I'm sure that they now have already started working on this, now that Apple has forced them to.
I always wonder why ppl do not use MacPorts? There was a great article on HN which basically drew a pretty clear picture how brew can easily mess your system up. Yet, being a new Mac user, wherever I go, I only see a reference to brew installs. I am using M1 for a over a month and it’s been a very smooth ride so far. Installing everything via MacPorts where I only had an issue with rabbitmqd which failed to build bec…
I switched to Brew back in... oh, 2012 or 2013, I think, because I was sick of MacPorts breaking itself horribly during normal operations (installing/uninstalling) every 3-6 months. Brew’s huge package selection, rare breakage (sometimes on OS upgrades, usually easy to fix), decent UI, and ability to also manage nearly all the closed-source software I install, have kept me from bothering to look at MacPorts again.
At that point in time I was a lot less technically capable, so on the rare occasion googling the issue would turn up a relevant mailing list archive, I usually wasn't able to act on it and I'd wind up procuring the package in question through some other method or just doing without.
So when Homebrew came along and most things installed and ran fine with the rare issue that cropped up getting fixed fairly quickly, it easily stuck.
I always wonder why ppl do not use MacPorts? There was a great article on HN which basically drew a pretty clear picture how brew can easily mess your system up. Yet, being a new Mac user, wherever I go, I only see a reference to brew installs. I am using M1 for a over a month and it’s been a very smooth ride so far. Installing everything via MacPorts where I only had an issue with rabbitmqd which failed to build bec…
- before, I had generally heard of homebrew a lot, and macports very little. Brew's marketing is better. I think this is intentional (as in Macports doesn't really do any)
- The docs for macports are very poor. They are comprehensive, but barely navigable. Keyword search doesn't work well. They're obtuse.
Further context: I also find brew docs poor, but they're much more user-focused (how to install packages), whereas macports' seem more packager-focused.
- Requiring sudo is a security feature, but Macports doesn't advertise this well, so brew "seems" more secure on first impression
- Most software with cli install instructions recommend brew up top (even when there's a macports option). i.e. there's no evangelization of macports by maintainers who package for it. I don't really know why this is, but it's something macports maintainers could/should look into.
Also commenting on single monitor support - a key note I missed from original reviews and maybe a reason to wait till more pro models come out?
Something that's been missed a lot, I think, is that the Intel-based 13" MacBook Pro actually came in two versions -- a two-port one with a less-capable, low-power processor and a lot of limitations that made it more like a juiced-up Air, and a four-port one which was much more like the 15" MBP. The current M1-based MBP is direct replacement for that two-port model, and is now absolutely just a juiced-up Air; there's very little that the M1 MBP does that the M1 Air doesn't.
And, yes, the Intel version of the MacBook Pro But Really Juiced-Up Air, or MBPBRUJUA for short, could run two external 4K displays or one external 5K display, while the M1 MBPBRUJUA can only run one external display (although for the ones and ones of you out there with 6K displays, good news!). I would presume Apple knows this is a regression and plans to address it, at least when they update the four-port MBPs.
Personally, I'm not convinced the MBPBRUJUA is going to stay around past this product cycle; it's always struck me as a laptop in sort of a weird middle space, too big to make people who really want an Air happy but not "pro" enough to make, well, actual pros happy, and the shift to Apple Silicon brings the Air and the MBPBRUJUA so close together the only material difference is the case design. I can't help but suspect that the only reason we have an M1-based MBPBRUJUA is so Apple could tick off the "shipped an ARM-based laptop with a MacBook Pro nameplate in 2020" box.
Earlier quoted context omitted.
Pandas works fine for me. But it’s a moderately sized data, below 100k rows. Dask works as well, though I can’t judge the speed.
How did you install pandas without any work around? (Mini forge, building from source, making a Rosetta terminal)
I wonder how much extra work Apple is generating audio companies like Native Instruments. I've been hoping for years that they would start supporting Linux, but I've settled with the fact that this won't happen. If one year ago one would have asked NI if they plan to support ARM chips, they would probably have laughed at you, but I'm sure that they now have already started working on this, now that Apple has forced t…
Proportional to the business they expect to get from M1/Arm.
>I've been hoping for years that they would start supporting Linux, but I've settled with the fact that this won't happen.
They'd have to have their codebase already compatible by a huge percentage (like BitWig, which was a fresh start from ex-Ableton folks) for that to happen (that is, it would have to require minimal effort to do it as a good will gesture that costs them nothing to just build and offer for the ocassional buyer).
Else, it would be lots of effort not really justified by expected sales (as only a tiny share of musicians use Linux, and they're generally not the "buying commercial DAWs/VSTs types").
I always wonder why ppl do not use MacPorts? There was a great article on HN which basically drew a pretty clear picture how brew can easily mess your system up. Yet, being a new Mac user, wherever I go, I only see a reference to brew installs. I am using M1 for a over a month and it’s been a very smooth ride so far. Installing everything via MacPorts where I only had an issue with rabbitmqd which failed to build bec…
I always wonder why ppl do not use MacPorts? There was a great article on HN which basically drew a pretty clear picture how brew can easily mess your system up. Yet, being a new Mac user, wherever I go, I only see a reference to brew installs. I am using M1 for a over a month and it’s been a very smooth ride so far. Installing everything via MacPorts where I only had an issue with rabbitmqd which failed to build bec…
I switched to Brew back in... oh, 2012 or 2013, I think, because I was sick of MacPorts breaking itself horribly during normal operations (installing/uninstalling) every 3-6 months. Brew’s huge package selection, rare breakage (sometimes on OS upgrades, usually easy to fix), decent UI, and ability to also manage nearly all the closed-source software I install, have kept me from bothering to look at MacPorts again.