Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Radiation-hardened quine

github.com

Post reply on HN
Print view View original

31–40 of 76 posts

Re: Radiation-hardened quine

#31

Post by stcredzero »

trapezoid wrote: post #24
audunw wrote: post #17

Earlier quoted context omitted.

Japanese is Subject-Object-Verb order, so it was probably "My Ruby (is) terrible". But I don't know Japanese so I can't tell you for sure. Chinese would also drop the verb in this case, so I'm assuming they might do that in Japanese as well.

Chinese and Japanese grammar have very little relation to each other - about as much as Chinese and English. (The alphabets are, of course, very similar, as the Japanese adopted Chinese characters.)

The Japanese use Chinese characters. The Japanese also have alphabets. (At least two.) But Chinese characters aren't exactly an alphabet and the Japanese don't use Chinese characters directly as an alphabet, though many characters are based on Chinese ones.

Re: Radiation-hardened quine

#32

Post by dllthomas »

foobarqux wrote: post #26
dllthomas wrote: post #3

Fascinating exercise. "Deleting one character" seems a phenomenally unlikely outcome of radiation, though.

Corrupting one bit is likely but if the rest of your system is not radiation hardened it isn't very helpful.

Yes, my objection wasn't that this failed to be a practical complete solution to radiation, but that there wasn't really a tie to radiation at all.

Re: Radiation-hardened quine

#33

Post by pjlegato »

stcredzero wrote: post #31
trapezoid wrote: post #24

Earlier quoted context omitted.

Chinese and Japanese grammar have very little relation to each other - about as much as Chinese and English. (The alphabets are, of course, very similar, as the Japanese adopted Chinese characters.)

The Japanese use Chinese characters. The Japanese also have alphabets. (At least two.) But Chinese characters aren't exactly an alphabet and the Japanese don't use Chinese characters directly as an alphabet, though many characters are based on Chinese ones.

Since we're being technical, Japanese does not have any alphabet as such; an alphabet has, by definition, a 1 to 1 correspondence between a single character and a sound. Japanese uses syllabaries ('kana' in Japanese), where almost all characters represent more than 1 sound. Hiragana is typically used to write Japanese words and grammatical particles, while katakana is typically used to write foreign words and for special emphasis, roughly analogous to how boldface type is used in English. Both of these kana are derived from Chinese characters, greatly simplified, though the relationship is somewhat distant.

Japanese also uses a third writing system called kanji, also not an alphabet, whose name literally means "Han [Chinese] characters" in Japanese. Kanji are logographs, where one character represents one entire word or concept rather than sounds.

Most kanji are identical or very similar to modern Chinese characters and are readily intelligible to a Chinese reader, at least in a general sense, though some have diverged a bit.

Grammar is another matter entirely. Japanese is a language isolate, a language that is not related to any other known language. (Someone will reply that it's distantly related to Korean, but this is a fringe theory in linguistics that is not widely accepted.) Chinese and Japanese are not grammatically related at all, and any similarity between their syntaxes is coincidental.

Re: Radiation-hardened quine

#34

Post by samatman »

tomp wrote: post #16

This would be much easier to understand if GitHub had proper ruby syntax highlighting. Just yesterday I was testing this, it appears they use very simplistic algorithm for parsing Ruby string interpolation - probably just regexes, which cannot handle nesting. https://gist.github.com/tomprimozic/9113077

Ironically, Linguist+Pygments, the detection and highlighting engine, is a Ruby tool.

Re: Radiation-hardened quine

#35

Post by ojii »

iterion1 wrote: post #29
ojii wrote: post #19

Earlier quoted context omitted.

Ruby is the subject in that sentence, not sure why gtranslate injects an "I". I'd translate it as "Ruby is scary, isn't it?"

Could also be 'surprising'. With the context of the sentence before it is basically, "I thought this would be hard to write. Ruby is surprising." Also, the author is a contributor to ruby on github, so I doubt he is negative towards the language. http://jisho.org/words?jap=%E6%81%90%E3%82%8D%E3%81%97%E3%81...

Yes it's one of those "funny" words in Japanese that is highly context sensitive, so you're probably right.

Re: Radiation-hardened quine

#37

Post by zackmorris »

Interesting! Does anyone know of a language or operating system that uses Reed–Solomon error correction on every file?

https://en.wikipedia.org/wiki/Reed–Solomon_error_correction

Or to top that, imagine a computer where the entire memory space, perhaps shared with persistent flash memory, was encoded in this manner, so that even the filesystem was protected against bit flips.

When I was doing Mac repair a few years back, the majority of the PowerMac G5s that came through the doors died premature deaths for two reasons: the ram was in a bad spot which caused the board to bend and crack on insertion, and the ram was non-ECC so it was notoriously difficult to isolate a bad ram chip. It was the most unreliable Mac I ever diagnosed, by perhaps an order of magnitude.

Contrast that with the Mac Pro, which used ECC and was so much more reliable that I don't remember seeing a single Mac Pro fail in the 3 years I was there.

Imagine how stable a Reed–Solomon computer would be..

Re: Radiation-hardened quine

#38

Post by DougBTX »

pjlegato wrote: post #33
stcredzero wrote: post #31

Earlier quoted context omitted.

The Japanese use Chinese characters. The Japanese also have alphabets. (At least two.) But Chinese characters aren't exactly an alphabet and the Japanese don't use Chinese characters directly as an alphabet, though many characters are based on Chinese ones.

Since we're being technical, Japanese does not have any alphabet as such; an alphabet has, by definition, a 1 to 1 correspondence between a single character and a sound. Japanese uses syllabaries ('kana' in Japanese), where almost all characters represent more than 1 sound. Hiragana is typically used to write Japanese words and grammatical particles, while katakana is typically used to write foreign words and for spe…

> an alphabet has, by definition, a 1 to 1 correspondence between a single character and a sound.

Do any languages have an alphabet according to this definition?

Re: Radiation-hardened quine

#40

Post by CraigJPerry »

zackmorris wrote: post #37

Interesting! Does anyone know of a language or operating system that uses Reed–Solomon error correction on every file? https://en.wikipedia.org/wiki/Reed–Solomon_error_correction Or to top that, imagine a computer where the entire memory space, perhaps shared with persistent flash memory, was encoded in this manner, so that even the filesystem was protected against bit flips. When I was doing Mac repair a few years b…

ZFS (the file system) goes to some fairly extreme lengths to validate data. It effectively doesn't trust anything past the south bridge.
Post reply on HN