Warming up a 2019-era (Intel) MacBook Pro was never my problem. Quite the opposite. Those machines ran notoriously hot. The later macOS releases, combined with company-mandated crapware, made it worse. Doing an ordinary build or starting a videoconferencing session was enough to cause the fans to run. On a warm day the fans couldn’t shed enough heat and so the system would go into thermal throttling. The OS would occupy a core with a 100% kernel_task that didn’t do any work but which would serve to prevent actual work from being scheduled onto that core. When four or five out of the six cores were occupied by kernel_task, I knew I was in for a bag of hurt (to steal a phrase from Steve Jobs). Responsiveness went completely to hell. The machine became effectively unusable.
After a while my normal procedure was to run with the thing sitting on top of an ice pack. That would let me run a 60-90 minute video conference without troubles.
The only redeeming feature of these machines is that they could emulate old x86 hardware at speed. That allowed me to run old apps on old OSes without having to keep old hardware running.
I had Windows and Mac laptops back then, and the HN snobbishness around the superiority of the Mac was genuinely baffling.
My i9 2019 MBP with discrete graphics was probably the worst laptop purchase I ever made. Docking it to an external monitor would enable the GPU, so even when idling it would run the fans and drain the battery.
I’d read cautionary tales about Windows laptops being pulled out of backpacks scorching hot as they failed to shut down. But that happened to my Mac all the time, too.
The M series though is incredible. I can’t imagine buying a Windows laptop now.
This was a laptop, so cooling was very constrained. The fans can only be so big & you can only shift so much air in & out of a MacBook.
I presume Apple knew perfectly well but wanted the halo product to sell to those people who will always pay extra for the perceived “top of the line” product. Once Intel branding had created an i9 that was a bigger number than an i7, then Apple was going to sell it.
It was faster than the i7 after all: just not for very long!
My entirely speculative theory is that the poor thermal characteristics of that era of Intel CPUs didn’t really become apparent until quite late in the development process & by that point Apple had probably committed to buying a fair chunk of Intel’s output.
> Intel really made themselves unpopular with Apple during that period.
Intel just reenacted IBM's history with Apple, particularly the G5 era. That CPU was instantly a no-go for anything mobile. In workstations it was cranked ever higher with very poor power-frequency scaling, needing water cooling for the beastly 200W idle power consumption and close to 1kW full throttle.
That went well so was a perfect role model for Intel's i9.
I had (and still have) a 4k external monitor. Naturally I wanted the MBP to drive the monitor with a resolution that took advantage of all the pixels. Unfortunately with most monitor settings the GPU power consumption would produce enough heat to run the fans even if the rest of the system was completely idle! If I set the output to full HD the GPU would cool down and the fans would turn off. But full HD on a 4k monitor is a waste.
It was very strange. I could drive the monitor at 4k but with the image upside down, and the power consumption would be low. But flip the image right side up and it would run hot and turn on the fans.
It took a couple weeks of fiddling, but I finally found a combination of refresh rate, resolution, image orientation (right side up!), and cabling that let me drive the monitor at high resolution without running the fans. What a pain.
(I used iStat menus to monitor GPU power consumption. At “good” settings it consumed about 5w. At “bad” settings it would consume 17w. At a bad setting you could immediately see the various temperatures go up and the fans spinning up to compensate.)
It was a truly ridiculous idea to put an i9 in any laptop. That generation of i9 is difficult to cool even with liquid cooler systems in big ATX cases.
My Intel MBP would noticeably raise the whole room's temperature, while the fans ran so loud. We had some corporate security software that would occasionally go haywire and lock up 100% of a core until you rebooted. If you got that at the same time as a video call it would become too physically painful to touch any part of the metal body with bare skin.
i decided to do an experiment and try to run an LLM in my old 2013 MBP. i7, 16 gb mem, 1 tb hd.
Installed Linux mint Xfce Edition for lightness, installed ollama, start to test different models. Gemma4 e4b runs perfectly fine, exposed it to the network, connected to it with my current notebook and use vs code codex to start to run inference.
For about 30 minutes of bliss, this setup work at a reasonable speed... then the MBP shut it self down. It was so hot that it trigger the safety mechanism, the fans sounded like the laptop was about to take off.
I though on leaving it on inside the fridge, but then the WIFI wouldn't reach.
On the other hand, my wife saw all this and offer to buy me an M5... the experiment didn't work as intended, but it did work.
On a laptop that old it might be worth opening it up to blow all the dust out with a compressor or air duster. I’ve often found that to work wonders on old MacBook Pros.
The other issue is that unless the battery has been replaced relatively recently its charging efficiency may not be that great and the high load being placed on it might be causing it to get hotter than it would have done when new.
Form always ruled function with Jony Ive, but he always had a good eye for the way compromises shook out. During that era, Ive was creatively checked out but Cook kept him on to maintain the stock price.
Maybe the same type. Each time I call the LLM api the fan starts to work and make big noise. The temperature in the room is going up noticeably for 1-2 degrees.
> Each time I call the LLM api the fan starts to work and make big noise
So every time you do HTTP calls? Nothing there should spin up your fans, unless you use an agent with an horribly broken TUI, I've heard there is a few of those out there. But remotely calling LLM APIs really shouldn't be taxing on your local device, something somewhere is wrong/bad if that's what you're seeing.
Sure, if that's what you're using, then that's definitively buggy, unless it's doing compilation or something actually using your resources, just making HTTP calls shouldn't be heavy for your computer. Claude Code was mainly what I was thinking about, as it similarly broken, but I'm sure there are more out there as most of them seem vibe-coded at best.
I’ve always been told to let electronics and musical instruments slowly warm up in their case after bringing them inside. Supposedly reduces the chances of condensation forming.
I still use a 2019 MacBook Pro, in 2026 I found the best way to warm it up was to use it daily and not blow the dust out of it for 7 years. After I opened it up and did that it's running a lot cooler.
My M3 Macbook Pro's palm rests get uncomfortably warm during regular IDE use. It doesn't get hot enough to spin up a fan, but it is enough to be distracting.
Haven't used PHPStorm but I know Android Studio does a lot of stuff in the background so I wouldn't be surprised if other JetBrains IDEs do the same. Although PHP isn't compiled...
There's still indexing, linting and code analysis tools running as well as multiple Docker containers (those are pretty much idle outside of running tests or migrations to be fair) and whatever else it could be doing in the background.
I spend 95% of the time with just PHPStorm and other stuff like the terminal, slack and ticketing open. And the browser of course (safari). Xcode and Android Studio are rarely opened. Mostly when I want to test out something in the apps that isn't on testflight / firebase yet.
Modern Macbooks have this issue, the other day I realised I had never heard the fans of it run, so I was wondering if they actually worked.
Found a web based benchmark tool that will run your CPU and GPU at 100% each. While temperatures went up to 90 degrees science... still no fans. Ended up installing a different utility to manually set the fan speed to confirm they worked.
Speaking of cold weather and warming up computers... I've had my fair share of long bicycle commutes during cold winters and I always wondered whether booting up the laptop right after arriving has any effect on the long-term reliability? Like, are there any components which suffer from being activated when they're really cold?
It increases the chance of solder cracks, which is one major cause of failure. Thermal cycles in general will do that, however, and home computers are designed to survive a lot of them.
I think my last Macbook was Wisconsin-locale instead of California. Closing the lid and putting it to sleep actually caused it to heat up (until the battery died).
Or just leave the machine plugged in and turned on for like 5 minutes while you grab a coffee or have a conversation. It doesn't really take that long to warm up to room temperature. Unless this guy is like biking 15 miles to work in the winter in which case, he is doing Wisconsin wrong, you're supposed to drive to work with a beer to warm you up.
I recently installed an app to manually activate the fans on my MacBook Pro M1 Pro as I've never been able to trigger them over the past 4+ years. Just to check whether the fans even work (they do).
You must be using only lame languages like C or Go or Python that aren’t optimized for laptop warming during compilation. Try using a Real Language with a Real Compiler, like C++ or Rust or Swift, and build decent-sized projects using all cores.
(All joking aside, this is why I have a MacBook Pro. Compilation easily hits the Air’s thermal limits and the performance boost on the Pro with its fan is impressive.)
Or something useful, save space, compressing some talk or edu video, just 6 fps is usually enough for slides or code, opus audio can go as low as 32k and still be decent compared to source quality, expect 10-15x size reduction
Is that running on Rosetta 2? Rosetta 2 does (or did, maybe it's removed now) a fine job running x86 code on Apple Silicon, but boy was it cycle-hungry to do it.
Apple Silicon is not really the simultaneously silent and quiet and cool system it was in the M1 days.
If you get a MacBook Air it will get quite toasty at throttling limits. After all, it has no fan.
MacBook Pro models and Apple computers in general tend to favor quiet operation over keeping the laptop surface cool.
Many PC gaming laptops go out of their way to keep warm air off the keyboard deck with a high willingness to use fan noise to accomplish that since the assumption is that you’re resting your hands on the computer for an extended period and you have headphones on for your game anyway.
The target market of the "Neo crap" doesn't care and/or isn't pushing workloads that come anywhere near saturating it. It's a laptop that doesn't bend, has a decent screen, has a decent battery, and isn't full of adware.
And your comment was calling it crap for some reason. We wouldn’t be having this conversation if you’d left that apparently superfluous word out of your comment.
How does the Neo getting to 100°C make it crap? By that logic, aren't all older Intel/x86 chips crap? If anything, I find it impressive that a small laptop CPU can do 100°C without a problem...my i7-7700T M710qs hit 75°C and throttle within a minute if I use a tool like y-cruncher or stress-ng. To be fair, totally different purpose.
For a very long time now, it has been the case that in the short term most processors will boost high enough for the die to reach around 100°C. When you see a reading substantially lower than that like your example of 75°C, either the system has throttled for a reason other than processor die temperature (eg. throttling to limit the temperature of the outer case of the machine) or the temperature reading you're seeing does not correspond to the hottest part of the chip and the throttling is based on the presumption that a different part of the chip that is not directly monitored will be much hotter.
In the specific case of the i7-7700T, the "T" suffix for Intel CPUs usually means you have mainstream desktop silicon with arbitrarily reduced long-term turbo limits, intended to be used in small form factor PCs with limited cooling capacity. Its limitation to 35W sustained and official Tj max of 80°C are artificial and essentially fiction, and the same silicon will readily do 91W sustained with a Tj max of 100°C as seen on the i7-7700K.
Processor temperature under load tells you almost nothing about the power draw or efficiency of the chip, because the temperature can be controlled to almost any value desired through a combination of varying cooling effort and varying clock speeds.
To be fair, the fundamental problem here is the author's resting of wrists to type.
This applies to any computer, Apple, Windows or Linux. Desktop or laptop.
If your typing on any computer is dependent on you resting your wrists whilst typing then it is indicative of poor typing technique and/or posture.
And ironically the very thing you think you're trying to prevent by resting your wrists (carpel tunnel and/or strain) is likely to be aggravated by over-reliance on wrist wrests due to the added pressure on the wrist.