|
|
|
|
|
by nottorp
3457 days ago
|
|
It's not the issue's existence that's my cause for concern, it's Apple's reaction to it. They've always had some process that went runaway and ate most of the CPU for no reason. Just the name of the process changed across hardware and software versions. The problem is, now they're removing an useful indicator to swipe the current problem (and I'm sure a large amount of people do have it) under the rug. It's this decision that worries me, not that they botched something on this laptop generation. |
|