64
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Nov 2023
64 points (100.0% liked)
Programming
17677 readers
72 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Drawing on Japanese, which is the only non-English language I have significant experience with,
object.method(parameter)
would feel more natural asobject.(parameter)method
, possibly even replacing the period separator with a Japanese grammatical construct (with no equivalent in English) that really suits this use case. Even the alternativefunction(self, parameter, ...)
would mesh better with natural Japanese grammar as(self、parameter、〜)function
. The majority of human languages have sentences which run Subject-Verb-Object, but a handful which includes Japanese run in the order Subject-Object-Verb.I gave an example of an alternative
for...in
loop in another comment here, so I won't rehash it here. But following the general flow of Japanese grammar, thatfor
at the beginning of the statement would feel much more natural as aで
(or "with
") at the end of the statement, since particles (somewhat similar to prepositions in English) go after the noun that they indicate, rather than before. And since semicolons don't exist in Japanese either, even they might be replaced with a particle like "と
".There aren't any big problems here, but a plethora of little things that can slowly add up.