3 ms·
The tl;dr: > The i486 added a few more control bits, and some of them > went into CR0. But instead of overflowing the new bits > into CR1, Intel decided
by falsedan 10y ago
The tl;dr:
> The i486 added a few more control bits, and some of them
> went into CR0. But instead of overflowing the new bits
> into CR1, Intel decided to skip it and open up CR4
> instead – for unknown reasons.
a.k.a. :shrug:
- Gracana 10y agoSpaces in front of your >s make your quote a raw formatted block that's really hard to read on a mobile device. :/
- Dylan16807 10y agoStrange. It's only 60 characters wide, so it should work fine. But the site fits it into a scrollable box only half the width of the screen.
- falsedan 10y agoYeah, I couldn't believe it when I saw it!
- falsedan 10y agoI'm posting from a mobile device and it looks unreadable, I hoped it was just for me because I know it looks fine on desktop…
- falsedan 10y agoI'm posting from a mobile device and it looks unreadable, I hoped it was just for me because I know it looks fine on desktop…
- ams6110 10y agoInstead of email-style quotes, just add an asterisk before and after the quoted text. That puts it in italics and makes it obvious that it's quoted material but it will wrap properly on various screen widths.
- scrollaway 10y agoI wish HN would simply support quoting with `>`. It's a recurring pain. That way it could be made to look good on mobile too...