I got the m1 max with 64gb ram when it came out. I was looking forward to this event, hoping to upgrade.
If you compare the m1 max to the m3 max; there isn’t much of a difference. It’s got more cores & ram, but that’s about it. 1 hour additional battery life and every else is same.
But why? I also have a 64GB m1max, I can’t imagine wanting to upgrade for the next 3-4 years, even if they did come out with something substantially faster. Moore’s law is dead, I doubt it’ll be much more than 10-15% year on year.
I run VMs. Visual code for mac is buggy, so I run it under windows. Usually I have a couple of projects in parallel and I need ram.
32GB out of the 64GB is allocated to the windows VM and then there’s some other small VMs for intermittent stuff that need to be “sandboxed”.
Why bother with OSX? The base OS is better integrated with the hardware. I’m past that moment in life where you love to tinker & experiment. Now I just want things to work, so I can finish what I want to do. And the battery life is much much better.
I was excited about the 128GB Ram option; but there’s nothing more. Hoping there’s a decent ARM windows laptop out soon with 20 hours battery life.
Your use case is wild. my project also needs 64GB of ram to run, but we moved away from VMs, just docker. m1max builds over twice as fast as our i9 machines did, and m2max was about 15% quicker, but I’m fine with my m1max.
What’s buggy about VS code for you? I don’t use it as a primary IDE but I find it find for lightweight stuff. I’ve just always preferred jetbrains IDEs, if you’re doing .net I strongly recommend giving rider a go.
VS for osx was in “preview” the last 3-4 versions I tried. Things would randomly not work. I would upgrade hoping some bugs were fixed. Some versions were more stable than others. The last version I was trying had a broken “git”, so that pushed me to branch off and commit to the windows VM. (puns intended)
I got the m1 max with 64gb ram when it came out. I was looking forward to this event, hoping to upgrade.
If you compare the m1 max to the m3 max; there isn’t much of a difference. It’s got more cores & ram, but that’s about it. 1 hour additional battery life and every else is same.
But why? I also have a 64GB m1max, I can’t imagine wanting to upgrade for the next 3-4 years, even if they did come out with something substantially faster. Moore’s law is dead, I doubt it’ll be much more than 10-15% year on year.
I run VMs. Visual code for mac is buggy, so I run it under windows. Usually I have a couple of projects in parallel and I need ram.
32GB out of the 64GB is allocated to the windows VM and then there’s some other small VMs for intermittent stuff that need to be “sandboxed”.
Why bother with OSX? The base OS is better integrated with the hardware. I’m past that moment in life where you love to tinker & experiment. Now I just want things to work, so I can finish what I want to do. And the battery life is much much better.
I was excited about the 128GB Ram option; but there’s nothing more. Hoping there’s a decent ARM windows laptop out soon with 20 hours battery life.
Your use case is wild. my project also needs 64GB of ram to run, but we moved away from VMs, just docker. m1max builds over twice as fast as our i9 machines did, and m2max was about 15% quicker, but I’m fine with my m1max.
What’s buggy about VS code for you? I don’t use it as a primary IDE but I find it find for lightweight stuff. I’ve just always preferred jetbrains IDEs, if you’re doing .net I strongly recommend giving rider a go.
VS Code for osx is fine.
VS for osx was in “preview” the last 3-4 versions I tried. Things would randomly not work. I would upgrade hoping some bugs were fixed. Some versions were more stable than others. The last version I was trying had a broken “git”, so that pushed me to branch off and commit to the windows VM. (puns intended)
Oh, lol yeah, I briefly used it before rider. Rider is really just “resharper the IDE”, and VS was always garbage without resharper imo.
I’d never use git in a gui app, it’s well worth learning CLI git well, once you get used to it you never go back.