- Joined
- May 22, 2015
- Messages
- 14,118 (3.96/day)
Processor | Intel i5-12600k |
---|---|
Motherboard | Asus H670 TUF |
Cooling | Arctic Freezer 34 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 2TB Crucial MX500 |
Display(s) | Dell U3219Q + HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
Exactly. Intel indeed "has to be better", but can they beat a fresh, unencumbered design while dragging compatibility features dating back to 8086 (that's about 45 years ago)? Is that all that silicon that goes to AVX and heats up like crazy under load worth it?With respect to x86, it is high noon for slashing legacy modes and legacy features, and revisiting some over-complicated features. I am not a fan of ARM's business model, but x86 better do something.
And if you want a "clean slate", I figure it will be nearly impossible to come up with another in-house instruction set when AArch64 and RISC-V are already around.
I'm glad I'm not tasked with solving this problem, but if this guy can, hats off.