61–70 of 244 posts
Do ARM compatibility issues still exist?
I have an M1, and I was unable to install tensorflow in a docker container on the M1 host (as of last time I tried, a few months ago).
which is the right one to get, 14 or 16?
14: pro - lighter con - less screen for multiple windows
16 pro - multiple windows side by side, longer battery lift con - 5 pounds, won't fit in backpack
Do ARM compatibility issues still exist?
Of course. Any time you try to run a non-ARM binary on an ARM CPU without some form of translation or emulation, it will fail. This is also true for any other CPU architecture. If you want to know about specific compatibility issues, I'm happy to try to help as I've been using an M1 Air as my daily driver for many months now.
Much has already been said about this, but this achievement of shipping a MBP that pro users seem to love is a triumph of user feedback over design purity. I suspect that Jony Ives’ departure may have facilitated this. I suspect it will be a breakout success and I aspire to contribute to their sales figures some day. Of all of Apple’s revenue streams I know their pro products are now merely an afterthought, but they…
I'm sure that is a very accurate statement. I thoroughly enjoy the improvements to the keyboard and adding back in the new ports. But I wonder what the future of the MacBook will be without the visionary design from Ives? Are we going to see a melding of PC and Macs or will Apple keep design innovation at the forefront?
Earlier quoted context omitted.
1. You can still charge over USB-C. (The 16" cannot charge at full speed over USB-C, because it charges at 140W which is more than USB PD can currently deliver. But it will still charge to full, just slower.) 2. The other side of the cable is USB-C.
If 140MW is more than USB PD can deliver, then how can the other side of the cable be USB-C?
Guessing they can only do 3.0 on the data ports for now and the MagSafe connector is just USB PD 3.1 implementation without any possibility for data.
Earlier quoted context omitted.
1. You can still charge over USB-C. (The 16" cannot charge at full speed over USB-C, because it charges at 140W which is more than USB PD can currently deliver. But it will still charge to full, just slower.) 2. The other side of the cable is USB-C.
If 140MW is more than USB PD can deliver, then how can the other side of the cable be USB-C?
The MagSafe 3 cable goes from 140W USB-C to MagSafe, but the USB-C charger is 100% standards-compliant USB-C EPR.
[0]: https://www.reddit.com/r/UsbCHardware/comments/qat7ej/new_ap...
Earlier quoted context omitted.
OpenGL still works on the M1 (Apple designed their own GL-over-Metal driver), albeit with the OpenGL version limitations from modern macOS in general. Vulkan works over MoltenVK. Other than old games, I'm not sure why 64-bit only is an issue. I've not hit any Docker-on-macOS issues with what I've used it for, at least.
Is MoltenVK usable right now? I was under the impression that it's a loooooooong ways behind DXVK in it's current state.
> It will probably take a little while for Mac apps to be updated to support the ProMotion display. I found that some apps scrolled text in the same buttery-smooth way that apps do on my iPhone and iPad, but others didn’t. I was able to find a few Catalyst-based apps that have already been written to support 120Hz displays on iPad and iPhone, and they looked spectacular. It surprised me that an app would have to be u…
They could, if they wanted, automatically opt existing applications to use 120 Hz refresh. But the power usage would be terrible, and it would be up to application authors to manually go in and tune it down (which many would not do, or would take too long).
So instead they keep them at the current refresh, and have them "opt-in" to higher. Which I'm imagining Apple is hoping application developers will do responsibly and only ask for 120 Hz when it is beneficial (although big YMMV).
Glad to hear that about the notch. I couldn't for the life of me think why it mattered. When the presentation showed it, I looked at the very display of the Mac laptop I was watching it on and sure enough, there was a gap in the menu bar where the notch would be, with the menu items on the left and the clock and all those little widget icons on the right. I was streaming it on my personal 2013 MacBook air (which is a great little machine but ready for an upgrade), and then glanced at my work Macbook Pro and its external display. On both those, there was also empty space where the notch would be. I thought, wow, what a great idea.
But then I saw all these comments about how it was horrible and a deal breaker, and some designer pompously talking about how when you're like him and pay close attention to detail it will be distracting, I thought either everyone had lost their collective mind, or I was missing something. I realize there are some apps with a lot of menu items which might have to oddly flow to the other side, but I don't think that's super common, and I guess I'll just have to see how it feels in the end. But glad that this reviewer isn't bothered by it.
Earlier quoted context omitted.
I don't think I've ever had an issue related to Rosetta2. Everything I had to run on it worked flawlessly and without any noticeable performance hit. This is only my own anecdote though.
I also had everything working fine but performance is really bad when you go through rosetta. For example, discord client is still x86 and while it works without any issues, the heaviness is noticeable. Also, .NET 5 does not have an arm build (.NET 6 does but it is still in beta). The entire toolchain works but compiling a binary can be 3-4 times slower on the emulated one. Things work without any issues though. They…