explain xkcd - User contributions [en]

Talk:1709: Inflection

2016-07-21T15:14:35Z

Windowsfreak:

The article says that Japanese Kanji (which uses Chinese characters) is uninflected. This is based on a confusion. Japanese itself is highly inflected, with grammatical markers that are usually expressed using either Katakana or Hirigana syllabaries. The Kanji themselves are used for many words but are embedded in sentences that use both Kanji and one or both of the syllabaries. Both nouns and verbs are inflected. There is no such language as "Japanese Kanji" so this is just wrong. I will delete the corresponding clause in the main article. [[User:Billjefferys|Billjefferys]] ([[User talk:Billjefferys|talk]]) 12:35, 21 July 2016 (UTC)

Does anyone know what the emoticon part is trying to say?
[[Special:Contributions/108.162.215.170|108.162.215.170]] 16:59, 20 July 2016 (UTC)--
:A loose translation would be "Yes". [[Special:Contributions/162.158.255.106|162.158.255.106]] 18:19, 20 July 2016 (UTC)
:👍=Correct 👏=Bravo/Congratulations 😊=I'm glad you get it --[[Special:Contributions/162.158.92.207|162.158.92.207]] 18:54, 20 July 2016 (UTC)

This comic was posted 3 days after the [http://worldemojiday.com/faq/ "World Emoji Day" (July 17)] created by Emojipedia founder Jeremy Burge in 2014. The date July 17 appears in the calendar emoji used by Apple, but other tech companies use [http://www.digitaltrends.com/social-media/today-is-world-emoji-day/ different dates] in their version of this emoji. --[[Special:Contributions/162.158.92.207|162.158.92.207]] 17:30, 20 July 2016 (UTC)

"Emojish" could be a good replacement for English which suffers from highly [https://en.wikipedia.org/wiki/Phonemic_orthography nonphonemic orthography] and is a pain in the 🍑💨 to [https://en.wikipedia.org/wiki/Ghoti wright corecttly]. 😊 --[[Special:Contributions/162.158.92.207|162.158.92.207]] 17:57, 20 July 2016 (UTC)

I lost it at the end of the title text. My friend and I say wat to each other all the time. [[Special:Contributions/108.162.215.144|108.162.215.144]] 18:13, 20 July 2016 (UTC)

When I saw the emoji, I realized that I understand them without having a spoken or written language equivalence. We are so conditioned to say "what is it trying to say?" and expecting a language equivalent. But that does not have to be the case. It made me wonder if very early humans using pictographs for communication automatically had language equivalents, or could they think by mentally visualizing the pictograph without translating everything to words. If so, could we train ourselves to imagine emoji instead of words. They clearly communicate something that need not be verbal. [[User:Rtanenbaum|Rtanenbaum]] ([[User talk:Rtanenbaum|talk]]) 18:59, 20 July 2016 (UTC)

I count 52 Spanish forms of "andar": ando andas anda andamos andáis andan andaba andabas andábamos andabais andaban anduve anduviste anduvo anduvimos anduvisteis anduvieron andaría andarías andaríamos andaríais andarían andaré andarás andará andaremos andaréis andarán anduviera anduviese anduvieras anduvieses anduviéramos anduviésemos anduvierais anduvieseis anduvieran anduviesen ande andes andemos andéis anden anduviere anduvieres anduviéremos anduviereis anduvieren andar andando andado andad. [[Special:Contributions/108.162.219.12|108.162.219.12]] 20:13, 20 July 2016 (UTC)

First person singualar "I" is a strange mix. It uses a verb not listed in that chart "am", uses the plural form "have" for present tense, and the singular form "was" for past tense. [[User:Tahg|Tahg]] ([[User talk:Tahg|talk]]) 01:32, 21 July 2016 (UTC)
:It also uses "were" for subjunctive ("If I were you..." // "If I were walking to the park right now instead of being on the computer...")[[Special:Contributions/108.162.221.98|108.162.221.98]] 13:19, 21 July 2016 (UTC)

Why didn't Randall not use '''''MOAR''''' as a substitute for MORE? 😞😞😞 --Björn

1691: Optimization

2016-06-08T07:16:47Z

Windowsfreak: /* Transcript */

{{comic
| number = 1691
| date = June 8, 2016
| title = Optimization
| image = optimization.png
| titletext = Premature optimization is the root of all evil, so to start this project I'd better come up with a system that can determine whether a possible optimization is premature or not.
}}

==Explanation==
{{incomplete|Created by a BOT - Please change this comment when editing this page.}}
Donald Knuth in his paper "Structured Programming with Goto statements" said:
<blockquote>
"There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: '''premature optimization is the root of all evil'''. Yet we should not pass up our opportunities in that critical 3%."
</blockquote>

Source: http://web.archive.org/web/20130731202547/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf (Computing Surveys, Vol 6, No 4, December 1974)

==Transcript==
:[A flow chart is shown with three boxes connected with two arrows. The first box rectangular:]
:Are you prematurely optimizing or just taking time to do things right?

:[From the first box there is a short arrow straight down to a diamond shaped box:]
:Are you consulting a flowchart to answer this question?

:[An arrow labeled "Yes" continues down to the last box, which is rectangularly shaped.]
:You are prematurely optimizing

{{comic discussion}}

[[Category:Flowcharts]]

1691: Optimization

2016-06-08T07:15:09Z

Windowsfreak: /* Transcript */

{{comic
| number = 1691
| date = June 8, 2016
| title = Optimization
| image = optimization.png
| titletext = Premature optimization is the root of all evil, so to start this project I'd better come up with a system that can determine whether a possible optimization is premature or not.
}}

==Explanation==
{{incomplete|Created by a BOT - Please change this comment when editing this page.}}
Donald Knuth in his paper "Structured Programming with Goto statements" said:
<blockquote>
"There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: '''premature optimization is the root of all evil'''. Yet we should not pass up our opportunities in that critical 3%."
</blockquote>

Source: http://web.archive.org/web/20130731202547/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf (Computing Surveys, Vol 6, No 4, December 1974)

==Transcript==
{{incomplete transcript}}

:[A flow chart is shown with three boxes connected with two arrows. The first box rectangular:]
:Are you prematurely optimizing or just taking time to do things right?

:[From the first box there is a short arrow straight down to a diamond shaped box:]
:Are you consulting a flowchart to answer this question?

:[An arrow labeled "Yes" continues down to the last box, which is rectangularly shaped.]
:You are prematurely optimizing

{{comic discussion}}

[[Category:Flowcharts]]

1691: Optimization

2016-06-08T07:14:00Z

Windowsfreak: /* Transcript */

{{comic
| number = 1691
| date = June 8, 2016
| title = Optimization
| image = optimization.png
| titletext = Premature optimization is the root of all evil, so to start this project I'd better come up with a system that can determine whether a possible optimization is premature or not.
}}

==Explanation==
{{incomplete|Created by a BOT - Please change this comment when editing this page.}}
Donald Knuth in his paper "Structured Programming with Goto statements" said:
<blockquote>
"There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: '''premature optimization is the root of all evil'''. Yet we should not pass up our opportunities in that critical 3%."
</blockquote>

Source: http://web.archive.org/web/20130731202547/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf (Computing Surveys, Vol 6, No 4, December 1974)

==Transcript==
{{incomplete transcript}}

:[A flow chart is shown with three boxes connected with two arrows. The first box rectangular:]
:Are you prematurely optimizing or just taking time to do things right?

:[From the first box there is a short arrow straight down to a diamond shaped box:]
:Are you consulting a flowchart to answer this question?

:[An arrow labeled "Yes" continues down to the last box, which is rectangularly shaped.]
:You are prematurely optimizing

{{comic discussion}}