Live data from Hacker News

New MacBook Pro Is Not a Laptop for Developers Anymore

blog.devteam.space

671–680 of 808 posts

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

#671

Earlier quoted context omitted.

> As a vim user, esc is pretty important. Only if you're too lazy to rebind it to any of the many more finger friendly options.

What if you log in to a large number of servers on a regular basis, then you'd need ESC for vi.

Or Ctrl-C or Ctrl-[

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

#672

Earlier quoted context omitted.

I really feel most Linux distros were made for developers and development. Whenever I try to do things on Windows and OSX I get insanely frustrated with the amount of friction. It's nice to have an OS that trusts you and lets you make mistakes.

Windows is quite a nightmare for any time of compiled code in my opinion. All of the Microsoft 'stuff' (anything in Visual Studio) works okay but once you start installing python or node modules, forget about it. I remember the click finally happened when I spent an afternoon installing package after package to get a node module to compile on Windows. When I installed it on OS X, it just installed... I didn't have to…

True story, tried compiling a node machine learning thing.

After 3 hours on Windows, I just brew-installed the damn thing from github on Mac and it just pulled all the dependencies.

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

#673
post #666

People like to use rhetoric to pretend that their opinion is universal as a preventative measure for suppressing disagreement. Programmers, unfortunately, like to apply this to things that are transparently subjective, targeted at an intelligent audience that often takes umbrage to being told what to think. I feel like I should flag this article for being nothing more than rhetorical rabble-rousing[0], but frankly so…

The best way for smart people to kill a community is to go somewhere else. Because when the smart people are gone, there is nothing interesting left in the community to follow. Therefore that's an option I want to suggest to you. Let us stupid people destroy ourselves here. Thanks.

No. I don't much care about your opinion of me, as is only appropriate.

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

#674
post #547

You 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.

I get though that it doesn't feel like Moore's Law type growth for system speed though, which is perhaps what people are hoping for. I have a hard time imagining that the 2016 model feels 16x as fast as the 2010 model. I've got a 2010 MBP with an SSD, and it feels pretty much the same as my 2013 with an SDD, and expect this 2016 one to feel roughly about the same for most tasks (35% isn't a difference I'll notice for…

Moore's law died a decade ago.

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

#675

I 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 was configuring a server while walking through the airport the other day (long story and I won't bore you with details) on my ipad. There is no control key on the ipad keyboard meaning that I could not save any files from the ssh terminal. It was not the greatest experience and I can definitely see these kinds of things happening on laptop now due to apples "courage". They seem to be gung-ho on breaking things that…

When I concluded my Thinkpad Tablet 2 was a little bit too small to work as a primary machine (switched to a Helix 2 for that), I re-paired the bluetooth keyboard w/optical trackpoint with my tablet. The keyboard fits inside my jacket.

I can't express quite how wonderful it is on the occasions I don't have a bag with me to still be able to have a proper keyboard+mouse setup when something goes sideways.

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

#676
post #388

Earlier quoted context omitted.

> So yes, rebinding Escape is the right answer if you heavily use it. nobody does that because it was unnecessary. Of course, now developers need to ADAPT the Macbook instead of the Macbook ADAPTING developer's workflow. That's not the definition of a developer friendly machine. The touchbar is a gimmick and even then it doesn't justify the removal of an entire row of keys. It was purely an aesthetic decision. But I…

Sorry, but removing this row of keys is entirely justified if you accept that the touchbar is a valuable addition. Having to reach over a row of useless keys (I suspect Apple's data would show ~90% of customers literally never use them, except for the system-control functions) to interact with the touchbar would seriously compromise it's utility.

> (I suspect Apple's data would show ~90% of customers literally never use them, except for the system-control functions)

Completely dishonest and backed by no fact at all, you can make up some data, I can too, I didn't. You call them "useless keys" but there are here for a reason. There are so useless than the touchbar can emulate this "useless" row, except that now users have to look at the keyboard to type since there is no physical feedback to guide them. this isn't innovation, this is a step back.

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

#677
post #427

Earlier quoted context omitted.

> As a vim user, esc is pretty important. Would it not be possible to map the dynamic touchbar keys to Esc when one is using vim?

But then how do you change the volume when using vim? Does vim need a special touchbar that basically completely emulates the old keys? That seems excessive.

Did you watch the presentation? Or are you just pearl clutching to try and crap on something you don't like?

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

#678
post #62

Earlier quoted context omitted.

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

I wonder how many vim users have tried using CTRL + [ for the first time today. Muscle memory being what it is I fully expect that nobody will swap over to this new and improved Apple way of pressing the Escape key.

Much to my surprise, after I was forced by circumstances to use Ctrl+[ for a month or so, I found I didn't actually want to go back to Esc.

Had it only been a week or two I suspect my muscle memory wouldn't've shifted though.

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

#679

Earlier quoted context omitted.

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…

Not even a developer key: `escape` is a very convenient UI mechanism for getting out of something modal or otherwise overlayed and open.

Esc is important in Excel too. More users than Vim.

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

#680
post #663

Earlier quoted context omitted.

Also... the F1 keys are like super important for debugging. Sure, you can click with the damn mouse in the button for step in, over, run, etc, but the thing is faster with F keys. Even if mac apps come mapped to other keys, many peaplo still runs windows with bootcamp, virtual box etc and wine programs in apple computers, making things even harder. And about external keyboards? Apple keyboards comes with F keys... th…

The F1 keys are not important for debugging. When I'm debugging, I'm not concerned with what's faster. So I use the icons and the mouse.

This is really just a war of opinions now, but the F1 keys are indispensable to me. My fingers rest on the hotkeys for "step into", "step over", "run to breakpoint" and I can keep my eyes glued to the watch list, inspecting the variables at each step. Some times you want to quickly step into functions, other times step over, and it's just really handy to have it mapped to keys.

I'm not even a power emacs user or something (IntelliJ is my preferred IDE). YMMV of course, but I find the hotkeys super useful.

Post reply on HN