I've actually used my wife's iPad Retina Mini and the display is impressive however it doesn't make much of a difference when you have milk bottles for glasses unfortunately. The scale of the stuff on the display is more important than the DPI to me.
The nice thing w/ Retina is that one gets small stuff w/ great details.
(re: Miller column filebrowser)
I find this incredibly hard to use. Particularly as it's a pain to scroll horizontally and vertically to get back to where you were. Not only that there is no grouping of directories and file separately so you have to scroll up and down a lot to find directories sometimes. Not very usable IMHO.
It was better in NeXTstep when the scroll bars were on the left (see Mullet & Sano's _Designing Visual Interfaces: Communication Oriented Techniques_ --- I still prefer it, and wish I could find a workable one for Windows.
<snip Services and PDF support>
I know Unix inside out and it's Unix under there but it's a *****Expletives removed by Moderator***** unfamiliar one.
It was nicer / more standard / more accessible in the NeXTstep days.
<snip inter-layering windows>
Development tools are awful. Sorry but I've sat in front of Xcode for a week now and it's horrible. The LLVM integration is pretty good, especially static analysis but the thing is so *****Expletives removed by Moderator***** obtuse. For example crazy stuff like editing iOS UIViews is only supported if they are zoomed to 100%, the assistant editor is just hell and the keyboard shortcuts have my hands doing games of Twister all day. Moving to and from the touchpad is a pain as well. My hands are always off the home row and hurting. I'm a pretty handy well exercised pianist and the keyboard is killing me on this.
Why not use a mouse?
Xcode and Objective-C make sense / fit well together once one buys into Apple's style of object-orientation.
The keyboard shortcuts get better once one turns on default Fn-keys, and one can re-work others.
I write TeX (well LaTeX) with vim and make usually on a Linux box in the office. The GUI side of things doesn't really add much for me as I'm used to hacking out the TeX macros.
Inverse search --- try <Command>-clicking in the .pdf view, or in your source text.
I also find it to just look nicer and work better than TeXworks and the other integrated shells (I use Dirk Stuve's WinTeXshell in Windows).
Automator got me 90% of the way to solving one problem I had (image batch resize) but it just feels clunky. AppleScript - didn't try it but it looks too much like natural language. Just get the feeling it's going to be error prone using it. This could be a non issue though.
You can call Unix shell scripts from Automator (may have to use AppleScript to do so). Batch image resizing is a task a lot of people have had to tackle --- I've done a bunch of variants on it at work. AppleScript can be infuriating at times, but mostly it can be made to work, and it's the most accessible spiritual successor to HyperCard/Talk.
<snip Notational Velocity, Aperture/Lightroom, GarageBand/music, iMovie, Pixelmator, misc. apps>
Was trying to avoid this as it would be a defeat! The hardware is nice. It's fast so windows is a possibility but I really would have to plug in a normal keyboard and mouse to it. Then it's just a normal PC which I might as well go and bag.
<snip Spotlight >
(2) I have to connect to a Windows remote desktop to do work. There is a massive disparity between the keyboard layout on a PC and a Mac and it is incredibly difficult to switch between the two using Microsoft Remote Desktop. This is not a fault of Microsoft Remote Desktop either. There are things that you just can’t do with the mac keyboard logically i.e. PrtScrn for example.
Can't recall the last time I had to use PrtSc. Just connect a Windows keyboard when one has to do that sort of thing, or re-map the keyboard layout.
(3) The keyboard. They keyboard sucks. The spacing between the keys is incredibly large so you have to move your fingers great distances. This makes typing on the keyboard incredibly difficult.
YMMV, I find the spacing fine --- try a MacBook Air w/ smaller keyboard?
The F-keys are all Fn-shifted on an MBP which makes various functions on Unix and Windows remote machines quite difficult. It’s like playing Twister.
There is an option to reverse that, so that the special functions require fn, and a bare tap of the f-keys gets one the fn functionality.
There are also 5 meta-keys (shift, Fn, Ctrl, Alt, Cmd) which are distributed inconsistently.
I always re-map Caps Lock to be Control, &c.
For example to create new tabs in Safari, it’s Cmd-T. To switch tabs, it’s Ctrl+T. WTF.
This made more sense back in the NeXT days --- <Control> shortcuts were either those of emacs, or were set-aside for user customization --- Developers were only allowed to set <Command> key shortcuts for their apps.
There is also no hash (#) which is required regularly when programming in any language these days; you have to Alt+3 to get it and it’s not marked on the keyboard.
Are you using a foreign-language version? You can always just re-map the keyboard / use a different keyboard layout. I'm seeing an octothorpe on every keyboard image I can find.http://techytot.com/apple-macbook-pro-keyboard-layout/
argues ``AnandTech Apple MacBook Pro 13 Can a Mac Be a Decent Windows''
The enter key is also tiny which leads to many miskeyings.
I believe it's been made larger (or eliminated on newer machines). Usually this is the sort of thing one can become used to / better at. Patience is a virtue and all that, though I understand yours is being tried.
(4) The touchpad was giving me really sore fingers. I bought a Magic Mouse hoping that would sort it but I just end up with sore fingers as well as the thing is poorly designed. It nips your fingers holding it on the side when you press the button and it's hard to hold because of the low profile.
I use a Wacom Intuos or Logitech G-600 on my machine at work and have never much liked the trackpads, hence my presence on a ThinkPad forum (I just wish I could get a ThinkPad running Mac OS X).
<snip allergy and continued perseverance>
Hope this helps you get further along!