What you need to know
- iFixit has published its initial teardown of the new 16-inch MacBook Pro.
- They wanted to take a good look inside Apple's brand new laptop keyboard mechanism.
- iFixit seems confident that MacBook's woeful keyboard days are behind it.
iFixit has published its initial teardown of Apple's brand new 16-inch MacBook Pro, giving viewers a look inside the new scissor mechanism keyboard, and the internals of the device.
In its teardown, iFixit reports that Apple's new keyboard is very much an improvement on the Butterfly mechanism of old:
Reassuringly, the new keyboard on the 16-inch Macbook Pro has a feel "almost identical" to older, more popular Apple keyboards like the Magic Keyboard. In fact, iFixit notes that the two are so similar, you can actually swap in old Magic Keyboard keycaps onto the new MacBook.
iFixit actually live-streamed its teardown over on YouTube, and you can check out that full video below. The purpose of this initial test was to dive into the internals of the new keyboard, and also catch a quick look inside. The full iFixit teardown is coming on Monday, November 18.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.