▲ 173 ▼ 8GB RAM in M3 MacBook Pro Proves the Bottleneck in Real-World Tests (www.macrumors.com) submitted 2 years ago by throws_lemy@lemmy.nz to c/technology@beehaw.org 62 comments fedilink hide all child comments
[–] interolivary@beehaw.org 15 points 2 years ago (1 child) Heh, an optimist here assuming Chrome will work with 8Gb RAM in 2033 permalink fedilink source parent hideshow 2 child comments replies: [–] abhibeckert@beehaw.org 2 points 2 years ago (1 child) It does. I have 16GB on my Mac, and half of it is given over to a virtual machine running Linux. Chrome (and 20 or so other things) runs fine on the remaining 8GB. permalink fedilink source parent hideshow 2 child comments replies: [–] interolivary@beehaw.org 12 points 2 years ago (1 child) Interesting. How are things in the year 2033? Could you tell us about the technology you're using to communicate with us? permalink fedilink source parent hideshow 2 child comments replies: [–] rwhitisissle@beehaw.org 8 points 2 years ago That's probably what the VM is doing: it's self-hosting a server running timemachined. timemachined itself is actually running out of a docker container that's running on the VM, but that's because by 2033 every single update, which occur daily, breaks the existing docker installation on a Mac. Which is honestly very similar to what happens in 2023, except it's every other day currently. permalink fedilink source parent
[–] abhibeckert@beehaw.org 2 points 2 years ago (1 child) It does. I have 16GB on my Mac, and half of it is given over to a virtual machine running Linux. Chrome (and 20 or so other things) runs fine on the remaining 8GB. permalink fedilink source parent hideshow 2 child comments replies: [–] interolivary@beehaw.org 12 points 2 years ago (1 child) Interesting. How are things in the year 2033? Could you tell us about the technology you're using to communicate with us? permalink fedilink source parent hideshow 2 child comments replies: [–] rwhitisissle@beehaw.org 8 points 2 years ago That's probably what the VM is doing: it's self-hosting a server running timemachined. timemachined itself is actually running out of a docker container that's running on the VM, but that's because by 2033 every single update, which occur daily, breaks the existing docker installation on a Mac. Which is honestly very similar to what happens in 2023, except it's every other day currently. permalink fedilink source parent
[–] interolivary@beehaw.org 12 points 2 years ago (1 child) Interesting. How are things in the year 2033? Could you tell us about the technology you're using to communicate with us? permalink fedilink source parent hideshow 2 child comments replies: [–] rwhitisissle@beehaw.org 8 points 2 years ago That's probably what the VM is doing: it's self-hosting a server running timemachined. timemachined itself is actually running out of a docker container that's running on the VM, but that's because by 2033 every single update, which occur daily, breaks the existing docker installation on a Mac. Which is honestly very similar to what happens in 2023, except it's every other day currently. permalink fedilink source parent
[–] rwhitisissle@beehaw.org 8 points 2 years ago That's probably what the VM is doing: it's self-hosting a server running timemachined. timemachined itself is actually running out of a docker container that's running on the VM, but that's because by 2033 every single update, which occur daily, breaks the existing docker installation on a Mac. Which is honestly very similar to what happens in 2023, except it's every other day currently. permalink fedilink source parent