Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MacBook Pro 14-inch and MacBook Pro 16-inch

apple.com

Post reply on HN
Print view View original

971–980 of 1001 posts

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#971

Post by WhompingWindows »

shortstuffsushi wrote: post #504
mizzack wrote: post #92

Wow looks like Apple has abandoned every bad decision on the MBP for the past 5 years in one swoop. No touchbar, increased key travel, added back hdmi/sd/headphone/power jacks. Plus bumped up RAM limit, M1, new displays, 120Hz... Wow.

As someone who bought a mid-2018 with the escape key on the touchbar, then watched the next model have it's own key, then watched all these ports get added back... I'm extremely frustrated to say the least. Trade in is valued at $840. If I had known either of these two updates would have gone " backwards " like this, I would have waited to purchase

Seems Apple loves to Think Different every couple of years. They make these paradigm shifts so quickly, it's a blessing and a curse.

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#972

Post by lanna »

ksec wrote: post #118

HDMI, SD Card, and MagSafe. Things people on the internet inclusive but not limited to HN said they will never come back because the future is USB-C. Now I just want to know if the new keyboard has more key travel distance back to the like of MacBook Pro 2015. In case anyone wants to know the thickness difference. MacBook Pro 13" 2015 - 1.8 cm MacBook Pro 13" 2016 - 1.49 / 1.55 cm MacBook Pro 14" / 16" 2021 - 1.55 /…

> 3456-by-2234 or 3024-by-1964 is 14:9 Ratio

If we subtract 74 pixels from their heights, we get 3456 by 2160 and 3024 by 1890, both of which are 1.6. So I'm guessing the notch is 74 pixels high?

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#973

Post by jagger27 »

adam_arthur wrote: post #478
sergioisidoro wrote: post #412

A fair warning to developers: You're getting into an adventure with M1. From docker images not built for M1 with segmentation faults on qemu (eg. Liquibase for spring developers), to _significant_ troubles trying to make React native apps build with the M1 and XCode. Don't get me wrong, I have a Macbook air M1 and I love it, but it hasn't been a love without pain. Also, the magsafe feels like it comes too late. Almos…

Is there any reason Apple couldn't implement a magsafe type connector but using USB-C form factor? By that I mean, you could use any USB-C compatible cable in the same port (just without the magnetics) It seems like they could have gotten the best of both worlds that way. Am I taking crazy pills?

USB-C is already a friction fit. Somehow adding magnets to it would just make it attach more strongly, which isn't the point of MagSafe. I feel like making a slightly loose USB-C cable but with magnets would be a bad user experience, and probably against the USB spec.

I don't really get what you're suggesting.

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#974

Post by Eugeleo »

tmellon2 wrote: post #875

Does anyone have a handle on how the new M1X is expected to perform on Deep Learning training runs vs a NVIDIA 1080Ti / 2080Ti. I think the 400 Gbps bandwidth and 64 GB unified memory will help - but can anyone extrapolate based on the M1 ?

If you find out, let me know! I'd love to know this, too.

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#976

Post by nicbou »

diebeforei485 wrote: post #645
ksec wrote: post #118

HDMI, SD Card, and MagSafe. Things people on the internet inclusive but not limited to HN said they will never come back because the future is USB-C. Now I just want to know if the new keyboard has more key travel distance back to the like of MacBook Pro 2015. In case anyone wants to know the thickness difference. MacBook Pro 13" 2015 - 1.8 cm MacBook Pro 13" 2016 - 1.49 / 1.55 cm MacBook Pro 14" / 16" 2021 - 1.55 /…

Agree- I have been largely disappointed by USB-C. It's been okay as a smaller USB-A replacement for flash drives and mice, but in general the lesson of USB-C is: just because it fits, doesn't mean it works. My personal favorite annoyance is how chargers and cables are advertised with the wattage they support, but it's really the voltage and current that matters. If you have a device that wants 20W as 9V/2.22A , your…

I'm honestly really happy with USB-C. My phone, laptop and tablet charge the same way. I bring one charger and two cables, so I can pack much lighter than before. Each device can serve as a power bank for the others. My monitor serves as a powered hub, so there's only one cable connecting everything to my laptop. I use the same charger for everything from my camping lantern to my computer. I don't have a big box of cables anymore, nor do I pack 5 different cables when I'm on the move. It's very convenient.

It only becomes a problem when I leave my bubble. I usually travel without my adapters, so I can't borrow someone's mouse, or plug something into their TV.

Then there's the issue with cables and chargers. I have thick cables and 100W chargers, so it's never a bother, but it's not a trivial thing for the average user to make sense of.

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#977

Post by nomel »

adam_arthur wrote: post #478
sergioisidoro wrote: post #412

A fair warning to developers: You're getting into an adventure with M1. From docker images not built for M1 with segmentation faults on qemu (eg. Liquibase for spring developers), to _significant_ troubles trying to make React native apps build with the M1 and XCode. Don't get me wrong, I have a Macbook air M1 and I love it, but it hasn't been a love without pain. Also, the magsafe feels like it comes too late. Almos…

Is there any reason Apple couldn't implement a magsafe type connector but using USB-C form factor? By that I mean, you could use any USB-C compatible cable in the same port (just without the magnetics) It seems like they could have gotten the best of both worlds that way. Am I taking crazy pills?

You can find these on amazon, for example:

https://www.amazon.com/Ansbell-Magnetic-Adapter-Transfer-Com...

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#978

Post by interestica »

smoovb wrote: post #16

Kills the touch bar, the light touch keyboard, adds back weight, card reader, ports and the mag safe. Feels like an apology for prior design decisions. My 2011 MBP is new again!

I recently got a new M1/MBP and really love the utility of a customized TouchBar (using BetterTouchTool). I'm sad it'll be gone! It's actually great - but certain functions are missed (like a dedicated volume buttons).

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#979

Post by interestica »

syspec wrote: post #420
sergioisidoro wrote: post #412

A fair warning to developers: You're getting into an adventure with M1. From docker images not built for M1 with segmentation faults on qemu (eg. Liquibase for spring developers), to _significant_ troubles trying to make React native apps build with the M1 and XCode. Don't get me wrong, I have a Macbook air M1 and I love it, but it hasn't been a love without pain. Also, the magsafe feels like it comes too late. Almos…

You can still charge using USB-C

Which has me wondering. The MagSafe brick is 140w and current USBC can only do 20vX5a (100w). New USBC version can do 240w apparently - but will the USBC on these laptops be able to pull 140w+ via the USBC?

edit: more digging says that the MagSafe will be using USBC PD 3.1 spec - which presumably means 240w potential or at least as much the brick. I only wonder because I have stupid issues like the Microsoft Surface Book2 that tries to pull more power than the provide power brick can handle!

https://usb.org/sites/default/files/2021-05/USB%20PG%20USB%2...

edit 2: okay, while the Block will be PD3.1, the Thunderbolt 4 ports (USBC) only follow PD2.1, so they will likely be limited to 100w.

https://www.theverge.com/2021/10/19/22734233/apple-140w-macb...

Re: MacBook Pro 14-inch and MacBook Pro 16-inch

#980

Post by fulafel »

zmmmmm wrote: post #738
sergioisidoro wrote: post #412

A fair warning to developers: You're getting into an adventure with M1. From docker images not built for M1 with segmentation faults on qemu (eg. Liquibase for spring developers), to _significant_ troubles trying to make React native apps build with the M1 and XCode. Don't get me wrong, I have a Macbook air M1 and I love it, but it hasn't been a love without pain. Also, the magsafe feels like it comes too late. Almos…

I'm curious about the docker image situation. I had thought that the M1 could natively emulate x86 instructions. So why then can you not run the native x86 docker images? Is it a virtualisation issue?

There is no hw emulation, it's all software.
Post reply on HN