omcnoe
Joined 1 year ago
Joined 1 year ago
Intel missed for a different reason - they didn't invest in the product space at all for decades. In terms of units they had the most market share (millions of Intel Integrated Graphics chips), but it wasn't seen as important. Bare minimum to render Windows and Office UI, nothing more.
Within a year many of these (>20%) started experiencing the "400 MHz bug" where the CPU is either intermittently or constantly stuck at 400 MHz, and the laptop starts to heat up like an oven. As far as I know there has never been any conclusive fix for this issue from Framework, or even an official debugging guide.
It really soured me on the idea of repairable laptops - what's the point of it being "repairable" if you have huge fundamental flaws in the hardware that go unfixed?
The mount is fine and speedy enough, but the underlying reads/writes turn into native NTFS reads/writes through Windows. NTFS file API is incredibly slow - high fixed overhead for initial file access.
So patterns like node_modules with many small individual files (or compiling code in general) are much much slower on Windows or WSL2 /mnt/c due to the fixed overhead adding up over a large number of files.
It's a ridiculous problem that has plagued Windows for years.
End result is that many outsourcing firms are borderline fraudulent in the way they treat their customers.
Lost out on $900m off a single spelling mistake - probably the most expensive spelling mistake in history.