Has anyone tried using a Wavlink 4K USB-C docking station with the M1? I use it on my intel Mac Pro and windows desktop and it works like a champ.
Onboarding with an M1
121–130 of 165 posts
Re: Onboarding with an M1
#122Earlier quoted context omitted.
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…
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?
Re: Onboarding with an M1
#123Earlier quoted context omitted.
I got 2 LG 4k monitors plugged into my Mac Mini M1, one USB-C (43 inch), and one HDMI (27 inch rotated). In both cases the Mac runs them at 60 hz, the 43 inch slightly scaled and the 27 inch around 1440p scaling. If I put them at full resolution (unscaled) they still run at 60hz.
how deep is your desk to be able to use all that screen real estate? I already suffer eye strain with my 34 4k as it's already too high
Re: Onboarding with an M1
#124Is everyone using the 16GB version of the M1? Or is the 8GB sufficient?
Re: Onboarding with an M1
#125Earlier quoted context omitted.
I switched from brew to macports recently, so here are my thoughts: - 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,…
Interesting observations. Why does Brew seem more secure on first impression?
In reality however, macports uses "privilege separation" which drops privileges for each individual install to a separate "macports" user. This is more secure than brews sudoless approach because not only does the installer not have root access, it doesn't have full access to your own user either (e.g. your HOME). Privilege separation isn't possible without initially having root privileges.
Re: Onboarding with an M1
#126Earlier quoted context omitted.
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…
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?
For context I regularly have open (what I consider to be standard apps):
* IntelliJ IDEA (Pycharm or Clion, never both)
* Slack
* Chrome
* kitty (20 or so terminals)
* Outlook
* yabai & bartender
* littlesnitch & adguard
Re: Onboarding with an M1
#127Earlier quoted context omitted.
> But I am able to run WAY more applications in 8GB than the 16GB intel Mac I had previously. Then your limitation clearly wasn’t RAM.
Memory management is different on the M1. This has been widely discussed.
It can't make it appear out of thin air. If you need 16GB of ram and only have 8GB, you will run out of memory.
Re: Onboarding with an M1
#128I 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…
Homebrew was the cool new kid at the right time, when Macs popularity amongst webdevs was growing exponentially. OTOH, Macports is still working fine; there is room for two package managers on macOS.
Re: Onboarding with an M1
#129I 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
I wasn't able to get it to work, and it left a bunch of users (like ten??) and other various junk which was a pain to clean up. This was in 2017 I think.
I keep hoping someone will chime in and say "I use nix on my Mac, and it's dreamy, everything Just Works you should try it!" because until that happens I'm going to stick with brew.
While I'm on the subject, I was also a macports user until hmm, 2013 I think. Don't recall exactly why I switched, just that I was having some kind of intractable problem, messaged a friend who knows what he's talking about, and he said "just use brew dude". So I did.
Re: Onboarding with an M1
#130Earlier quoted context omitted.
I have completely the opposite experience; brew would screw something up every other time I upgraded a package, and didn't cross OS updates very well at all. MacPorts has been rock-solid, possibly because it is more careful about making sure that ports have exactly the right deps.
Weird. Macports is the one I was always having to edit packages for to un-break them, with a totally normal installation. Seemed like their packages were poorly-maintained. Must have gotten better I guess.