4 ms·
Semantically wrong or not, it's all the HN developers have chosen to give us for blockquoting. That's not the users' fault. For mobile, it helps if you manual
by CamperBob2 9y ago
Semantically wrong or not, it's all the HN developers have chosen to give us for blockquoting. That's not the users' fault.
For mobile, it helps if you manually truncate lines, like so:
One puzzling feature of the shift register
is that there is no wiring between the stages!
How do bits get from one stage to the next?
Did the chip have another layer of wiring that
wasn't in the photos? Was there some sort of
hidden connection? Eventually I noticed that
there wasn't an isolation ring between the
stages—a silicon barrier that separated most
I2L circuits. Without this isolation ring,
an "invisible" PNP transistor exists between
The site is called "Hacker News," after all. Apparently that's because we're expected to, well, hack.
- scarface74 9y agoItalics are more readable.
- CamperBob2 9y agoAnd semantically just as broken. Would it be that hard for the '1337 h4x04s at YC to support '>' blockquote markup like so many other forums?
- scarface74 9y agoSo what's more important "semantic correctness" or having a readable post?
- CamperBob2 9y agoThat question excludes an obvious middle ground, which is supporting a reasonable feature set in the BBS software so that the question never even comes up. Let's stop carrying water for lazy programmers. The lack of a proper quoting syntax has been a problem on HN for a long time.
- scarface74 9y agoWell, if you want your posts readable there seem to be two choices - either convince HN to change their code or use what they support. Which one do you think is more likely to happen?
- CamperBob2 9y agoI don't care either way, since I rarely read HN on mobile. But I sympathize with people who do, which is why I manually break quoted lines at a few dozen characters. Does anyone have a problem reading my example above? (Granted, it's at -3 and falling, so the text color will be the biggest challenge for mobile users. They can't highlight grayed-out text as easily. About the only safe conclusion I can draw, from the outside looking in, is that HN doesn't like mobile users very much.)
- andai 9y agoYep, despite the line length they get cut off about halfway.
- CamperBob2 9y agoSo, if I want to use the feature for what it's intended for, and post some code, people on mobile won't be able to read that, either. But we're told that it's the user's problem, not HN's, and that we should quietly accept half-assed broken features and be grateful for them. OK, got it.
- jacquesm 9y agoThey are not just programmers, they also moderate and put the trash out and have a life besides. Try being a bit more considerate of people whose lives you have no idea about and that work hard to make your life easier.
- codetrotter 9y ago> For mobile, it helps if you manually truncate lines, like so Mobile user here, your manual truncation was not enough unfortunately; it still gets cut off. Leading white space is for code. I wish everyone stopped making “blockquotes” with leading whitespace. It makes the text hard to read on mobile and it looks strange to have it in monospace font anyway. Instead, prefix each paragraph of quoted text with the “>” but no leading whitespace and it’s clearly visible that you are quoting. > One puzzling feature of the shift register is that there is no wiring between the stages! How do bits get from one stage to the next? Did the chip have another layer of wiring that wasn't in the photos? Was there some sort of hidden connection? > Eventually I noticed that there wasn't an isolation ring between the stages—a silicon barrier that separated most I2L circuits. > Without this isolation ring, an "invisible" PNP transistor exists between the stages, apparently allowing one stage to flip the next stage to the right value. > Each shift-register stage is constructed from two NAND-gate latches. When the clock is low, the first latch is forced into an indeterminate state. When the clock goes high, the latch ends up as 0 or 1 based on the bias it receives from the previous stage through the "invisible" PNP transistors. > Thus, the latch becomes edge-sensitive since it will change right on the clock's rising edge. I found a paper ("Injection-Coupled Synchronous Logic", 1978) that describes a similar technique for an I2L shift register9, so I think this is the right explanation, even though the circuit seems a bit sketchy.