The article mentions P or E is generally decided by if it's a "background" process (whatever than means). Possible some (undocumented) designation in code or directive to the compiler of the binary decides this at compile time.
My M2 MBA doesn't have a fan but literally smokes the majority on Intel systems which are space heaters this time of year. Those legacy x86 apps don't really exist for the majority of people anymore.
If you place 1mm thermal pads between the sinks and the case, the CPUs/GPUs won't throttle as readily. At least for my M3 MBA (check your actual clearance).
I replaced a MacPro5,1 with an M2Pro — which uses soooooo much less energy performing similarly mundane tasks (~15x+). Idle is ~25W v. 160W
You already don't want notebooks sitting on your lap (safe radiation exposure limits from WiFi / Bluetooth), which is why they're no longer referred to as "laptops" (by OEMs).
But if you're commenting about temperature / burns — the bottom of the MBP doesn't get noticeably warmer (at all), likely because the large metal case is such an efficient dissipator/sink.
The casebottom of my 15" MBAir has never exceeded 32°C — and that's sitting on a bed. Just a matter of physics: conductive case has orders of magnitude more thermal mass.
It also helps that Apple Silicon processors consumer orders of magnitude less power than most competitor OEMs. Pegged out the entire machine uses less energy than my former notebook's GPU, alone.
Are the Intel systems plugged in when running those tests? Usually when Apple machines do the tests then the difference between battery/plugged in is small if any.
> Multiple desktops work well, nice gestures, simple installers and applications.
Multiple desktops on Windows is not a nice experience for me. When you switch the desktop on one display then they ALL change for every display. I need them independent ala macOS or it is just so infuriating to use. Win11 also has big Fisher Price sized title bars now and macOS Tahoe isn't far behind. I think the GUI designers are on magic mushrooms when coming up with these designs.
It's about precedence in cases like this as the dominos fall quickly otherwise. If you stop the roots from growing then other countries won't get ideas. It's why companies should totally ban the Brit geo for all the daft laws they enact.
A CS degree is there to teach you concepts and fundamentals that are the foundation of everything computing related. It doesn't generally chase after the latest fads.
Sure, but we need to update our definitions of concepts/fundamentals. A lot of this stuff has its own established theory and has been a core primitive for software engineering for many years.
For example, the primitives of cloud computing are largely explained by papers published by Amazon, Google, and others in the early '00s (DynamoDB, Bigtable, etc.). If you want to explore massively parallel computation or container orchestration, etc, it would be natural to do that using a public cloud, although of course many of the platform-specific details are incidentals.
Part of the story here is that the scale of computing has expanded enormously. The DB class I took in grad school was missing lots of interesting puzzle pieces around replication, consistency, storage formats, etc. There was a heavy focus on relational algebra and normalization forms, which is just... far from a complete treatment of the necessary topics.
We need to extend our curricula beyond the theory that is require to execute binaries on individual desktops.
I just don't see the distinction. Looking at it from the other direction: most CS degrees will have you spend a lot of time looking at assembly language, computer architecture, and *nix tools. But none of these are mathematical inevitabilities - they're just a core part of the foundations of software engineering.
However, in the decades since this curricula was established, it's clear that the foundation has expanded. Understanding how containerization works, how k8s and friends work, etc is just as important today.
Containerization would be covered in a lecture on OS Concepts. A CS degree isn't to teach you about using containerization. Take a course specific to that.
I do agree that the scale has expanded a lot. But this is true with any other fields. Does that mean that you need to learn everything? Well at some point it becomes unfeasible.
See doctors for example, you learn a bit of everything. But then if you want to specialise, you choose one.
Fine, just like literally thousands of previous weekends before this one. And now I’m going to ask you the same and then zone out for 5 minutes because I literally couldn’t care less.
reply