Practicality: Difference between revisions

612 bytes added ,  1 month ago
no edit summary
No edit summary
No edit summary
(6 intermediate revisions by 3 users not shown)
Line 1:
{{Needs work|Vetting, more perspectives and rebuttals}}
[[File:RobWords Toki Pona video comments.png|250px|thumb|Analysis of first 1000 top-level comments on the video about Toki Pona by YouTuber Rob Watts (RobWords), demonstrating non-speakers' views of the practicality of the language]]
 
The '''practicality''' of Toki Pona for real-world use is debated, as it is a {{w|Philosophical language|philosophical}} {{w|artistic language}}. This extends to whether lack of fitness for various use cases would be a shortcoming of Toki Pona, thus devaluing it, or simply outside of its design goals.
 
Often, when people are introduced to the language, they voice concerns about Toki Pona being used in {{w|emergencies}}, or otherwise precise, risky, or jargon-heavy situations such as {{w|medical examination}}s.<ref>{{cite web|url=https://web.archive.org/web/20240202121235/https://cdn.discordapp.com/attachments/301380012156911616/1202926900633407529/robwordscomments.png|title=Stats from the 1000 first top-level comments on Robwords' video on Toki Pona|author={{tok|jan Sepulon}}|username=|date=2024-02-02|website=Discord|publisher=|access-date=2024-02-02}}</ref> Suffice it to say that a niche hobby {{w|quote=constructed language}} Archivedis fromnot [//cdn.discordapp.com/attachments/301380012156911616/1202926900633407529/robwordscomments.pngbeing theused originalin such applications, and most [[Tokiponist]]s onare 2not Februarypromoting 2024.<blockquoteit style="font-size:smaller;">for such usage.
;Objection
:Technical (science, medical)
;Percentage
:16.71%
;Example
:"Doctors will give you the wrong medicine because they won't understand your description of your condition"
</blockquote></ref><ref>{{cite web|url=//drive.google.com/file/d/13OtUeC7mwtkycNcmN6Z1wsybIIJlCrSq|title=robwordsstats.ods|author={{tok|jan Sepulon}}|username=|date=2024-02-02|website=Google Drive|publisher=|access-date=2024-02-02|quote=}}</ref> Suffice it to say that a niche hobby {{w|constructed language}} is not being used in such applications, and most [[Tokiponist]]s are not promoting it for such usage.
 
These concerns may stem from the assumption that Toki Pona has the same {{w|Finvenkism|goals of global adoption}} as the {{w|Esperanto movement}}; in reality, Toki Pona is not an [[international auxiliary language]], and many Tokiponists are against treating it as such.
 
=={{tp|pu}}==
{{nasin pu}}
The book {{lipu pu|en}}, in the chapter "Limitations", claims the following:<ref>{{cite pu|11}}</ref>
 
Line 24 ⟶ 18:
 
==Emergencies==
{{Needs workmedia|[https://knowyourmeme.com/photos/1916659-science-diagrams-that-look-like-shitposts the "{{tp|a}}" shark meme|section]}}
As of 2024, Toki Pona is probably unsuitable for emergency situations due to the low number of speakers. Navigating emergencies in the language would be most likely to come up at a Toki Pona [[gathering]]. Instructions would ideally still be given multilingually, as often already occurs with natural languages. It remains to be seen whether Toki Pona will grow enough to become relevant in emergencies.
 
Line 54 ⟶ 48:
|o tawa anpa supa. o len o awen e lawa sina. o jo e noka supa.
|Go below furniture. Cover and protect your head. Hold the furniture's leg.
|o tawa anpa supa&#x3000;{{idsp}}o len o awen e lawa sina&#x3000;{{idsp}}o jo e noka supa
}}
 
Line 60 ⟶ 54:
Toki Pona can express concepts that are given {{w|jargon}} in English and other natural languages, although generally not as efficiently. It may demand [[mi ken ala toki pona e ijo la mi sona ala e ijo|deeper understanding]] of the concepts involved, but among professionals in a technical field, this would presumably be the case. Thus, issues with translating jargon would come down to lack of technical understanding or Toki Pona skill, rather than a shortcoming of the language inherently.
 
For jargon that is relatively international, while Toki Pona's [[philosophy]] <em>prefers</em> that concepts are explained in simple language, one could [[Toki Pona is not exceptional|do as natural languages have]] and translate terms such as "{{w|HDMI cable}}" as {{tp|[[linja]] HDMI}}, for example. (See also [[{{sect|Names#Against names|Names &sect; Against names]]}}.) If this does not work, one would have to describe the subject or explain what it does in better detail, but this is still equally true of other languages.
 
Notably, very many such technical terms were not present in <em>any</em> languages until recently, so this seems like a flawed metric to measure a language's practicality, much less how worthwhile its existence and usage is. (For example, what is the term for "HDMI cable" in {{w|Latin}}?)
 
There is also an argument that the lack of jargon can be <em>more</em> practical. While jargon provides better {{w|information density}}, it risks not properly or fully conveying the information in the first place, limiting its practicality. The plain, transparent approach encourages sharing and building proper understanding, and discourages obfuscation tactics such as "{{w|bullshitting}}". As put by {{tok|jan Lakuse}}:<ref>{{cite roundtable|page=7}}</ref>
<blockquote>
A person can't throw a million-dollar {{w|buzzword}} at you like {{wikt|antidisestablishmentarianism}} and expect you to know what they're talking about. They have to be curious about where you are and meet you where you're at. Instead of conversation starting with a buzzword, 'antidisestablishmentarianism,' it might start instead with, 'so how familiar are you with the Church of England?'
</blockquote>
 
==See also==