Actually now that I think about it I customized the defaults with smcFanControl pretty much the moment I got it so I actually probably don't know the defaults >:y
Even the base 13 inch touchbar model throttles itself
https://www.notebookcheck.com/Test-Apple-MacBook-Pro-13-2018-Touch-Bar-i5-Laptop.316002.0.html
Is it seriously 7 grand? Christ almighty. And it has shit all for IO. AGAIN you're going to have to go out and pay extra for a blockdock that sticks out just to have decent IO
it’s literally 4TB of SSD
why would anyone need it unless you’re already a youtuber rolling in the dosh?
stop cherrypicking the most expensive one
Every single thread about Apple:
*someone customizes one of their products to have all of the most expensive options and posts a screenshot*
Every retard in the thread: WHY WOULD U EVER PAY THAT MUCH FOR A LAPTOP WHEN U CAN GET WINDOWS COMPUTER CHEAPER!!
Repeat ad nauseam
The base model is at most a couple hundred bucks more than an equivalent premium Windows laptop, e.g. from the Dell XPS line. Yes, Apple computers are more expensive. But if you make decent money it's really not that big of a difference and if you prefer Apple computers, then it can absolutely be worth it to you.
Apple has found a cause of the throttling in their software, the new update out today boosts perfomance up to 200%.
https://www.macrumors.com/2018/07/24/apple-addresses-macbook-pro-throttling/?utm_source=osx&utm_medium=push&utm_campaign=front
How the FUCK do you manage to fuck your OS up so hard that the patch doubles the performance
then again, I’m asking the same company that had a bug where spamming a login box with the username ‘root’ and a blank password gave you full rights to any computer running the OS
Apple for its part said it never experienced any issues with excessive
performance degradation in its pre-production testing of the 2018
MacBook Pro, completed in June. The company did identify what it calls
an isolated bug after digging deeper, and came up with what it calls a
simple fix.
Semi-clickbait title. The bug only occured in some video-rendering workflows.
Sorry, you need to Log In to post a reply to this thread.
