4 ms·
I get that it's because the author collected these examples from Twitter, but I find it upsetting that all this ASCII art is presented as pictures instead of...
by ywain 4y ago
I get that it's because the author collected these examples from Twitter, but I find it upsetting that all this ASCII art is presented as pictures instead of... ASCII.
- kzrdude 4y agoHe beats expectations by linking to the actual source code
- chrismorgan 4y agoBut… but… when you have identified where it comes from, why would you go to the trouble of putting the images in rather than copying the code? I would genuinely expect copying the code to be easier, and it’s clearly better and more consistent.
- rocqua 4y agoThis gives a consistent and faithful image. Doing it as plaintext would cause problems with reflowing, weird scrolling boxes, and generally might have you fighting with the browser text renderer.
- chrismorgan 4y agoConsistent? Faithful? I see a whole bunch of images in different styles with different fonts, colours, fairly consistently the wrong line-heights, and even severe JPEG artefacts in at least one case. Doing it in plain text with `white-space: pre` (the default for the <pre> element) would work better.
- rocqua 4y agoConsistent over devices, not Consistent between the images. The point is that jpeg rendering is a whole lot more consistent between devices than html rendering.
- Akronymus 4y agoBecause making the code render properly would require a JS library. (Only slightly sarcastic, as I genuinly have heard similar arguments before)