A physical ESC isn't that important because multiple presses are idempotent usually; there's only one dialog in the foreground of the active application (at least there should be) or you're only in one insert mode. I also don't see this being a big deal for key-combos. As long as it's available in apps that make use of it or Apple let's you enable it, and there's a way for you to learn where it is by touch, this shouldn't be that big of a deal.
New MacBook Pro Is Not a Laptop for Developers Anymore
691–700 of 808 posts
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#692Your developers. Stop moaning about lack of this or that key and just remap the existing keys.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#693You immediately lost any credibility when you complained that the 2.4 GHz processor is the "same" as the one back in 2010. Clock rate has nothing to do with performance these days. Skylake is 25-35% faster across the board (and multiples faster for number crunching) than whatever Nehalem or Core2 was in the Macbooks in 2010.
25% faster is still a joke. I want 100%!
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#694I'd like to see stats on how my VIM users actually still use the ESC key. Most (including me) have mapped this to Caps-lock a long time ago because the Esc key for a long time has not been in the same place on any keyboard as it was when VIM was originally created.
If you don't have the data, you have no position saying most vim users do anything. There is no reasonable way to assume that most users of any software make the same configuration changes away from default.
Which is why I said "I'd like to see stats"...
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#695I dislike this post intensely. The opinion comes across as uncharitable, as the author probably has not used this Macbook Pro yet. How can you (alexeysemeney) be so sure? I consider myself a developer, and I almost never use the Fn and ESC keys on my Mac. Everybody uses the computer differently, but I'm pretty sure this is not a deal-breaker for most. One could also argue that the touch bar might lead to innovative d…
Developer here. Dealbreaker for me. All my tools heavily use function keys and escape. If I had no other options I'd just deal with it, but Apple is competing with themselves: since they didn't bother to upgrade the actual performance, I have no incentive to move from my current macbook. And when I do, I'll probably just buy a different brand if they don't release a laptop that's actually useful for me.
Non-developer here. The new MacBook has both an escape key and function keys, as could clearly be seen in the demos and screenshots on Apple.com. So all your tools will still work.
Saying the new MacBook doesn't have an escape key is like saying the iPhone doesn't have an "L" key. It does when you need it to.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#696I dislike this post intensely. The opinion comes across as uncharitable, as the author probably has not used this Macbook Pro yet. How can you (alexeysemeney) be so sure? I consider myself a developer, and I almost never use the Fn and ESC keys on my Mac. Everybody uses the computer differently, but I'm pretty sure this is not a deal-breaker for most. One could also argue that the touch bar might lead to innovative d…
Surely the weird thing about removing the escape key is that it is used to bring up the force quit menu (cmd-option-esc). Pretty ingrained in my mind at least, but to be fair not needed that often.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#697Earlier quoted context omitted.
Like I said in another post, is a new single purpose cable a solution for a missing dongle if I still have to carry the old cable with me too? Great, I don't need a USB-C to USB-A dongle, I just need both my USB-C to lightning and USB-A to lightning cables. It is the same problem, just shifting around the inconvenience. And if USB-C is so great and the future of all tech, why isn't Apple moving to it on their mobile…
Google has moved to USB-C with the Pixel. https://madeby.google.com/phone/ Within 24 months, most Android phones will ship with USB-C. That's over a billion devices a year. http://www.theverge.com/2016/6/1/11836816/iphone-vs-android-... Chromebook are starting to ship with USB-C. http://venturebeat.com/2016/10/03/hp-chromebook-13-review-th... USB-C is the future. I'm really not sure why PC vendors having put a couple…
Most new-ish Android phones (as counted by number of models) are likely already coming with USB-C. Both the Pixels, the Nexus 5X and 6P before them, the LG v20, the Moto Z, all come with USB-C. As far as I'm aware, only Samsung hasn't made the jump yet.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#698Earlier quoted context omitted.
> you need a dongle or an USB-C to Lightning cable. Those exist. And so do any USB-C to any other USB-Plug cables. Considering that Apple revises their hardware builds about every four years, it makes sense to move to strictly USB-C now as two years from now, I'm quite sure no more peripheral will come out that has anything but USB-C. So within the next 2-3 years you'll have collected heaps of USB-C cables that will…
> So within the next 2-3 years you'll have collected heaps of USB-C... I agree with you that in the future USB-C is better and makes more sense. However, I don't think that the logical conclusion is that we should get rid of USB-A prematurely. I liken this the the decision to remove the CD from computer when CD were still used daily. I agreed that CDs wouldn't be used in the future, but, that doesn't do much for me i…
That's the price of progress and this dropping support of older technology sooner than everyone else has been part of Apple's MO forever. The day 3rd parties will stop making older parts/accessories is the day they're no longer viable to make. If Apple were to keep a USB A jack for legacy compatibility reasons, 3rd parties will certainly delay moving forward to the new USB-C standard.
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#699I dislike this post intensely. The opinion comes across as uncharitable, as the author probably has not used this Macbook Pro yet. How can you (alexeysemeney) be so sure? I consider myself a developer, and I almost never use the Fn and ESC keys on my Mac. Everybody uses the computer differently, but I'm pretty sure this is not a deal-breaker for most. One could also argue that the touch bar might lead to innovative d…
I put it to you that you've never used a debugger if you've never used Fn keys.
To use the function keys on an old MacBook Pro, you have to chord with the "fn" key to override the brightness, volume, etc controls.
To use the functions keys in the touch bar in the new MacBook Pro, you have to chord with the "fn" key as well.
So where is the difference...
Re: New MacBook Pro Is Not a Laptop for Developers Anymore
#700Earlier quoted context omitted.
As a vim user, esc is pretty important. I would say the author clearly knows very little computer specs: "The MacBook Pro had options with 2.4 gigahertz dual-core processors back in 2010. Anything new in 2016? Not really, well… nope." Because a 2010 2.4ghz dual core is identical to a 2016 2.4 ghz dual core.... I thought we got over comparing processors purely by their clock speed a long time ago. (I will agree that t…
I nearly exclusively use VIm and any other editor I use has a VIm mode plugin installed. I pretty much can't work productively in anything else. I can tell you that I haven't used Esc in ages. I have Caps Lock mapped to Ctrl (as it is a vastly more useful a key than Esc and Caps Lock is a much better position for it and is just as an extraneous as Esc is). I use Ctrl-C or Ctrl-[ to exit insert mode and it works just…
> I use Ctrl-C or Ctrl-[ to exit insert mode and it works just fine. In fact I understand that most experienced VIm users do this.
That's pretty uncommon to imply it's generalizable. Most vim users, I feel comfortable in saying, actually use 'Esc', or a key mapped to the same. Speaking for myself, I can't see why I'd want to use two keys when one would do.