New 16-inch MBP with M1 Max to feature High Power Mode for intensive workloads
macrumors.com
macrumors.com
For several years I continued to use that beta version, patching it to use updated WebKit versions. I think it finally stopped working around v7 or v8.
Still got the 14 since the 16 seems too bulky and heavy for a daily carry.
It is still thinner than the 2012-2015 15" model (which had a perfectly functional keyboard and trackpad) but ~.3 pounds heavier.
I really don’t get all this talk about how heavy laptops are…
> Still got the 14 since the 16 seems too bulky and heavy for a daily carry. 16" is still lighter than my old T430 and T440p, never had a problem stuffing those in bags. Tiny bezels and weird aspect ratios mean it's not much bigger either.
But the best feature, to me, was those PC with a turbo button that also had a seven-segment display showing the current speed. This was looking really cool.
At the time I had no idea what it was and...not sure I do now.
Makes sense when you consider that the M1 has more efficiency cores than the M1 Pro/Max.
I'd actually like to build myself a home NAS/server with only Gracemont cores if we ever see Alder Lake-L available in a mini-ITX form factor. (Was going to try with Jasper Lake, but that seems to have been effectively cancelled with the chip shortage.)
[1]. https://www.anandtech.com/show/17019/apple-announced-m1-pro-...
So no. Definitely not. The user should be able to toggle this. As Apple has wisely chosen.
Nothing worse than trying to concentrate on something when "helicopter mode" suddenly kicks in :)
`echo 0 > /sys/devices/system/cpu/intel_pstate/no_turbo`
Damn these trickster designers and their shitty design decisions. That's exactly the opposite of what I thought it did.
So, unpressed button makes computer slower, not pressed one.
Source: actually used the button on my 386 SX 20/40 MHz
Maybe yours operated differently, but everything I can find about turbo buttons on the internet indicates that they operated as I remember them - your computer gets slower when you turn the button on. I specifically remember playing certain DOS games where, if I didn't activate the turbo button, the entire game would speed through at what felt like double or triple speed.
From wikipedia on Turbo button:
> On IBM PC compatible computers, the turbo button selects one of two run states: *the default normal speed or a reduced "turbo" speed*. It was relatively common on computers using the Intel 80286,[1] Intel 80386 and Intel 80486 processors,[2] from the mid 1980s to mid 1990s. The name is inspired by turbocharger, a device which increases an engine's power and efficiency. *Contrary to what it suggests, the "turbo" button was generally intended to let a computer run slower than the speed for which it had been designed when pressed.*[3]
Look, you read about it in wikipedia, but I actually lived with this computer for my whole childhood. I know for sure how the turbo button worked, because I actually used it to cheat in F1 and Lotus racing games.
Best I can find in 10m I dedicated to this is this video showing switch between 22 and 40 MHz modes with a turbo button (around 8:50): https://youtu.be/TdenDH7S8LM
“ On most systems, turbo mode was with the button pushed in, but since the button could often be wired either way, on some systems it was the opposite.”
You turned the Turbo mode off when you needed to run it slower, say for playing games.
So, technically the button did what it said, run faster in Turbo mode.
Some selectors would let you choose between 2 speeds, others had multiple speed selections. Often the higher ones would crash a lot more. There were also variable speed controls that acted like a rheostat with continuous speed changes. Those worked but were even more unstable.
It literally did nothing except change an LED readout on the case from saying "16" to saying "166".
On the motherboard there was a jumper which took the input from the turbo switch.
To provide feedback to the user, some cases ran a wire from the turbo switch to a bi-color LED on the front of the case as well as to the motherboard to control the turbo state.
On fancier cases they had multiple seven-segment LEDs which had a multi-state jumper for each segment, which decided to light that segment depending if the switch was on or off (example: http://www.minuszerodegrees.net/led_speed_display/LED%20disp...), so you could display either the two different clock frequencies, or a "HI"/"LO" message, or anything you wanted. And connecting that switch input to the motherboard wasn't necessary for the LED to change, so I guess that is how your father's was setup :)
I wonder if this is priced in to the public M1 Max benchmarks we've seen already? (Presumably it was in their own presentation benchmarks)
Yes, this goes a little farther than power management currently present in Linux and support by OEMs.
See Apples low power mode for an example.
If you’re actually comparing the two genuinely, I encourage you to read more on the topic.
Not that my opinion of what is garbage may differ than yours. The M1 has spoiled me perhaps.
It's definitely not as seamless or effortless as what you get on a Mac.
https://wiki.archlinux.org/title/Power_management#Userspace_...
There is nothing instant about the Linux variant.
Ive was not unilaterally responsible for deciding what constitutes a MacBook Pro or frankly any of the products Apple created. And he never dictated anything to anyone other than the Design team he managed.
Major product decisions are always made across many parts of the company e.g. Product Marketing, Design, Hardware Engineering, Operations etc and are signed off by the Senior Leadership Team.
MacBook Pro is a critical product for the company and the idea that one person is simply making all the decisions is just laughable.
You should look up what Product Marketing is because out of anyone they are far more responsible for what features go into a product.
And you were talking about product features e.g. TouchBar and ports. Those definitely aren't the sole decisions of the Design team.