We are currently working on new rules for what content should and shouldn't be allowed on this website, and are looking for feedback! See Esolang:2026 topicality proposal to view and give feedback on the current draft.

Talk:Nah.

From Esolang
Jump to navigation Jump to search

What was the motivation for this article? Corbin (talk) 15:52, 30 August 2026 (UTC)

to print "Nah.", persumably --dragoneater67 talk contribs (mobile) 17:52, 30 August 2026 (UTC)
Printing "Nah." is possible without inventing a "language" and writing an "article" (quoted intentionally, I don't consider them a language and an article). --Blashyrkh (talk) 17:55, 30 August 2026 (UTC)
I guess they meant to create a language that does nothing BUT print "Nah." since it's not the only constant language here and they do exist, believe it or not. However, I do agree with Esolang:2026 topicality proposal in the sense that maybe they should all be merged into a list like what's happening with Trivial brainfuck substitutions and Trivial deadfish substitutions. ❰❰ raiseafloppafan7741kausapin mo ako】【old contribs投稿】【▼(°v°)▼】【Fight for what HTML deserves.】❱❱ 17:58, 30 August 2026 (UTC)
I believe they don't even deserve a list. Populating such list with new items would be no effort at all. --Blashyrkh (talk) 18:00, 30 August 2026 (UTC)
Is it because constant languages are quite trivial in every way and there's like infinite constant languages derived from infinite strings? ❰❰ raiseafloppafan7741kausapin mo ako】【old contribs投稿】【▼(°v°)▼】【Fight for what HTML deserves.】❱❱ 18:02, 30 August 2026 (UTC)
this also applies to trivial brainfuck substitutions and trivial deadfish substitutions --dragoneater67 talk contribs (mobile) 18:10, 30 August 2026 (UTC)
They are at least programming languages. Constant languages are unusable for programming, so I wonder why they're not off-topic on this wiki. --Blashyrkh (talk) 18:12, 30 August 2026 (UTC)
deadfish's unusable for programming --dragoneater67 talk contribs (mobile) 18:14, 30 August 2026 (UTC)
A point in deadfish's favor is that it's not exactly trivial to implement, unlike constant languages where you can get a string printer generator ❰❰ raiseafloppafan7741kausapin mo ako】【old contribs投稿】【▼(°v°)▼】【Fight for what HTML deserves.】❱❱ 18:15, 30 August 2026 (UTC)
Not sure about stuff like Malloc or though since they (or in ™'s case, some dialects of it) are unusable for programming, maybe they're on the chopping block too? ❰❰ raiseafloppafan7741kausapin mo ako】【old contribs投稿】【▼(°v°)▼】【Fight for what HTML deserves.】❱❱ 18:23, 30 August 2026 (UTC)
is safe at least --dragoneater67 talk contribs (mobile) 04:39, 9 September 2026 (UTC)
I mean I think it'd balance itself out, I think there'd be less if not no people at all making constant languages if it's just gonna be a single entry in a table rather than its own page. I don't really care either way though, whatever happens happens. –PkmnQ (talk) 18:35, 30 August 2026 (UTC)
yeah good point, however I don't think much people are making constant languages very often anyway since they're not that interesting to anyone (no offense) unless they are part of a programming challenge or have been around for a while, but that's for already existing ones 【user:raiseafloppafan7741 | kausapin mo akopast life投稿】【▼(°ʌ°)▼】【Fight for what HTML deserves.】】 18:45, 30 August 2026 (UTC)
"Nah." is Han backwards which is the number one in korean and Korean is a language. And I would go as far as to say Korean and most CJK are noteworthy enough that anything in relation to them and their scripts are on topic.Miui (talk) 19:03, 30 August 2026 (UTC)
No offense but this is a quite arbitrary and strange argument to make. You can't just argue that something is on topic for the wiki just because its name is related to something on topic. Also, the Korean language itself is not on-topic for this wiki since it is a natural language for communication and not an esoteric programming language. 【user:raiseafloppafan7741 | kausapin mo akopast life投稿】【▼(°ʌ°)▼】【Fight for what HTML deserves.】】 19:12, 30 August 2026 (UTC)
You can make an esolang based on the Korean language and make a page for it here but you can't make a page about the Korean language itself, one is on topic but the other is not 【user:raiseafloppafan7741 | kausapin mo akopast life投稿】【▼(°ʌ°)▼】【Fight for what HTML deserves.】】 19:13, 30 August 2026 (UTC)
I have two languages which both require Nah. for their page descriptions. I was asked why I made the page, and the "strange" argument was not required. So attacking the argument and not recognizzing that I was only required to state why I made the page according to the OP is more offtopic IMHO. Nevertheless, I know people who actually speak [eselangs] in real life who would appreciate the context. In addition, it is helpful for coding in '''구'''. Being attacked by the community is pretty exhausting. It would be a shame if it went down for longer periods, but perhaps some of you folks do need to touch grass Miui (talk) 19:23, 30 August 2026 (UTC)
Supposedly "eselangs" contains a recaial slur and was deleted, and is just another bad faith argument it seems folks are using to gang up on me, but that language as well does not contain a racial slur, and it genuinely useful for people who speak that programming language naturally to learn how to program. Miui (talk) 19:25, 30 August 2026 (UTC)