5 ms·

I can only aspire to this level of beautiful whimsy - it's unfortunate that it triggered a codepath that could be measured, because that is by far the easiest e

by mjg59 5y ago

I can only aspire to this level of beautiful whimsy - it's unfortunate that it triggered a codepath that could be measured, because that is by far the easiest excuse to remove something beautiful and rarely seen. The closest I've managed is: $ grep -o --text U+1F4A9 vmlinux U+1F4A9 and while there may be an argument that this is whimsical, I don't think there's an argument that it's beautiful. (U+1F4A9 should be the literal Unicode PILE OF POO glyph, but HN strips it, so)

stavros 5y ago
But those bytes could randomly be in anything, doesn't mean they're interpreted as Unicode, no?
- mjg59 5y ago
  Oh absolutely - as far as the code is concerned they're just bytes, the fact that interpreting them as UTF-8 is entertaining is not something the kernel cares about at all.
  - stavros 5y ago
    Ah OK, I thought it was implying that the kernel displayed a pile of poo somewhere.
mjg59 5y ago
Although the fact that I've since encoded the "UUID" that this is contained within into other codebases such that Linux can't remove it without breaking some deployed u-boot builds is definitely something I'm proud of.
- Jaruzel 5y ago
  Your mention of UUID, reminded me that the GUIDs for Microsoft office products in the Windows Registry all end with '0FF1CE' - that's a nice Easter egg I think that doesn't impact anything.
  - dspillett 5y ago
    I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data. And for a while one was floating about in production where it would appear in URLs for anyone who cared to look to see¹, because someone else took a bit of my PoC work and shoved it where it didn't yet belong without review… [1] not just in the middle of a sea of otherwise arbitrary hex either, something like 00000000-0000-ABAD-IDEA-000000000000 so it was easily visible as a “test” value.
    - reaperducer 5y ago
      I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data. DEADBEEF shows up regularly if you work on projects that have only a seven-segment display.

by mjg59 5y ago

stavros 5y ago

But those bytes could randomly be in anything, doesn't mean they're interpreted as Unicode, no?

mjg59 5y ago
Oh absolutely - as far as the code is concerned they're just bytes, the fact that interpreting them as UTF-8 is entertaining is not something the kernel cares about at all.
- stavros 5y ago
  Ah OK, I thought it was implying that the kernel displayed a pile of poo somewhere.

mjg59 5y ago

Although the fact that I've since encoded the "UUID" that this is contained within into other codebases such that Linux can't remove it without breaking some deployed u-boot builds is definitely something I'm proud of.

Jaruzel 5y ago
Your mention of UUID, reminded me that the GUIDs for Microsoft office products in the Windows Registry all end with '0FF1CE' - that's a nice Easter egg I think that doesn't impact anything.
- dspillett 5y ago
  I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data. And for a while one was floating about in production where it would appear in URLs for anyone who cared to look to see¹, because someone else took a bit of my PoC work and shoved it where it didn't yet belong without review… [1] not just in the middle of a sea of otherwise arbitrary hex either, something like 00000000-0000-ABAD-IDEA-000000000000 so it was easily visible as a “test” value.
  - reaperducer 5y ago
    I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data. DEADBEEF shows up regularly if you work on projects that have only a seven-segment display.