2 ms·
They should have mentioned that in the first line of the github readme, not burried deep down in the text.
by littlecranky67 2mo ago
They should have mentioned that in the first line of the github readme, not burried deep down in the text.
- RamRodification 2mo agoBuried? Deep down? The fourth paragraph, clearly labeled "Affected Systems", a minute or two into the read.
- deleted 2mo ago[deleted]
- rbanffy 2mo agoWe have shorter attention spans now.
- bunbun69 2mo agoMultiple things can be true at the same time. While we do have shorter attention spans, some (lots of?) developers absolutely suck at writing articles
- rbanffy 2mo agoI fancy myself as a decent writer, but I suck at writing documentation. People describe reading my notes frustrating and incomprehensible. I find it much better to use AI to untangle my, admittedly, convoluted reasoning
- account42 2mo agoAnd some intentionally write clickbait headlines even though the have the skills to do better.
- fph 2mo agoOpening with the title "hardware backdoors in x86 CPUs" is quite misleading, though.
- netsharc 2mo agoImagine getting a letter "High Risk of Cancer" and getting all the way to the 4th paragraph to see it's just relevant to a race of blue aliens...
- arcfour 2mo agoThey knew what they were doing by not including "VIA C3 CPUs" before the fourth paragraph. Come on. It should have been in the title.