My laptop would shut down. My first thought was that there was some sort of bug with memory or the underlying mechanism of pointers This author does not unders

My laptop would shut down. My first thought was that there was some sort of bug with memory or the underlying mechanism of pointers This author does not understand how protected memory and privileged instructions work in a modern OS and CPU. A typical bug in a non-privileged userland process cannot shut down a computer, because it simply does not have the permission to execute privileged instructions that would trigger a shutdown (IIRC, on x86, using IN/OUT to write to a register of CMOS memory on I/O port 0x70), or cannot write to memory pages that would mess up the OS's data structures so much that it would shut down (eg. BSOD, kernel panic). These types of pb are caused by privileged code (drivers, kernel modules), not by userland apps doing pure numerical computations. Also, virtually all languages allow you to utilize the CPU at 100% (see cpuburn, sha1sum, etc). This article is garbage. The pb is the laptop is defective and cannot dissipate the heat of 100% load on the CPU. This has nothing to do with Go.