Live data from Hacker News

New MacBook Pro Is Not a Laptop for Developers Anymore

blog.devteam.space

231–240 of 808 posts

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#232
I remap my CTRL to CAPS LOCK because it's more convenient.

Have come across a lot of Vim power users that do the same with ESC. Or buy the model without the Touch Bar.

Can we stop with the drama now? It's becoming pathetic.

Apologies for the bluntness.

P.S.: more RAM and CPU? Get a desktop or buy another laptop. Since when was Apple the fastest, more bang for your money? This was clearly not a specs bump iteration.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#233
post #92
post #24

It's funny they bring up devs using vim, because the only vim key they removed is Esc, which a lot of vim devs remaps to caps-lock or similar anyways. I almost never use the F keys, so if they kept the Esc key but removed the rest it would be perfect :)

I don't know anyone who remaps capslock to esc. It just sounds like something that is fun to say on hackernews. You didn't even say you use it, you said a lot of vim devs do, to which i would counter--they dont. The better choice is remapping capslock to ctrl.

I do. And judging from the list of articles that explain on how to do it for various platforms I suppose a lot of people do. The carabiner-elements is a whole (popular) program to do just that (by default, it has more options as well)

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#234
post #99

Earlier quoted context omitted.

I'm not suggesting you do this, for legal reasons blah blah blah, but putting together a hackintosh is pretty easy these days if you really like osx.

How easy is it to maintain? Last I heard every update breaks everything.

It’s not. You’re pretty much stuck on a static OS unless you want to spend hours dealing with various problems each update.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#235
post #147

Earlier quoted context omitted.

I'm 99% sure the escape key will be there when in Terminal.app, I also imagine terminals like iTerm2 will have some really sweet TouchBar options to make it even better with all your console apps.

Apple may prove me wrong with the ergonomics of the TouchBar, but I've yet to find a virtual button that I've liked as much as a physical button.

The feel of a real button is great, but you can imagine the possibilities of what you can do with that space when you look at your MacBook keyboard right now and notice you likely never use a thing but the escape key, brightness and volume.

I haven't used it yet, so I can't judge it too much, but I imagine Escape actually works well since it's the top corner of the keyboard and easy to feel, if escape were anywhere else it would really suck.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#236
post #55

As a developer and an Apple user for last decade, this has certainly been the most disappointing Keynote I've ever seen from Apple. I do think, however, some of these concerns are overblown. If you're a VIM user and haven't tried overriding the Caps Lock key to be an Esc key, you should give it a try, it has made VIM a much better experience for many people. On the memory side, doing development work I can hardly thi…

The problem is that as soon as you need a VM (and doing any web development typically needs one to test IE/edge with), you're pushing your RAM limits.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#237
post #115

To be honest, the only thing that's causing me to say it's not a "developer machine" is the keyboard. It features the same butterfly switches that the 12" MacBook has and my good are they horrible. I seriously can't imagine writing long sessions of code with this mushy keyboard. I don't get it. With the new touch bar and stereo speakers they WANT us to use the MacBook as is, without external keyboard and then they gi…

The new MacBook Pro uses version 2 of the butterfly keyboard. Not the same one as 12" MacBook. Verdict is still out how much is the improvement.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#238
post #132

Earlier quoted context omitted.

I've developed on a MacBook Pro for the last 5 years in vim and I have never touched the escape key or any of the F keys, ever. If you're using vim and reaching for the escape key you are doing it wrong imho. Rebind esc to something else (like capslock) or learn another pattern that has more ergonomic value.

> If you're using vim and reaching for the escape key you are doing it wrong imho. So generations of Vim users are doing it wrong but you have the right answer?

The Vi editor was originally written on a terminal which had the Escape key positioned where the Tab key is on modern keyboards.

So yes, rebinding Escape is the right answer if you heavily use it. The normal positioning for Escape is very inconvenient for touch typing.

http://vim.wikia.com/wiki/Avoid_the_escape_key

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#239
post #62

Earlier quoted context omitted.

I had no idea you could use C-[ as ESC

It's also a kinda crappy alternative, because it's not possible on a large number of non-English keyboard. Ctrl+c is also an option, although I think there's a slight difference.

ESC is 0x1B, traditionally the CTRL key reset the two highest bit of the ASCII code, [ is 0x5B, if you reset the two highest bits of 0x5B you get 0x1B which is why ESC and CTRL-[ are the same thing.

CTRL-C is completely different.

Re: New MacBook Pro Is Not a Laptop for Developers Anymore

#240

It's worth noting that only the higher-end of the new MBP's have the Touch Bar. The lower end still has a traditional function row: http://arstechnica.com/apple/2016/10/no-new-macbook-airs-as-... So I suppose in theory if you wanted something new but without breaking your workflow, you could just go for that one.

The frustrating thing is that machine only has 2 USB ports, rather than 4. So one port for power and another for a single wired accessory. I guess buying a dongle isn't a huge deal, but kind of frustrating that you'd have to spend more money for what I would expect to be included functionality for a "pro" machine.

[deleted]
Post reply on HN