Re:Wikifunctions
by zozbot234 on Wednesday December 06, 2023 @04:54PM
(#38550062)
I assume it's intentional, so that source code can be stored in a form that's independent of natural language. They can just call to a LSP backend for the implementation language to rename identifiers in the source code before showing them to the user, much like Wikidata does today with its semantic content.
[ Parent
| on HN ]
Re:Wikifunctions
by zorgmonkey on Wednesday December 06, 2023 @06:43PM
(#38551025)
I think you're about the goal, but in practice it looks more line they are making code that is readable in 0 languages instead of at least 1 language.
It looks like in practice people are unsurprisingly coming up with workarounds for this by adding some boilerplate code, these are the first two lines from the python example above (also all the local variables in the function are in English too):
def Z10591(Z10591K1, Z10591K2):
word, is_ra_plural = Z10591K1, Z10591K2
Re:Wikifunctions
by threatofrain on Wednesday December 06, 2023 @08:10PM
(#38551644)
There's no reason why English words couldn't be translated any better than Z11410, but now editors will have an extra layer of indirection.
so we will need to learn to read gzip (and other compressed binary formats) as if they were not compressed
this is also related to how 2 hour long movies will diminish into a niche... and movies of the future will be more like [0]
this observation is on the same trend as operas; which way back would last all evening (over 3 hours was typical)
Re:Wikifunctions
by finnjohnsen2 on Wednesday December 06, 2023 @06:38PM
(#38550995)
> so we will need to learn to read gzip
this rant gave me a proper laught. thank you.