Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Onboarding with an M1

authzed.com

Post reply on HN
Print view View original

71–80 of 165 posts

Re: Onboarding with an M1

#71

Post by NetOpWibby »

barkingcat wrote: post #46
nsxwolf wrote: post #31

Earlier quoted context omitted.

A lot of people missed it. No one expects features to be removed from the latest and greatest model.

It's called wishful thinking with blinders. What? The M1 MacBook Pro is not the magical device with no compromises??? People were way too enthusiastic and purposely skipped over any weaknesses of the form factor. People were claiming that it was capped at 16G ram because there were no purpose for having 32G ram (it was amazing to see the hacker news technical set reclaim Bill Gate's "640K ought to be enough for anybo…

Thank you

Re: Onboarding with an M1

#72

Post by havernator »

tastyminerals2 wrote: post #66

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.

Re: Onboarding with an M1

#73

Post by supermatt »

eertami wrote: post #69
supermatt wrote: post #50

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.

So why did you buy one?

Re: Onboarding with an M1

#74

Post by asimpletune »

tastyminerals2 wrote: post #66

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…

Or for that matter I’m looking forward to learning more about nix which promises sort of the holy grail in these matters

Re: Onboarding with an M1

#75

Post by runjake »

mistersquid wrote: post #63
clashmoore wrote: post #2

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…

I understand the lack of multi-monitor support in the M1s is an issue. But just after the launch of the M1, I came across a video that demonstrated an M1 Mac mini driving six monitors. [0] There is also a short write up about that workaround, for those who don’t want the video. [1] There are similar workarounds for the M1 MacBoooks. [2] Is this a reasonable workaround until Apple provides M1 hardware that can run mor…

#2 is using a DisplayLink device to run multiple monitors. I presume the other videos do too.

There's no trick or way around this on an M1-equipped Mac. Something else will be handling the graphics.

DisplayLink generally works excellent for running most apps. It does not work well where you’re pushing a bunch of bits at the screen rapidly, eg. First person shooters or high definition video.

That said, one of my DisplayLink monitors is used for IP camera feeds, and while the little traffic light on the USB dongle is blinking incredibly fast, I don’t notice any stutters.

Everyone already knows about this and the author mentions this in their post.

Re: Onboarding with an M1

#76

Post by supermatt »

barkingcat wrote: post #54
supermatt wrote: post #50

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?

Yes I am using one. There are workloads that don't fit into 16G ram. Even with paging, there are legitimate needs for 32G and beyond memory sizes.

What specific workloads? If you bought a 16GB machine to keep 32GB of data in RAM then clearly you bought the wrong machine. But I am able to run WAY more applications in 8GB than the 16GB intel Mac I had previously.

Re: Onboarding with an M1

#77

Post by hedgehog »

clashmoore wrote: post #2

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…

There are also compatibility issues with ultrawide monitors and DDC support is missing (so there's no way to do brightness or volume for external displays). The new machines are still better for most people but as always evaluate before upgrading.

Re: Onboarding with an M1

#78

Post by fiddlerwoaroof »

tastyminerals2 wrote: post #66

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 because it goes out of its way to avoid breaking your system. I recently gave macports another try and the experience involved editing Portfiles over and over again to try to get applications to work.

The most common complaint (changing permissions on /usr/local) isn’t a problem with the arm64 version which now uses /opt/brew but, also, as far as my trust model goes, it isn’t a problem for me: I already have $HOME/bin on my path and, so, any local exploit that relies on overwriting system executables has multiple ways of tricking me into running a malicious program.

Re: Onboarding with an M1

#79

Post by stu2b50 »

Jcowell wrote: post #52
f6v wrote: post #47

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)

(Not OP btw)

While I'm not sure if it's building from source or pulling a binary, just pip3 install pandas seems to work just fine. Not a Rosetta terminal.

Just ran a fresh install from a new poetry venv, seemed to work fine. This was the poetry output

Using version ^1.2.4 for pandas

Package operations: 3 installs, 0 updates, 0 removals

  • Installing numpy (1.20.2)
  • Installing pytz (2021.1)
  • Installing pandas (1.2.4)

Re: Onboarding with an M1

#80

Post by e-clinton »

FroshKiller wrote: post #36
nsxwolf wrote: post #31

Earlier quoted context omitted.

A lot of people missed it. No one expects features to be removed from the latest and greatest model.

No one expects a brand-new hardware platform to have different capabilities from other devices in its class?

It’s not “brand new hardware”, it’s just another MacBook Pro. Being a MacBook Pro, I expect a keyboard, trackpad, screen... and the ability to plug-in monitors, just like every other MacBook Pros has for however many years.

They shouldn’t have called it a pro.

Post reply on HN