So as far as I can tell, wikilambda is a programming language with IDs instead of keywords, and translatable user-defined names, and that gives you code like this:
Which is fine, that's just the storage format, kind of like how Smalltalk isn't readable on disk.
But a lot of things that I'm clicking through spend a lot of time describing the architectural-astronaut underpinnings in uselessly vague terms without showing any concrete examples at all or linking to anything at all. What they're saying could apply to any of dozens of programming languages that I've run across, and lots of it applies to literally all of them.
What does this actually do and how do you use it? And how, as a visitor to the WikiLambda project page¹, would I even find that information? Because I am a visitor and I just failed to do so. I can't even tell if this would be interesting to me or not because it said so little in so many words.
I rather like Wikidata and see a lot of untapped potential in it. In contrast, WikiLambda feels like a fully utopian project. I already shudder from the complexity of a medium to large MediaWiki template, and I'm not convinced this system can be expanded into a full programming ecosystem - one that's supposed to cross the bridge to natural language too.
As far as i know, wikilambda isn't really based around the mediawiki template system. And the mediawiki ecosystem itself is turning away from complex wiki syntax templates to lua based templates.
Regardless i do agree with you though. WikiLambda/Abstract wikipedia feels like second system syndrome to me.
WikiLambda is what happens when someone looks at the definition of the second-system effect and says, "Hey, that's cool and all, but I bet I can make a bigger, better version of this."
"The Search for the Perfect Language" is a really entertaining book if you like codes, languages, occult history, and/or chuckling at hubristic academic endeavors.
Umberto Eco is a wonderful writer, up there with Borges. They shared a deep philosophical interest in language, exploring it from various angles in their works. Both widely versed in obscure literature, approaching it with wit and humor.
So as far as I can tell, wikilambda is a programming language with IDs instead of keywords, and translatable user-defined names, and that gives you code like this:
Which is fine, that's just the storage format, kind of like how Smalltalk isn't readable on disk.But a lot of things that I'm clicking through spend a lot of time describing the architectural-astronaut underpinnings in uselessly vague terms without showing any concrete examples at all or linking to anything at all. What they're saying could apply to any of dozens of programming languages that I've run across, and lots of it applies to literally all of them.
What does this actually do and how do you use it? And how, as a visitor to the WikiLambda project page¹, would I even find that information? Because I am a visitor and I just failed to do so. I can't even tell if this would be interesting to me or not because it said so little in so many words.
1: https://www.mediawiki.org/wiki/Extension:WikiLambda is this the project page? Should I be looking somewhere else? I can't even tell. It seems fairly central to a lot of links though.
https://www.joelonsoftware.com/2001/04/21/dont-let-architect...
I miss Joel's blog posts!
Touché
I rather like Wikidata and see a lot of untapped potential in it. In contrast, WikiLambda feels like a fully utopian project. I already shudder from the complexity of a medium to large MediaWiki template, and I'm not convinced this system can be expanded into a full programming ecosystem - one that's supposed to cross the bridge to natural language too.
As far as i know, wikilambda isn't really based around the mediawiki template system. And the mediawiki ecosystem itself is turning away from complex wiki syntax templates to lua based templates.
Regardless i do agree with you though. WikiLambda/Abstract wikipedia feels like second system syndrome to me.
WikiLambda is what happens when someone looks at the definition of the second-system effect and says, "Hey, that's cool and all, but I bet I can make a bigger, better version of this."
The estate of Jorge Borges should sue.
This might interest you then https://ont.fyi (shameless plug)!
Looks nice! I have my own vision and plans in this field :)
"The Search for the Perfect Language" is a really entertaining book if you like codes, languages, occult history, and/or chuckling at hubristic academic endeavors.
Umberto Eco is a wonderful writer, up there with Borges. They shared a deep philosophical interest in language, exploring it from various angles in their works. Both widely versed in obscure literature, approaching it with wit and humor.
A language to surpass Metal Gear...