&gt;<i>First; I run the same software on all my computers for around 15+ years; some libraries etc have been added ofcourse but basically I develop with vim in python, c#, java, c&#x2F;c++, haskell, haxe, ruby, perl, php etc and the Chrome browser since it was out.</i><p>So, clearly, unless you SSH, you also install all kinds of stuff to support those languages (compilers, runtimes, linters, the whole of cabal, etc).<p>&gt;<i>I do not do 3d work or video editing and maybe it is faster in that; to me while coding it just does not feel as snappy and I can just show the beach ball to you on the pro while I have never even seen it on the air during work.</i><p>Well, I&#x27;m a coder too, and I use Vim too (also ST3, Eclipse, XCode and Idea for different stuff) and I&#x27;ve never seen the beach ball while coding with vim on my MacBook Pro. So what now?<p>In any case, I don&#x27;t think a support team in a company is the one to solve such software issues. They are just some random guys (not even CS degrees) with general knowledge of computers, that mostly run through &quot;customer service&quot; scripts.<p>Given that it&#x27;s 100% a software issue (and not e.g. a faulty HD causing slowdowns), the best way for someone who is a programmer is to go down and trace the root cause themselves. Try booting from another drive. Run dtrace (or what&#x27;s called on the Mac). Check Activity Monitor. Etc.<p>Whenever I have such issues, on OS X, Windows or Linux it&#x27;s just a hour or so to find the culprit. At worst, a day, after you already have a strong clue.<p>The battery life seems to be of the same origin. Increased CPU usage depletes the battery faster. I get 6-7 hours from my MBP, with Chrome and programming and mail and stuff going on, and it&#x27;s a 2 year old machine.