The escape key always seemed a horrible choice for such an essential key in vim.
I mapped it to capslock like 2 days after starting with Vim.
Many people also use "jj" or something similar.
New MacBook Pro Is Not a Laptop for Developers Anymore
91–100 of 808 posts
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#92It'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.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#93So use an editor that supports a modern UI, like Sublime Text or Atom, and not something originally designed for an ADM-3A terminal.
Good luck using Sublime or atom over SSH.
Sublime has an SFTP/FTP plugin that makes it trivial to edit files over SSH. Since you are running ST on your local machine and only using SSH to save/read the file it actually works better over a flaky connection (like on a plane) than SSH+vi.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#94This doesn't even get into the dongle problem. The simplest example is that if you want to hook up Apple's flagship phone up to their flagship laptop for development, you need a dongle. And if you want to share one of their flagship wired headphones between the two devices, you need another dongle. Therefore if you want to connect three of Apple's flagship devices together on a daily basis, you can't go anywhere with…
I agree with you, but it seems they are already selling a USB-C to lightning cable. http://www.apple.com/shop/product/MK0X2AM/A/usb-c-to-lightni... a.k.a the "lightning to thunderbolt" cable.
That might remove the dongle but is it any better? I now need either two cables, one to hook my phone up to my laptop and one to hook it up to my computer, or a new charger that accept USB-C but won't be compatible with most other devices out there.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#95Lenovo introduced a Touch Bar (Adaptive Keyboard strip) in the Thinkpad X1 Carbon in 2014. It flopped so hard that Lenovo pulled it and reinstituted a normal function row in the 2015 refresh.
Why does Apple get a pass? No physical keys means not being able to find functionality by touch alone means no muscle memory means no productivity. This isn't a hypothesis, this is a proven market reaction to Lenovo's design choices.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#96Sure I would like Apple just have kept the keyboard as is, and not having the ESC key is going to take some getting used to, but even as a Vim user it's a solvable problem.
Depending on your workflow and platform choices, you don't even need to upgrade your Macbook Pro, the last to generation are perfectly fine for a very large number of people.
Scott Hanselmans comment that not having a ESC key for Vim is messing with Apple core audience the just plain stupid. The VAST majority of Apple MacBook Pro customer aren't installing Vim.
Only having USB-C connectors seems like pushing it in terms of how fast you can expect users to adapt and it's going to be an adaptor hell for a year or two.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#97This doesn't even get into the dongle problem. The simplest example is that if you want to hook up Apple's flagship phone up to their flagship laptop for development, you need a dongle. And if you want to share one of their flagship wired headphones between the two devices, you need another dongle. Therefore if you want to connect three of Apple's flagship devices together on a daily basis, you can't go anywhere with…
What prevents you from connecting them using Bluetooth? I forgot when it was a last time I had to connect my iphone via cable, MacBook just always knows that it's there via Bluetooth, and for the headphone, their flagship headphones are wireless now, and I've been very happy using bose Bluetooth headphones, losing a cord is a major benefit that far outweighs any drawbacks of dongles for me
> What prevents you from connecting them using Bluetooth
I don't think you can connect via BT and then use that connection from Xcode for deployment and debugging. That still requires a cable.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#98I'm always confused by the interface outrage from hard core devs around new laptops. As a dev, I spend the absolute minimum time possible developing by interfacing with my MacBook itself. 98% of the time I'm plugged into a mechanical keyboard, giant monitors, and a real sound system. My MacBook sits to the side and only gets touched when I'm on an airplane or a meeting.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#99I've had a good, satisfying run with MacBook Pros, but now I'm stepping off the Apple train. I understand that Apple is trying to go in a new direction with the new MacBook Pros, and I won't complain about it. I am now simply moving to an Arch Linux setup on an old Lenovo Thinkpad Carbon X1 to continue living inside the Terminal.
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.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#100This seems like a combination of trolling for page-views and begging the question of whether your personal tastes are universally shared.
Nobody has even used the touch bar yet so we don't know how well the escape + function key mode works for the average developer, or how often the wins of other features (e.g. the dedicated “man page” button shown in the screenshots, the kinds of context-sensitive things something like a debugger, browser dev tools, etc. could do, etc.) would balance out the lost of a physical key.
There's a small mistake in assuming that the quad-core 2.4GHz processor you got in 2010 is exactly the same as the 2016 Skylake version, and I think that masks a much larger question: how many people actually need more CPU or even RAM? Some developers definitely do – if you're working with a 20GB model, there's no alternative – but a large number don't.
For me, most of my development laptop hardware requirements plateaued somewhere around the MacBook Air somewhere around the 2010-12 range because this thing called the cloud happened and most of the work which can't be done on a small laptop with an SSD also isn't a good fit for a slightly larger laptop. Everything else I'd look for are different areas like screen size.