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

2016 Retina MacBook Pro Caveats

lvh.io

Post reply on HN
Print view View original

281–290 of 317 posts

Re: 2016 Retina MacBook Pro Caveats

#281

Post by Lio »

CountSessine wrote: post #268
emidln wrote: post #238

Earlier quoted context omitted.

It can. I've been using Caps Lock as Escape across Linux, FreeBSD, and OS X for 7 years now. The various gui interfaces to xmodmap even have an option to do the flip for you (at least in GNOME, Cinnamon, and KDE).

I've been using Caps Lock as Escape That's easy - what @Lio was talking about was having Caps Lock be a tap for and then holding it with another key would be . Is that what you're talking about? Karabiner can accomplish this on macOS, but I can't find a gconf/gsetting/xmodmap combination to do this on Linux. Caps Lock as Escape is easy. Caps Lock as Ctrl is easy. Caps Lock as both doesn't seem to be possible on Linux…

That is exactly what I meant.

The worry about building up muscle memory around something not portable is exactly what lead me to force myself to use C-[ as Escape too.

Re: 2016 Retina MacBook Pro Caveats

#282

Post by eridius »

falcolas wrote: post #255
eridius wrote: post #245

Earlier quoted context omitted.

There have always been charge-only USB cables, they're just not all that common (I believe many mice come with those for charging, but I don't know where else you'd get one). I agree that it is a problem for Apple to be shipping a charge-only USB-C cable, both because this significantly increases the number of charge-only cables in the wild, and because this is probably the first USB-C cable that their customers will…

FWIW, the only time I've seen charge-only USB cables is when they are permanently attached to a charging brick.

I'm pretty sure I have a charge-only Mini USB cable lying around in a drawer somewhere that came with an old mouse years ago.

Re: 2016 Retina MacBook Pro Caveats

#283

Post by Lio »

pimlottc wrote: post #221
Lio wrote: post #152

Earlier quoted context omitted.

> You can get C-c to be pretty much identical with a little remap > :imap True but you're still out of luck in other Vi like places. As an alternative I used Karabina in the past to map Caps lock into Esc (when pressed and released) and Ctrl (when pressed with another key). I think you could also make it latch as Caps lock by using Caps-Shift but I'm not 100% on that. Does anyone know if Karabina has been updated to…

I assume you mean Karabiner. Their page still has a notice that it doesn't work with macOS Sierra. https://pqrs.org/osx/karabiner/

I did mean Karabiner, thanks for the catch.

I've stayed El Capitan because I couldn't think of anything I found compelling in Sierra. I'll probably reconsider when Karabiner-Elements becomes a suitable replacement.

Re: 2016 Retina MacBook Pro Caveats

#284

Post by Lio »

rdslw wrote: post #173
CountSessine wrote: post #148

Earlier quoted context omitted.

You can get C-c to be pretty much identical with a little remap :imap Remapping caps lock would be good too, but I already have caps lock remapped to Ctrl and I'm just used to that. In anticipation of what seemed like the inevitable loss of my escape key, I've been trying really really hard to like Ctrl-[ the last three weeks, but I've just given up. I keep opening up Ctrl-P searches or hitting Ctrl-]. My pinky just…

I aslo remap caps to ctrl everywhere. For vim, you can map tab to being your new esc. Chances are you are using expandtab option, so actual tab usage is not big (it exists though, left here as an exercise for a reader ) Anyway im moving to kabylake dell xps 13. After 9 years with apple. Windows from 2016 gives much better linux integration. And its good to challenge yourselfe with such a big change every 10 years. It…

If you did remap tab to Escape in Vim you could still use C-i for tab as an alternative.

Other neat insert mode shortcuts include C-h for Backspace, C-m for Return and indent/outdent with C-t and C-d.

Re: 2016 Retina MacBook Pro Caveats

#285

Post by ianburrell »

otterley wrote: post #9

We bought a 15" 2016 Macbook Pro ("Retina" is redundant; there are no 2016 MBPs that lack a Retina display.) We also bought a LG 27UD88-W monitor to go with it. (It's one of the few that has a USB-C input.) I have to say, I'm really impressed by the single-cable solution. The monitor charges the laptop (57W maximum, which is less than the Apple charger, but "good enough"), and the laptop sends both video and USB peri…

#3 is because the USB-C charge cable only does USB 2. It doesn't have all the wires that would be needed to do USB3 or alternate modes.

The reason is that USB2 cables are cheaper and easier to make longer. The charge cable is 2m and $19, the Belkin 1m is $22, the Belkin Thunderbolt 0.5m is $22, and the Belkin Thunderbolt 2m is $52.

Also, the charge cable is emarked and supports charging at 5A (100W). Regular USB C cables only support 3A and 60W.

Re: 2016 Retina MacBook Pro Caveats

#287

Post by matt4077 »

MitjaBezensek wrote: post #65

A few other problems I came across: 1. Battery life is much lower than specified: http://forums.macrumors.com/threads/battery-life-for-13-and-... 2. Some users report graphic card problems: http://forums.macrumors.com/threads/pool-do-you-have-graphic... Here is how it looks like: http://forums.macrumors.com/threads/graphic-card-freaks-out-... 3. TouchBar graphics sometimes display on the screen instead of on the Touc…

Battery life may be an effect of all the stuff that goes on when setting up a new Mac, mostly the spotlight indexing.

Re: 2016 Retina MacBook Pro Caveats

#288

Post by matt4077 »

slantyyz wrote: post #136
ChuckMcM wrote: post #40

"Most dongles don't work" was what killed it for me, after reading several reports that it was really hard to hook up anything reliably to the USB-C ports given the churn in the dongle market I decided to skip this generation and go for the next rev.

>> after reading several reports We HN users are fortunate to be "in the know" about these issues, because we keep up with this information. Can you imagine how the out of the box experience would feel like for less-informed early buyers of the new MBP who find out about these issues post purchase? I get the impression it's going to hurt the "everything just works" reputation that Macs have had for the longest time.

"Several" isn't really a reliable number. I know of three people with new MBPs, and none of them are experiencing any of these issues.

Re: 2016 Retina MacBook Pro Caveats

#289

Post by otterley »

snowwrestler wrote: post #280
otterley wrote: post #9

We bought a 15" 2016 Macbook Pro ("Retina" is redundant; there are no 2016 MBPs that lack a Retina display.) We also bought a LG 27UD88-W monitor to go with it. (It's one of the few that has a USB-C input.) I have to say, I'm really impressed by the single-cable solution. The monitor charges the laptop (57W maximum, which is less than the Apple charger, but "good enough"), and the laptop sends both video and USB peri…

With respect to #2, it seems ridiculous to me that in 2016 we still have to manually eject USB devices from Macs. How have they not figured this out yet? I hope it finally gets fixed next year with the new AFS.

Apple can't guarantee that write caching is disabled on every removable storage device out there, even if they send the correct command to do so (some devices ignore it to improve their performance benchmark scores). The best they can do is flush the data on unmount, which requires they be notified in advance via a user action. What else do you expect them to do?

BTW, Windows and Linux have the same problems. The fault lies with the storage device vendors.

Re: 2016 Retina MacBook Pro Caveats

#290

Post by nilkn »

kaypro wrote: post #180

I just got back from returning my 15" 2.6 i7 with Radeon 450. First time I've returned an Apple product ever. The build quality of the machine is superb. TouchID, display, keyboard and SSD are fantastic. There's something going on with the GPU's... I'm putting my money on the Intel HD but the framerate is extremely slow. Just scrolling a simple web page in Safari stutters considerably. I tried using gfxCardStatus to…

The stuttering that you describe when scrolling sounds very similar to an issue I discovered recently where the automatic brightness adjustment feature occasionally causes all multitouch gestures to be very choppy (including scrolling, but also swiping between desktops, activating mission control, etc. -- all of it).

I understand you returned it so you can't exactly test this, but it would've been interesting to see if that particular issue was fixed by just disabling automatic brightness adjustment.

Post reply on HN